Closed defunctzombie closed 1 year ago
@itay are you still working on this project? Any thoughts on the above?
I would be also interested in the above.
Adding a unit test that checks the cover stats and confirms that all files are above a certain level of code coverage should be a simple thing to do. (similarly to what you do in the cli reporter to decide the red color of the row)
(I was thinking of adding a test like that ... it would fire when travis-ci kicks in... and make sure that no commit brings down the code coverage. So neat! )
@ogt @shtylman I haven't had time, but I would more than welcome someone doing this. Happy to give either of you push access to the repo, and give some guidance on where to put things.
Is there a good example (or even possible) to use cover as a library? The thinking would be to instrument it into a test suite (like mocha) so that the testing and coverage generation can happen all at once just by running the main test framework.
From my very limited understanding of cover, it works by intercepting require, which I think should mean that it could be dropped in to a nodejs app as a library?