[TIP] Help needed for Couverture.io (code coverage service)

[Alexandre Conrad]

Hi Florian,

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!

Cheers,
Alex

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
> +0000]:
> > 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:
> https://codecov.io/gh/qutebrowser/qutebrowser/pulls/2339/diff
>
> I see that there are four new lines, of which one is not covered and
> one is covered partially.
>
> Florian
>
> --
> 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
> http://lists.idyll.org/listinfo/testing-in-python
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.idyll.org/pipermail/testing-in-python/attachments/20170221/1b7a4440/attachment.htm>