Keyboard

↓ ↑
move between the rows you can see
→
open a feature, then step into it
←
close a feature, or step out to the one above
Enter
go to the page in focus
Tab
the same rows, plus everything else on the page
/
search the whole report
m
open or close the navigation drawer
Esc
leave the search box, or close the drawer
?
this list

Folds an HTML index page below its top level

All 5 scenarios hold

Every level of the report has an index page listing what is under it, and the report opens on the root one.

The rule below reads a report of two test classes in one package, com.example.orders.OrderTest and com.example.orders.ProductTest, with one table each. The root index therefore sits above two class pages, and each class page above one table.

An index page holds every page under it, however deep. The top level alone is open. An entry that holds pages is a fold, so the reader opens the part they want. The publisher no longer chooses one depth for every reader. A folded entry stays in the page, so a browser search and a printed copy both reach it.

These rows read the root index of a second, deeper report. That report holds 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 its top level is order-test and pricing.

expected outcome broken scenario
ScenarioEntryBehind a fold?
A page at the top levelorder-testfalse
A fold at the top levelpricingfalse
A table below a top-level pageitemstrue
A fold below a top-level foldpricing-testtrue
A table two levels downdiscountstrue