LCOV reporter changed from Absolute file paths to Relative

[jcdesousa]

#9742 💥 Regression Report
After upgrading to the 25.2.7, we saw that our reported lcov.info file is not showing the absolute file paths anymore. This is causing a problem when reporting to sonarQube.

Before on 24.8.0:
SF:/Users/jose.sousa/git/project/webapp/common/App.js

Now on 25.2.7:
SF:common/App.js

Last working version

24.9.0

Stopped working in version:
25.1.0

To Reproduce

Steps to reproduce the behavior:

• run jest with coverage and lcov reporter.
• check lcov file generated and compare with the previous.

[jcdesousa]

It seems that for version 25.2.0, we need to configure the projectRoot to fix the relative path.

"coverageReporters": [
      ["lcov", {"projectRoot": "../"}],
      "text-summary"
    ]

[SimenB]

Interesting... Did any Istanbul dependencies change during your upgrade? I didn't think any changes we made would affect this

[jcdesousa]

Yes, I did further analises and it seems it stop working after 24.9.0. The version 25.1.0 does have some updates to istanbul dependencies.

[SimenB]

Right. That's expected. Essentially istanbuljs/istanbuljs#529 and the linked PR to jest which allows you to set projectRoot is the "fix" on our side

[williamsousa]

@jcdesousa Thank's a lot. Works fine!

[randing89]

After setting to

 ["lcov", {"projectRoot": "/"}]

The path is

SF:Users/jose.sousa/git/project/webapp/common/App.js

It is still not an absolute path

[Rey-Wang]

@randing89 that's even a wrong path.
@jcdesousa Actually, we can solve this by using the sed command to correct the path in lcov.info, even though, you still need to take care of the path may different with the test-report.xml

[ramkrk]

After upgrading to Jest 27.0.6, still facing the SF path issue in coverage reports.

without coverageReporters:

SF:app1/common/App.js

with coverageReporters ["lcov", {"projectRoot": "/"}] :

SF:Users//git/project/webapp/app1/common/App.js

with coverageReporters ["lcov", {"projectRoot": "__dirname"}] :

SF:..app1/common/App.js

Jest-config present in webapp folder

Am expecting the following:

Absolute SF Path: /Users//git/project/webapp/app1/common/App.js
Relative SF path: common/App.js

Right now using sed command to get it work.

Is there any workaround to fix it up in jest config level?

[dlarr]

Same problem, I am expecting absolute path. Anyone made any progress on this (except for the sed usage)

[jozefizso]

I have simple project where I use jest v29.4.3. I run npm test as jest --coverage without jest config. I get correct coverage report in console, the HTML report and XML files are correct.

When I run the jest --coverage locally on Windows or macOS system, the coverage/lcov.info contains correct path to app/index.js file:

TN:
SF:app\index.js
FN:19,(anonymous_0)
FN:81,(anonymous_1)

When I run the same project in GitHub Action in ubuntu-22.04 the path in lcov.info is incorrect. All the other files - HTML, XML reports, contain correct paths (eg. ):

TN:
SF:../../home/runner/work/generator-license/generator-license/app/index.js
FN:19,(anonymous_0)
FN:81,(anonymous_1)

From clover.xml:

<file name="index.js" path="/home/runner/work/generator-license/generator-license/app/index.js">

[github-actions]

This issue is stale because it has been open for 1 year with no activity. Remove stale label or comment or this will be closed in 30 days.

[github-actions]

This issue was closed because it has been stalled for 30 days with no activity. Please open a new issue if the issue is still relevant, linking to this one.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.