[Python-Dev] Code coverage reporting. (original) (raw)
Brett Cannon brett at python.org
Mon Jun 19 19:17:50 CEST 2006
- Previous message: [Python-Dev] Code coverage reporting.
- Next message: [Python-Dev] Code coverage reporting.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 6/19/06, Benji York <benji at benjiyork.com> wrote:
Brett Cannon wrote: > But it does seem accurate; random checking of some modules that got high > but not perfect covereage all seem to be instances where dependency > injection would be required to get the tests to work since they were > based on platform-specific things. > I don't know if we need it hooked into the buildbots (unless it is dirt > cheap to generate the report). It would be interesting to combine the coverage over several platforms and report that.
Ah, do the union of the coverage! Yeah, that would be nice and give the most accurate coverage data in terms of what is actually being tested. But as Titus says in another email, question is how to get that data sent back to be correlated against.
-Brett -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/python-dev/attachments/20060619/33a1a1d2/attachment.html
- Previous message: [Python-Dev] Code coverage reporting.
- Next message: [Python-Dev] Code coverage reporting.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]