Routes.js files in develop don't have coverage

[uo289321]

Even with the tests done, sonarCloud keeps saying that they have 0% coverage. Tried to change the name, still 0%. (branch develop)

[augustocristian]

Hi everyone!
I checked a few minutes ago and the pipeline reported good coverage.

Please provide me more details about the problem, but looks like something related to:
https://community.sonarsource.com/t/coverage-issues-for-typescript-lcov-could-not-resolve-file-paths/13301/6

[augustocristian]

After the group have implemented the changes suggested by @pglez82, I've been examining the local Sonar logs. Removing the relative paths resolved the warnings, but the code coverage remains lower than expected. It seems that the files are being properly indexed for analysis, as evidenced by these two examples:


I've suggested to activate the verbose mode until the problem would be solved.

[algarfer]

Yes, I activated the debug mode on e2f394a.

Also, I have tested generating jest configuration files and changing the paths of sonar, but these don't seem to fix it at all.

I've also noticed that there are some inconsistencies in the coverage reports:

Further information can be found here