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.
| Scenario | Published tables | Section heading? |
|---|---|---|
| The class in the root package |
| h3 |
| One package deeper |
| h4 |
| Two packages deeper |
| h5 |
| Three packages deeper |
| h6 |
| Four packages deeper, past h6 |
| h6 |