You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have lots of projects that need to work in browsers but also in Node, Narwhal.js, Rhino, and other JavaScript environments. Example coverage report: http://rawgithub.com/mathiasbynens/esrever/master/coverage/esrever/esrever.js.html
The main code starts at line 20 and ends at line 41. Everything else is the export logic that covers all those environments.
Of course, since Istanbul uses Node to run the tests, the code paths for the other environments won’t be reached. But this is also causing the coverage % of the file to drop.
It would be nice if it was possible to somehow configure Istanbul to ignore some parts of the code and just consider them as covered, or just display them greyed out in the report (to signify that they were ignored while calculating the coverage % of the file). Thoughts?
The text was updated successfully, but these errors were encountered:
I have lots of projects that need to work in browsers but also in Node, Narwhal.js, Rhino, and other JavaScript environments. Example coverage report: http://rawgithub.com/mathiasbynens/esrever/master/coverage/esrever/esrever.js.html
The main code starts at line 20 and ends at line 41. Everything else is the export logic that covers all those environments.
Of course, since Istanbul uses Node to run the tests, the code paths for the other environments won’t be reached. But this is also causing the coverage % of the file to drop.
It would be nice if it was possible to somehow configure Istanbul to ignore some parts of the code and just consider them as covered, or just display them greyed out in the report (to signify that they were ignored while calculating the coverage % of the file). Thoughts?
The text was updated successfully, but these errors were encountered: