[TIP] Help needed for Couverture.io (code coverage service)
alexandre.conrad at gmail.com
Tue Feb 21 10:28:23 PST 2017
Thanks for your input! I'll have take a closer look at their reports and
play with test samples and edge cases.
So far I haven't seen any services out there that show as much information
as couverture.io does, such as showing introduced dead code. For example,
if a function is no longer called due to a code change (in the diff), the
coverage will naturally drop outside the diff but many services don't tell
*where* it dropped (it's like finding a needle in a haystack).
But hey, even if they do provide this functionality, I guess there's room
for everyone ;) Thanks for your support!
On Tue, Feb 21, 2017 at 8:49 AM Florian Bruhin <me at the-compiler.org> wrote:
> Hey Alex,
> * Alexandre Conrad <alexandre.conrad at gmail.com> [2017-02-21 16:12:22
> > Instead of just rendering prettified coverage reports, Couverture.io
> > encourages contributors to write tests by showing them exactly where they
> > need to focus their testing efforts for a given pull request.
> Doesn't codecov.io do the same? For example, here:
> I see that there are four new lines, of which one is not covered and
> one is covered partially.
> http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
> GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
> I love long mails! | http://email.is-not-s.ms/
> testing-in-python mailing list
> testing-in-python at lists.idyll.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the testing-in-python