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

Links an index page to every page beneath it, nested as they are

All 4 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.

The list holds the whole subtree, and not the level below alone. One nesting level of the list is one level of the report.

Each link takes the syntax of the format the reporter generates, and points at the file that format writes. The two text formats therefore list the same pages. An HTML index lists them too, and folds all but the top level away — the rule below states that.

expected outcome broken scenario
ScenarioFormatPage URLPage content?
The root index pageasciidoc/
  • = ++orders++
  • “”
  • * xref:./order-test/index.adoc[++order-test++]
  • ** xref:./order-test/items.adoc[++items++]
  • * xref:./product-test/index.adoc[++product-test++]
  • ** xref:./product-test/price.adoc[++price++]
The root index pagemarkdown/
  • # orders
  • “”
  • * [order-test](./order-test/index.md)
  • * [items](./order-test/items.md)
  • * [product-test](./product-test/index.md)
  • * [price](./product-test/price.md)
A class index pageasciidoc/order-test
  • = ++order-test++
  • “”
  • * xref:./items.adoc[++items++]
A class index pagemarkdown/order-test
  • # order-test
  • “”
  • * [items](./items.md)