[tahoe-lafs-trac-stream] [Tahoe-LAFS] #623: coverage: compute+display differential coverage

[Tahoe-LAFS]

#623: coverage: compute+display differential coverage
------------------------------------+--------------------------------
     Reporter:  warner              |      Owner:  zooko
         Type:  enhancement         |     Status:  closed
     Priority:  major               |  Milestone:  eventually
    Component:  dev-infrastructure  |    Version:  1.2.0
   Resolution:  fixed               |   Keywords:  coverage coveralls
Launchpad Bug:                      |
------------------------------------+--------------------------------
Changes (by daira):

 * keywords:  coverage => coverage coveralls
 * status:  assigned => closed
 * resolution:   => fixed


Old description:

> It would be great if the buildbot produced, for each new build, a
> description of lines of code that gained or lost test coverage.
>
> I just made a change to the Makefile to include the raw figleaf pickle in
> the directory that gets uploaded to the webserver, so from here on out we
> should have machine-parsable historical data. (for the builds until this
> point, we only have rendered HTML for each build).
>
> I suppose the right approach is to have a 'render-figleaf-delta' target,
> which starts by trying to download the pickle file from the previous
> build, then have a script to construct the deltas, then render those
> deltas into more HTML, then include the delta HTML (as well as a machine-
> readable delta pickle) in the next batch of uploaded data.

New description:

 It would be great if the buildbot produced, for each new build, a
 description of lines of code that gained or lost test coverage.

 I just made a change to the Makefile to include the raw figleaf pickle in
 the directory that gets uploaded to the webserver, so from here on out we
 should have machine-parsable historical data. (for the builds until this
 point, we only have rendered HTML for each build).

 I suppose the right approach is to have a 'render-figleaf-delta' target,
 which starts by trying to download the pickle file from the previous
 build, then have a script to construct the deltas, then render those
 deltas into more HTML, then include the delta HTML (as well as a machine-
 readable delta pickle) in the next batch of uploaded data.

--

Comment:

 Actually coveralls.io: [https://coveralls.io/r/tahoe-lafs/tahoe-lafs]

 This isn't using buildbot but I think it fulfills the spirit of this
 ticket.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/623#comment:11>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage