-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Restore Jest sonar reporter and bump workflow timeout #1840
Conversation
Signed-off-by: Andrew W. Harn <[email protected]>
Signed-off-by: Andrew W. Harn <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your continued efforts to keep this stuff running.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks @awharn!
Codecov ReportAll modified and coverable lines are covered by tests ✅ 📢 Thoughts on this report? Let us know!. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes LGTM.
I had one comment/question
@@ -134,6 +134,7 @@ module.exports = { | |||
}], | |||
["github-actions", { "silent": false } ] | |||
], | |||
"testResultsProcessor": "jest-sonar-reporter", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should the "jest-sonar-reporter" be added to the reporters list above?
I'm kind of worried about the testResultsProcessor
property, since it had a tendency to override some reporters (probably in older versions of jest). IDK if you remember, but that's why Dan's jest-stare
reporter had a list of additionalReporters
where we had the jest-junit
and jest-sonar
.
If this is not something to be concerned about in newer versions of Jest, then I'm fine with leaving it as-is.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tried that and it doesn't work. jest-sonar-reporter does not support the newer interface, and has been archived since 2019. Nothing else seems to exist outside of beta for providing Jest results to Sonar, so either we need to add this back, add something else to do a sonar scan on top of Jest tests (only thing I saw was in jest-sonar
with a version of 0.2.1), or drop the use of Sonar.
@@ -80,5 +81,8 @@ | |||
"ts-jest": "^29.0.0", | |||
"typedoc": "^0.23.10", | |||
"typescript": "^4.0.0" | |||
}, | |||
"jestSonar": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we add the jest-sonar-reporter
to the reporters list, we can move this configuration item there too 😋
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Again, tried that, Jest threw errors because the jest-sonar-reporter API wasn't compatible.
Kudos, SonarCloud Quality Gate passed! |
Seems like the reporter doesn't support the new syntax. 😢 |
What It Does
Restore Jest-Sonar scans and increase workflow timeout
How to Test
Review Checklist
I certify that I have:
Additional Comments