Skip to content
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

feat(karma): npm peer deps & remove @rules_webtesting//browsers/sauce:chrome-win10 support #1346

Merged
merged 1 commit into from
Nov 14, 2019

Conversation

gregmagolan
Copy link
Collaborator

@gregmagolan gregmagolan commented Nov 9, 2019

Branches off of #1342 which should land first.

Also cleanup us arguments and doc string for karma_web_test_suite.

BREAKING CHANGES:

npm karma deps for karma_web_test and karma_web_suite are now peer deps so that the versions used can be chosen by the user.

This PR also removes the built-in @io_bazel_rules_webtesting//browsers/sauce:chrome-win10 saucelabs support. It is not very useful as it only tests a single browser and it difficult to use. In the angular repo, saucelabs support was implemented with a custom karma config using karma_web_test. This is the recommended approach.

@gregmagolan gregmagolan force-pushed the karma_peer_deps branch 3 times, most recently from 923df59 to 3de6f6a Compare November 12, 2019 02:30
…:chrome-win10 support

Also cleanup us arguments and doc string for karma_web_test_suite.

BREAKING CHANGES:

npm karma deps for karma_web_test and karma_web_suite are now peer deps so that the versions used can be chosen by the user.

This PR also removes the built-in  `@io_bazel_rules_webtesting//browsers/sauce:chrome-win10` saucelabs support. It is not very useful as it only tests a single browser and it difficult to use. In the angular repo, saucelabs support was implemented with a custom karma config using karma_web_test. This is the recommended approach.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants