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.
I have a Loopback server, which is similar to Express
There are certain routes that I simply know get hit by Loopback, for example, everything in the boot directory.
I am running a child_process like this:
but using Istanbul in this way, does not seem to generate accurate coverage reports.
Any idea why this might be?
For example, I know this file would have been run by Loopback and I can log it to be sure:
(because the above screenshot is from a file in
server/boot