CI/CD
Trigger Playwright test reruns in CircleCI — only the failed tests, not the whole suite
Tynkr integrates with CircleCI to trigger selective test reruns directly from a pipeline step. Instead of rerunning the full test suite when one workflow fails, Tynkr identifies the failed steps and reruns only those — cutting rerun time significantly and keeping your pipeline fast.
What you can do
- Rerun only failed Playwright tests from a CircleCI pipeline step
- Trigger Tynkr workflows as a CircleCI job on every deployment
- Get Tynkr execution results back into the CircleCI pipeline as test artifacts
Common questions
How does Tynkr work with CircleCI?
Tynkr can be triggered from a CircleCI pipeline step via API. Your pipeline calls the Tynkr API to start a workflow run, polls for completion, and receives the pass/fail result as a pipeline status. Failed workflows can trigger selective reruns without rerunning the full CircleCI job.