<div dir="ltr">Hi Florian,<div><br></div><div>Thanks for your input! I'll have take a closer look at their reports and play with test samples and edge cases.</div><div><br></div><div>So far I haven't seen any services out there that show as much information as <a href="http://couverture.io">couverture.io</a> 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).</div><div><br></div><div>But hey, even if they do provide this functionality, I guess there's room for everyone ;) Thanks for your support!</div><div><br></div><div>Cheers,</div><div>Alex</div></div><br><div class="gmail_quote"><div dir="ltr">On Tue, Feb 21, 2017 at 8:49 AM Florian Bruhin <<a href="mailto:me@the-compiler.org">me@the-compiler.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hey Alex,<br class="gmail_msg">
<br class="gmail_msg">
* Alexandre Conrad <<a href="mailto:alexandre.conrad@gmail.com" class="gmail_msg" target="_blank">alexandre.conrad@gmail.com</a>> [2017-02-21 16:12:22 +0000]:<br class="gmail_msg">
> Instead of just rendering prettified coverage reports, Couverture.io<br class="gmail_msg">
> encourages contributors to write tests by showing them exactly where they<br class="gmail_msg">
> need to focus their testing efforts for a given pull request.<br class="gmail_msg">
<br class="gmail_msg">
Doesn't <a href="http://codecov.io" rel="noreferrer" class="gmail_msg" target="_blank">codecov.io</a> do the same? For example, here:<br class="gmail_msg">
<a href="https://codecov.io/gh/qutebrowser/qutebrowser/pulls/2339/diff" rel="noreferrer" class="gmail_msg" target="_blank">https://codecov.io/gh/qutebrowser/qutebrowser/pulls/2339/diff</a><br class="gmail_msg">
<br class="gmail_msg">
I see that there are four new lines, of which one is not covered and<br class="gmail_msg">
one is covered partially.<br class="gmail_msg">
<br class="gmail_msg">
Florian<br class="gmail_msg">
<br class="gmail_msg">
--<br class="gmail_msg">
<a href="http://www.the-compiler.org" rel="noreferrer" class="gmail_msg" target="_blank">http://www.the-compiler.org</a> | <a href="mailto:me@the-compiler.org" class="gmail_msg" target="_blank">me@the-compiler.org</a> (Mail/XMPP)<br class="gmail_msg">
GPG: 916E B0C8 FD55 A072 | <a href="http://the-compiler.org/pubkey.asc" rel="noreferrer" class="gmail_msg" target="_blank">http://the-compiler.org/pubkey.asc</a><br class="gmail_msg">
I love long mails! | <a href="http://email.is-not-s.ms/" rel="noreferrer" class="gmail_msg" target="_blank">http://email.is-not-s.ms/</a><br class="gmail_msg">
_______________________________________________<br class="gmail_msg">
testing-in-python mailing list<br class="gmail_msg">
<a href="mailto:testing-in-python@lists.idyll.org" class="gmail_msg" target="_blank">testing-in-python@lists.idyll.org</a><br class="gmail_msg">
<a href="http://lists.idyll.org/listinfo/testing-in-python" rel="noreferrer" class="gmail_msg" target="_blank">http://lists.idyll.org/listinfo/testing-in-python</a><br class="gmail_msg">
</blockquote></div>