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

Heads each section at its depth, and no deeper than six

All 5 scenarios hold

A report is normally a directory of pages. Single-file mode writes it as one self-contained HTML file instead. You can mail that file, attach it to a build, or open it from a memory stick with nothing beside it.

The rules below read a report of one test class, org.example.CalendarTest, with two tables: leapYear and monthLength.

The one file carries the outline that the tree carried. Each section therefore takes a heading one level below the section it sits in. HTML stops at h6. A report deep enough to need an h7 therefore holds its deepest sections at h6. The reporter writes no heading a browser does not know.

The second class below keeps the report root shallow. The packages named in each row are then levels the reader walks down.

expected outcome broken scenario
ScenarioPublished tablesSection heading?
The class in the root package
  • org.example.CalendarTest#leapYear
  • org.example.other.Trivia#facts
h3
One package deeper
  • org.example.a.CalendarTest#leapYear
  • org.example.other.Trivia#facts
h4
Two packages deeper
  • org.example.a.b.CalendarTest#leapYear
  • org.example.other.Trivia#facts
h5
Three packages deeper
  • org.example.a.b.c.CalendarTest#leapYear
  • org.example.other.Trivia#facts
h6
Four packages deeper, past h6
  • org.example.a.b.c.d.CalendarTest#leapYear
  • org.example.other.Trivia#facts
h6