Closed flegall closed 6 years ago
Hi @flegall,
Apologies for the delayed reply, I was away for the holidays & am still catching up on some things.
Each formatter looks in a hard-coded path for the coverage information, and the lcov
formatter expects to find the coverage at coverage/lcov.info
. In your case it seems like the simplest thing to do might be to just cd js-given
before running cc-test-reporter after-build
. If you do that you'll probably also need to drop the -p js-given
flag: I suspect the actual file paths listed in your lcov.info
are already relative to js-given
, e.g. that file would have an entry for src/Stage.js
, not js-given/src/Stage.js
.
Let me know if that helps.
In case this helps someone in the future. I'd simply forgotten to generate my report file. Be sure to check that this file is actually generated.
Hi,
I'm trying to set up code coverage on my travis build of js-given (https://github.com/jsGiven/jsGiven).
In my build the coverage file is located in ./js-given/coverage/lcov.info
The coverage is there, because coveralls already use it
I've setup the after_script part to :
I'm having this error :
Regards,
Florent