Changing location of SpecRunner breaks code coverage

[robianmcd]

If I change the outfile to something like this:

outfile: 'target/_SpecRunner.html'

Then the code coverage starts looking for all my javascript one directory above where it is actually located. The resulting error messages look like this:

Warning: Unable to read "../javascript/services/englishStrings.js" file (Error code: ENOENT). Use --force to continue.

Anyone else getting this issue?
Thanks!
Rob

[williamrjribeiro]

I'm also having the same problem but I haven't figured it out yet. But I found out that grunt-jasmine 0.5.2 had a fix for a kid of similar issue:
gruntjs/grunt-contrib-jasmine#68

Probably the jasmine-istanbul has to update.

[nukefusion]

I also came across this issue and I believe it's the aforementioned grunt-jasmine fix that's caused this. Jasmine now creates the list of source files with paths relative to the outdir. The istanbul template then uses these paths to copy the sources for instrumentation, however it does that from the context of the grunt CWD. Because the paths are now relative to the outdir and not the grunt CWD, if the CWD and outdir are at different levels the sources can't be found.

As a result this change probably has ramifications for any jasmine template that enumerates the source files.