Source Map for Instrumention

[deckar01]

Note: This unrelated to #59.

I am debugging the instrumented code in a browser, and it would be a lot easier if there was a source map that the browser could use to hide istanbul's instrumentation.

My use case is jasmine's web runner. Currently I either have to debug instrumented code, or rerun the tests with an alternate configuration that skips coverage. I am currently choosing to debug instrumented code, because I am switching between the coverage and the web runner often. It is faster to set break points in the test files and step into the instrumented code, than it is to switch scripts when I want to run a coverage report.

[cphoover]

+1 Yup

[deckar01]

FWIW I am migrating my unit tests to a new configuration that uses babel and it's istanbul plugin to instrument the specimen when it is imported into the test script. I loose the ability to differentiate the source code from it's dependencies for instrumentation, but I gain a much simpler config file that doesn't require a huge manifest of files. Another huge advantage is that my HTML coverage report shows the coverage of the ES6 source files.