Nightly e2e run with morning report
Run the full end-to-end suite every night at 2am and wake up to a digest of failures with screenshots, suspect commits, and a flakiness verdict per test.
/schedule every day at 2am, run the full e2e suite against the staging build; for each failure, attach the trace or screenshot, list the commits since the last green run, and say whether the failure looks flaky or real; post the digest to e2e-reports/ as a dated markdown file
claude-code · codex
Implementation note
Nightly cadence catches integration breakage without slowing daytime CI. The flaky-or-real verdict is the part that saves you triage time each morning.
More testing loops
Watch tests while you work
A passive watchdog loop that reruns your test suite every 15 minutes and surfaces failing tests with their error output.
/loop 15m run the test suite, and if anything fails, show me the failing tests and the error output
testinglow risk
Kill flaky tests
Run your test suite repeatedly, collect every intermittent failure, and fix or quarantine flaky tests until you get five consecutive green runs.
/loop run my test suite 20 times, collect every intermittent failure, fix or quarantine the flaky ones, and don't stop until you get 5 consecutive fully-green runs
testinghigh risk
Make all tests pass
Implement remaining code and run tests repeatedly until the full suite passes.
/goal finish the implementation and make all tests pass
testingmedium risk