Opens and marks the trail down to your page

All 3 scenarios hold

Every page carries the whole report as a link tree. A reader can therefore reach any rule from any page, without going back to an index first.

The rules below read a report of one test class, com.example.orders.OrderTest, whose only table is items. That report is three pages deep: the package orders, the class page order-test, and the table page items.

A page deep in the report is one entry in a long tree. A mark on that entry alone highlights a single leaf, and leaves the reader to work out which feature holds it. The sidebar therefore marks every entry above the page as well.

An entry that holds pages is a fold, so the sidebar of a large spec is a short list rather than every rule at once. A reader can follow a link into the middle of a report, and would then have to unfold a path back to their own page. The sidebar writes the folds on that path open instead. Only an entry with pages under it is a fold, which is why a page at the top level opens one fold and stands above no entry at all.

These rows read a second, deeper report, of two test classes: com.example.orders.OrderTest, whose table is items, and com.example.orders.pricing.PricingTest, whose table is discounts. The report root is the package orders, so the entries below it are order-test and pricing.