Makes one page for each package, class, and table

All 5 scenarios hold

Nobody chooses the shape of a report. The shape follows the packages of the test classes that published. Each row below writes a published table as the class that ran it and the method that holds it.

The indexDepth option says how much of the tree gets an index page. That option has a feature of its own, beside this one.

A nested test class is a page below its outer class, and the outer class becomes an index page even when it publishes no table of its own. That index page is the one page the reporter names after the Java class rather than after its slug, which is why the row below reads OrderTest beside product-test. Open: whether it should carry the slug the other class pages carry.