Test report generation

[troglobit]

Description

A few observations re: report.pdf

Reduce font size of logs

Without sacrificing content, and also improving harmony with the size of document headings, we could reduce the size of the font used for test logs a few points. This would also allow more text to fit on a single line.

In the following example we can see how the size of the font in the test log appears larger than the sub-heading for the test name itself:

Avoid in-document links

The text "Test Specification" at the start of the test output looks like another sub-heading. It was not until started digging around in the report generator that I realized it was a link! For links it's almost always best to use more recognizable blue underlined. However, for print media it should be avoided altogether.

Other recommendations

1. A front page, with (brand-able) logo and relevant details of what the report covers
2. In the Test Summary, total tests and numbers of pass/fail/skip should¹ be listed
3. Using the test names, and the 9pm numbering, as title of each test in the Test Output is counter-intuitive, and frankly confusing. We should use the test name from the specification instead

Footnotes

1. mgmt loves their metrics ↩

[troglobit]

Proposed Changes

The following screenshot shows both the font size change, as well as two new fonts, using Source Sans Pro for the body, from the same family as Source Code Pro, and the clean Lato for headings.

Front page with (optional) logo, details the vendor/OS as well as version and test date.

For the Test Summary and combined specification and report, see above and the following test-report.pdf attachment.

Combining spec. and report usually works, but for cases where a test does not have a spec (maybe all tests should?) we fall back to use the test name and 9pm numbering in headings, as shown here in the refreshed Table of Contents.

Pull Requests

• Improve PDF test report generation and typography rical/9pm#59
• Test fixes #1135