[FOLIO-2100] Sonarcloud coverage reports 0% on ui-modules Created: 12/Jun/19  Updated: 03/Jun/20  Resolved: 14/Jun/19

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Bug Priority: TBD
Reporter: Ian Hardy Assignee: Ian Hardy
Resolution: Done Votes: 0
Labels: ci, devops, platform-backlog
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Sprint: Core: F - Sprint 65
Story Points: 2
Development Team: Core: Platform

 Description   

Observed in a number of UI modules, sonarscan reports test coverage reports 0



 Comments   
Comment by Ian Hardy [ 12/Jun/19 ]

Error from jenkins build (ui-calendar #116)

Perhaps sonar is fialing to pick up tests and needs an additional parameter set when invoked `-Dsonar.sources` or `-Dsonar.tests`

INFO: Analysing [/home/jenkins/workspace/folio-org_ui-calendar_master/project/artifacts/coverage/lcov.info]
WARN: Could not resolve 16 file paths in [/home/jenkins/workspace/folio-org_ui-calendar_master/project/artifacts/coverage/lcov.info], first unresolved path: /home/jenkins/workspace/folio-org_ui-calendar_master/project/CalendarUtils.js
Comment by Ian Hardy [ 12/Jun/19 ]

Created new quality profile FOLIO-JS test that omits the latest change to the defautl Sonar Way quality profile, and tested on ui-calendar https://jenkins-aws.indexdata.com/job/folio-org/job/ui-calendar/job/folio-2100-testing/lastSuccessfulBuild/. This does not appear to clean up the coverage issue & the error above,

Comment by David Crossley [ 13/Jun/19 ]

This looks like our problem:
https://community.sonarsource.com/t/js-coverage-doesnt-work-anymore/10750

Comment by Ian Hardy [ 13/Jun/19 ]

Thanks David, looks like they're working on a bugfix, see the pr here:
https://github.com/SonarSource/SonarJS/pull/1263

Comment by Ian Hardy [ 14/Jun/19 ]

Looks like the patched version of the SonarJS was deployed to sonarcloud sometime around 12 utc and JS projects are reporting code coverage as of that time.

Comment by John Malconian [ 17/Jun/19 ]

For those modules showing 0% coverage due to this issue, coverage stats will be corrected the next time a build of master is triggered and the next analysis is done.

Generated at Thu Feb 08 23:18:12 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.