Separating the instrumenting step from the "coverage" step is quite helpful, p.e. if you want to run integration tests against an instrumented web application.
What we are doing is: instrument our code with istanbul, start a webapp with the intrumented code, then run our integration tests against it, afterwards we generate the reports.
it would be great if we could extend or test setup with coffeescript support and your ibrik istanbul extension looks great and doing almost the job we need.
Do you see a good way to introduce an separate instrument command to ibrik?
Separating the instrumenting step from the "coverage" step is quite helpful, p.e. if you want to run integration tests against an instrumented web application.
What we are doing is: instrument our code with istanbul, start a webapp with the intrumented code, then run our integration tests against it, afterwards we generate the reports.
it would be great if we could extend or test setup with coffeescript support and your ibrik istanbul extension looks great and doing almost the job we need.
Do you see a good way to introduce an separate instrument command to ibrik?