Javascript Coverage mismatch

Thanks for looking into it! It appears we have same file names in different modules and when the lcov reports are generated the source file (SF:) path in these files show only relative path which might be causing sonar to not appropriately map these files.

I think we can modify the jest config or update the lcov reports to have it populate the absolute path or atleast include the module name in the path.

Please consider this resolved

Bharath.

1 Like