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

Writes every link relative, whatever the format

All 3 scenarios hold

A report is a tree of files that link to each other. Every one of those links is relative to the page that holds it. One report therefore works from three places: a local folder, the root of a web server, and a subpath such as a project's GitHub Pages. You do not generate it again for each.

The rules below read a report of two test classes in sibling packages, com.example.orders.OrderTest and com.example.products.ProductTest, with one table each. The report root is the package example. Below it sit the packages orders and products, each above one class page, and each class page sits above its one table — items or price. A page of that report therefore lies up to two directories below the root.

One link that starts at a server root breaks a report served from a subpath. It breaks that report nowhere else, so the build stays green and a reader meets the fault first. This rule therefore reads back every file of a whole report, in each format, and collects the links those files hold.

A report may state one address in full: the link back to the site that hosts it. A project declares that link, and the reporter never generates it. The reports below declare none.

expected outcome broken scenario
ScenarioFormatLinks starting at a server root?
A report of any format
  • html
  • markdown
  • asciidoc
[]