Send scenario name and git branch to saucelabs #26063
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A couple of changes to make the SauceLabs dashboard more useful to us!
Tests are now tagged with their branch name, so you can filter to tests for a particular branch...
...or verify from test metadata which branch a test came from:
We now push the full scenario name for each test instead of just the feature name, disambiguating cases like this:
Into this:
This will also make the new "Test History" feature a lot more useful - right now it rolls up all the results from all the scenarios in a single feature. Having them broken out may help us diagnose issues faster.