<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Coverlet on Artur Rios Lab</title><link>https://lab.artur-rios.tech/tags/coverlet/</link><description>Recent content in Coverlet on Artur Rios Lab</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 21 Oct 2026 13:10:00 +0000</lastBuildDate><atom:link href="https://lab.artur-rios.tech/tags/coverlet/index.xml" rel="self" type="application/rss+xml"/><item><title>Test Coverage in .NET: What It Measures and How to Collect It</title><link>https://lab.artur-rios.tech/dotnet/test-coverage/</link><pubDate>Wed, 21 Oct 2026 13:10:00 +0000</pubDate><guid>https://lab.artur-rios.tech/dotnet/test-coverage/</guid><description>&lt;p&gt;A pull request comes back with a comment: &amp;ldquo;coverage dropped from 84% to 81%&amp;rdquo;.&#10;What does the number mean? Which 3% went missing, and does it matter? Coverage&#10;is one of the few test metrics that every .NET tool can produce for free, and&#10;one of the easiest to misread. It is very good at answering &lt;em&gt;which code did no&#10;test run?&lt;/em&gt; and close to useless at answering &lt;em&gt;are the tests any good?&lt;/em&gt;&lt;/p&gt;</description></item></channel></rss>