Ensure buildbot configuration automates coverage analysis with publicly linkable reports.

[nejucomo]

I'm not certain whether or not the buildbot waterfall produces coverage results.

Close Criteria:

Close this ticket when:

• automated builds produce coverage information, and
• there are publicly linkable source code coverage links.

Bonus:

• Include a link to a coverage report.

[nejucomo]

Something I would love, which should probably be a separate ticket, is a report of unittest results, and for each unittest there is a link to a coverage report for only that unittest.

[daira]

Replying to nejucomo:

Something I would love, which should probably be a separate ticket, is a report of unittest results, and for each unittest there is a link to a coverage report for only that unittest.

I think that's hard to implement in terms of the current --coverage feature of trial.

[zooko]

Replying to nejucomo:

Something I would love, which should probably be a separate ticket, is a report of unittest results, and for each unittest there is a link to a coverage report for only that unittest.

That would be awesome. I can see how to implement it using Ned Batchelder's coverage.py. You would use ​coverage.py's API to start tracing just before each unit test (i.e. perhaps in a setUp method), and then just after each unit test, use the coverage.py API to generate the coverage results report and put it in a place where it will be linked to from that unit test.

[daira]

Duplicate of #623.