Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
fix(karma): allow custom browsers to specify args (fixes #595) #2132
fix(karma): allow custom browsers to specify args (fixes #595) #2132
Changes from all commits
7e3fb2a
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
how is this tested? to put it another way, if I take these changes to packages/karma/test but throw away the change to packages/karma/karma.conf.js will the CI be red?
Feels like maybe we're missing one more target here, like maybe a
generated_file_test
that asserts on what the generated karma conf will look like for the:testing
karma_web_test_suite aboveThere 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.
That's right. I was a bit concerned about the churn associated with a golden file test, but if that is the standard, I will create one.
Would you happen to know how to get a label to the generated .conf.js file?
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 would be nice to test it in a better way but probably hard to sense whether the browser got a right initial dimensions or something.
I don't know the label offhand, if you use
bazel query //the/package:all
it will probably show upThere 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 had to make the generated .conf.js a 'predeclared' output so as to write this test. I hope that's okay.
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.
yeah that looks fine. Note you could also add the file to an Output Group to give a way to select the dynamic (non-predeclared) output