Publish karma/nightmare coverage reports in Jenkins/integration with Sonarqube
Description
Environment
None
Potential Workaround
None
blocks
is blocked by
relates to
Checklist
hideTestRail: Results
Activity
Show:
John Malconian September 29, 2018 at 1:42 AM
This is enabled for all frontend components by default that generate lcov.info reports.
Jeffrey Cherewaty August 8, 2018 at 4:43 PMEdited
Looks like we can also exclude any .stories.js or /stories/*.js files.
John Malconian August 8, 2018 at 3:58 PM
Couple of TODOs to myself so I don't forget -
The Sonarqube scan should only be triggered on PR and master branch builds.
Set up a separate Github account for Sonarqube. Sonarqube has a nasty habit of removing all previous PR comments when it adds a comment. This may mitigate that.
John Malconian August 8, 2018 at 3:54 PM
Tests should be excluded now. https://sonarcloud.io/component_measures?id=folio-org%3Astripes-components&metric=Coverage
John Malconian August 7, 2018 at 9:37 PM
Right. The easiest method would be to exclude -test.js. I will try that.
Done
Details
Details
Assignee
John MalconianReporter
John MalconianPriority
P3TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created August 7, 2018 at 3:08 PM
Updated November 12, 2018 at 2:24 PM
Resolved September 29, 2018 at 1:42 AM
TestRail: Cases
TestRail: Runs
Karma coverage reports are generated during Jenkins builds as HTML and lcov.info , but are not published by Jenkins. Publish the HTML report and possibly use lcov.info for integration with Sonarqube.