Code Coverage is a measurement of how many lines/blocks/functions/etc of your code are executed while the automated tests are running. Code coverage is collected by using a specialized tool to instrument the binaries to add tracing calls and run a full set of automated tests against the instrumented product. A good tool will give you not only the percentage of the code that is executed, but also will allow you to drill into the data and see exactly which lines of code were executed during particular test. It is one of the very important QE best practices. Code coverage is going to improve the quality and coverage of our tests. Code Coverage is usually done for both backend and front end applications. I will talk/demo on how we can do it for front end javascript applications only, as this is not widely been done in the QE field. It is quiet easy to do it for a back end application. Some Challenges are, for example: – Development code fully written in JavaScript and Test Code fully written in Java – Test code is not part of the dev code’s repo – Code instrumentation Tool used: Istanbul: https://istanbul.js.org/