List quarantined tests
Returns the tests quarantined for the repository the OIDC token was issued to, so a CI step can keep their failures from failing the build. For Playwright, pass playwright_grep_invert to --grep-invert.
github_oidcAuthorizationBearer <token>A GitHub Actions OIDC token requested with the audience coderhelm, from a workflow run of a repository connected to your team.
The quarantined tests.
application/json- response
The tests quarantined for the calling repository.
playwright_grep_invert*stringA pattern for Playwright's --grep-invert that skips them; empty when none are.
"checkout applies a discount code"tests*array<>Every quarantined test.
curl -X GET 'https://api.coderhelm.com/webhooks/ci/tests/quarantine' \ -H "Authorization: Bearer $OIDC_TOKEN"{ "playwright_grep_invert": "checkout applies a discount code", "tests": [ { "file": "e2e/checkout.spec.ts", "framework": "playwright", "id": "e2e/checkout.spec.ts::checkout › applies a discount code", "project": "chromium", "title": "checkout › applies a discount code" } ]}Jira webhook POST
For a plain Jira webhook, when the CoderHelm Jira app can't be installed. The URL holds a token generated for your team on the Jira page of the dashboard. If you also generated a secret there, every request must carry `X-Hub-Signature`: `sha256=` and the hex HMAC-SHA256 of the raw body, keyed with that secret. Jira Cloud signs webhooks this way when you set the secret on the webhook; a Jira automation can send the header itself.
Upload a test report POST
Takes one test report from a CI job whose results never reach GitHub (a device farm, say), signed with the job's GitHub Actions OIDC token instead of a CoderHelm secret. Request the token with the audience `coderhelm`. CoderHelm checks it was issued for a workflow run of a repository connected to your team with E2E results turned on, then reads the report like one from GitHub: flaky tests, failure groups and quarantine.