[tahoe-lafs-trac-stream] [tahoe-lafs] #2103: Ensure buildbot configuration automates coverage analysis with publicly linkable reports.

[tahoe-lafs]

#2103: Ensure buildbot configuration automates coverage analysis with publicly
linkable reports.
--------------------------+-------------------------------
     Reporter:  nejucomo  |      Owner:  daira
         Type:  defect    |     Status:  new
     Priority:  normal    |  Milestone:  undecided
    Component:  unknown   |    Version:  1.10.0
   Resolution:            |   Keywords:  buildbot coverage
Launchpad Bug:            |
--------------------------+-------------------------------

Comment (by zooko):

 Replying to [comment:1 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
 [http://nedbatchelder.com/code/coverage/api.html#api 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.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2103#comment:3>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage