Understanding JavaScript Code Coverage
<p><em>This is the first of a two-post series in which we try to understand how code coverage is measured and reported in JavaScript by building a simple code coverage tool ourselves. You can find the second post </em><a href="https://medium.com/engineering-semantics3/understanding-javascript-code-coverage-part-2-9aedaa5119e5" rel="noopener"><em>here</em></a><em> and the reference code for this exercise </em><a href="https://github.com/amarnus/learning-code-coverage" rel="noopener ugc nofollow" target="_blank"><em>here</em></a><em>.</em></p>
<p>I have always been fascinated by the idea of being able to measure code quality. Recently, I had a chance to dig in and understand how a code coverage tool works under the hood. It was a fun exercise — so, I thought that I’ll share.</p>
<p>Code Coverage is a measure of the percentage of your codebase covered by your test-suite. It is a simple metric but arguably a strong indicator of code quality.</p>
<p><a href="https://medium.com/engineering-semantics3/understanding-code-coverage-1074e8fccce0"><strong>Visit Now</strong></a></p>