-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[test optimization] [SDTEST-996] Add instructions for test session name #26807
[test optimization] [SDTEST-996] Add instructions for test session name #26807
Conversation
Preview links (active after the
|
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.
So are we deprecating DD_ENV as well?
not deprecating, but I'd say we don't need to put in the onboarding |
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.
Can you include somewhere why this would be of interest or when to use it? e.g. if your tests have dynamically generated names, giving a test session name will allow you to have better flaky test detection and test history
It would also be nice to include a section in Troubleshooting with this problem, and then point to this new solution
that's a good idea. I've just added it |
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.
Looks great! Just left two minor suggestions.
Co-authored-by: Brett Blue <[email protected]>
thanks! I applied them 😄 |
/merge |
Devflow running:
|
What does this PR do? What is the motivation?
Let users know about test session name and how they can use it.
Merge instructions
Merge readiness:
Merge queue is enabled in this repo. To have it automatically merged after it receives the required reviews, create the PR (from a branch that follows the
<yourname>/description
naming convention) and then add the following PR comment:Additional notes
https://docs-staging.datadoghq.com/juan-fernandez/test-session-name-SDTEST-996/tests/setup/javascript/?tab=ciproviderwithautoinstrumentationsupport#dd_test_session_name