Understanding JavaScript Code Coverage

This is the second 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 first post <a href="https://medium.com/engineering-semantics3/understanding-code-coverage-1074e8fccce0" rel="noopener">here</a> and the reference code for this exercise <a href="https://github.com/amarnus/learning-code-coverage" rel="noopener ugc nofollow" target="_blank">here</a>. By the end of the <a href="https://engineering.semantics3.com/understanding-code-coverage-1074e8fccce0" rel="noopener ugc nofollow" target="_blank">last post</a>, we had built an instrumenter. It takes our single-file source program and modifies it to add counters. These counters let us measure statement coverage when our tests run. The next step is to make our tests use our instrumented source code. <a href="https://medium.com/engineering-semantics3/understanding-javascript-code-coverage-part-2-9aedaa5119e5">Learn More</a>