Yet another JS code coverage tool that computes statement, line, function and branch coverage with module loader hooks to transparently add coverage when running tests. Supports all JS coverage use cases including unit tests, server side functional tests and browser tests. Built for scale.
Just curious, when an Istanbul process exits prematurely (uncaughtException, etc), does Istanbul still collect as much coverage information as possible no matter what? Or does it only write out the info if the process exits with code 0?
this seems pertinent, because my exit code handler is not being hit, and I believe it's because istanbul's exit handler is synchronously exiting before mine gets invoked?
Just curious, when an Istanbul process exits prematurely (uncaughtException, etc), does Istanbul still collect as much coverage information as possible no matter what? Or does it only write out the info if the process exits with code 0?