-
Notifications
You must be signed in to change notification settings - Fork 424
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
chore(ci_visibility): add quarantine support to pytest #11615
chore(ci_visibility): add quarantine support to pytest #11615
Conversation
BenchmarksBenchmark execution time: 2024-12-20 12:17:07 Comparing candidate commit e419523 in PR branch Found 1 performance improvements and 0 performance regressions! Performance is the same for 393 metrics, 2 unstable metrics. scenario:iast_aspects-ospathdirname_aspect
|
…raujo/SDTEST-1255/quarantine
|
…raujo/SDTEST-1255/quarantine
…raujo/SDTEST-1255/quarantine
…raujo/SDTEST-1255/quarantine
Datadog ReportBranch report: ✅ 0 Failed, 922 Passed, 546 Skipped, 16m 53.61s Total duration (55m 44.02s time saved) |
This PR adds preliminary support for quarantining tests in pytest.
The API to query which tests are quarantined does not exist yet on the backend side, and the final form of that API is still to be defined, so the code dealing with the API has been moved to a separate PR (#11770). Currently, we can mark tests as quarantined by manually adding the
test.quarantine.is_quarantined
tag to the test with a pytest decorator:For testing purposes, the environment variables
_DD_TEST_FORCE_ENABLE_QUARANTINE
and_DD_TEST_FORCE_ENABLE_ATR
have been added to enable quarantine and ATR without depending on the backend.The test reporting looks like below. Errors and logs for quarantined tests are not printed.
Checklist
Reviewer Checklist