Instrument task includes relative paths to source files in instrumented files instead of absolute paths

[epoberezkin]

That makes it difficult to merge coverage reports from different sources.

I am using instrument task on source files that are later combined into a bundle with browserify.
At the moment I have to replace relative paths in instrumented files to absolute paths.

That is the similar issue to the one fixed here:

karma-runner/karma-coverage#163

[jamestalmage]

From the spec

path - The path to the file. This is an absolute path, and should be the same as the key in the report object.

[epoberezkin]

Exactly. So this package doesn't follow the spec...

[jamestalmage]

Yes... I was voicing agreement.

[epoberezkin]

:)

[epoberezkin]

The workaround is to use the option cwd:

instrument: {
  files: '...',
  options: {
    cwd: __dirname
  }
}

But probably should be the default behaviour

[sgerace]

@epoberezkin Thanks, that helped a lot!

In case this helps anyone else: in my case I am using load-grunt-config so all of my grunt configuration files are located in a /grunt folder within my project (not in the root of my project). Therefore, cwd: __dirname didn't work for me, I ended up using cwd: fspath.join(__dirname, '..'), but same basic idea.