Add --test-suite option to record session #861
Merged
Conversation
This file contains hidden or 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
9736500 to
f8acdb1
Compare
This comment has been minimized.
This comment has been minimized.
f8acdb1 to
a34230e
Compare
|
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.
Background
When we introduced a workspace, we expect that customers use a workspace per test suite. However, we noticed that some customers use a single workspace with multiple test suites. Mixing test suites in a workspace make many features less valuable. For example, trends, test issue triages, test session list, and unhealthy tests are affected. It’s natural to promote “test suites” as a first class data model on Launchable so our customers can sort, filter, and analyze data based on test suites in a workspace.
Change
--test-suiteto specify a name of test suite executed in a test session.