Runs the repository's test suite five times on the same commit, finds tests whose results are not deterministic, investigates why, and files one ticket per run listing every flaky test with its cause. Set your repository on the Clone step after importing.
- Identifier
flaky-test-detector- Version
- 1.0.2
- Steps
- 4
- Triggers
- 1
- ci
- testing
- flakiness
- scheduled
- automated
When it runs
schedule.weekly- Schedule
- Every Sunday at 03:00 UTC
0 3 * * 0 - Timezone
- UTC
The pipeline
The graph below is the one the workflow opens with in the builder — same steps, same layout, drawn on the same canvas. The run playing through it is a simulation; the branches and conditions are real.
- 01Weekly Schedule (Sunday 03:00 UTC)
triggerThe event that starts the run.
- 02Clone Repository ⚠️ SET YOUR REPO
git.cloneShallow-clones the repository at the right ref.
- 03Detect Flaky Tests
agent.runOne agent works the task with its toolkit.
- 04File Flaky Test Ticket
ticket.createOpens a ticket on the connected tracker.
Branches
- flake_agent to file_ticket: runs only if outputs.flake_agent.message contains RESULT: FINDINGS
The agent
Flaky Test Detector
- Base type
- Senior Developer
- Temperature
- 0.2
- Max iterations
- 50
- Tools
- 5
Filesystem · 2
read_fileRead File · readlist_dirList Directory · read
Terminal · 1
run_terminal_cmdRun Terminal Command · write
Code search · 1
code_searchCode Search · read
Status · 1
update_statusUpdate Status · write
Related playbooks
Fix CI
Reads CI failure logs, locates the root cause in the diff, and pushes a fix.
Write Tests on Command
Comment /write-tests on a PR and an agent writes, runs, and pushes tests to the branch.
CI Duration Regression Watch
Weekly analysis of CI durations that identifies regressed jobs, opens the workflow definition, and proposes a specific cause and fix.