-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
🏗 ✨ ❄️ add karma-junit-reporter to store test results in a way circleci can interpret them #33682
Conversation
06d1a3f
to
557aaf9
Compare
Hey @rsimha! These files were changed:
|
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.
Exciting to see this in action! A few comments below.
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.
Getting closer! A few more comments below.
588893a
to
3a5b506
Compare
const {Base} = Mocha.reporters; | ||
|
||
/** | ||
* Creates a custom Mocha reporter which runs many reporters at once. |
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.
It seems like we now have two ways to combine reporters: This function, and the one below, which combines MochaDotsReporter
and JsonReporter
.
amphtml/build-system/tasks/e2e/mocha-ci-reporter.js
Lines 27 to 32 in e9cb065
function ciReporter(runner, options) { | |
Base.call(this, runner, options); | |
this._mochaDotsReporter = new MochaDotsReporter(runner, options); | |
this._jsonReporter = new JsonReporter(runner, options); | |
return this; | |
} |
Assuming I'm right, can we consolidate them into one solution (whichever is better)? Okay to punt this to a separate PR, and might be worth getting this bit reviewed by Esther.
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 looked at ciReporter
when I was writing this and didn't view it as very extensible. I think it could easily be replaced with an invocation of my new method but as you suggest I would rather handle that as a separate PR. @estherkim Do you have an opinion on this?
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 would rather have ciReporter
replaced directly by your junit reporter than in this roundabout way. Ok to do in a separate PR if you want to remove e2e changes out of this one.
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.
Alright, I'll move the e2e changes to another PR
2f01eca
to
d9aad91
Compare
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.
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.
Blocking for now to get e2e comments resolved, thanks!
…ci can interpret them (ampproject#33682) * add karma-junit-reporter to store test results in a way circleci can interpret them
…ci can interpret them (ampproject#33682) * add karma-junit-reporter to store test results in a way circleci can interpret them
CircleCI can show test metrics but is not currently configured to do so. Unfortunately our current approach result collection is not supported so I am adding in the reporter they recommend (https://circleci.com/docs/2.0/collect-test-data/#karma) and configuring the build to read those results