Istanbul doesn't play nicely with sandboxed-module

[searls]

I require each of my units with sandboxed-module so that I can isolate it from its collaborators, but unfortunately this approach means istanbul never instruments the code that's loaded (and requiring it separately doesn't work either).

More discussion here.

[gotwarlost]

Low-tech inelegant solution:

• Pre-instrument the code using istanbul instrument
• Ensure that the instrumented version of code is loaded in tests
• Ensure that the __coverage__ global is set for every sandbox you create so it keeps accumulating stuff
• Write a process.on('exit') handler to dump coverage to file system (similar to istanbul cover)
• Run istanbul report to get the reports.

As I said, fugly :)

[searls]

Thanks. I actually have started a really nasty monkey patch in lieu of this. I've got everything working up until the report generation (because, grossly, the sandboxed-module code will be a couple of lines longer than the actual file listing).

https://gist.github.com/searls/7001427

[searls]

Just updated the gist, glad to report that I got this monkey patch of sandboxed-module playing completely nicely with istanbul: https://gist.github.com/searls/7001427