Continuous code coverage

19 Feb 2012

What if we could do a continuous code coverage? That is, while debugging and testing the app, storing the coverage information. A first version would consider lines that are not changed as covered if they have been executed during previous runs. This could be a sort of blunt tool to help isolate code that should be flagged either for removal, for code review, automatic or manual testing.

It should be simple enough to send information about code coverage when running JavaScript code. The challenge is to map the coverage information with source lines and keeping some sort of data structure that represents the code and coverage information that can be updated with the old coverage information form previous versions of the code.



Do you want to send a comment or give me a hint about any issues with a blog post: Open up an issue on GitHub.

Do you want to fix an error or add a comment published on the blog? You can do a fork of this post and do a pull request on github.