Skip to content

Separate Saucelabs cross-browser tests by package #1756

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

Merged
merged 11 commits into from
May 13, 2019
Merged

Conversation

hsubox76
Copy link
Contributor

@hsubox76 hsubox76 commented May 7, 2019

Setting up our Saucelabs test to run tests for each package separately and sequentially, making it easier to identify which package/browser combination has failed.

Each run of all tests has one build number and counts as a build in Saucelabs' dashboard. Each test has a separate name based on package name and browser environment. Tests are run on one package at a time, on 5 browsers in parallel.

Will try to address some of the test failures in future PRs.

Copy link
Contributor

@mmermerkaya mmermerkaya left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you change the PR title to a single sentence summary of what you did?

http://go/cl-descriptions#firstline

@hsubox76 hsubox76 changed the title Ch saucelabs Separate Saucelabs cross-browser tests by package May 8, 2019
@hsubox76
Copy link
Contributor Author

hsubox76 commented May 9, 2019

  • Set it to only run npm pretest scripts right before the package it is for.
  • Make sure it exits with 1 if any package fails (so CI will show an overall failure)

@hsubox76 hsubox76 merged commit 462047e into master May 13, 2019
@hsubox76 hsubox76 deleted the ch-saucelabs branch May 13, 2019 18:04
@firebase firebase locked and limited conversation to collaborators Oct 11, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants