A passing check is a claim about one run, not proof that the behaviour is right. These articles cover test-first work with an agent, telling useful tests from coverage, stopping agents from weakening tests to make them pass, confirming that reported checks actually ran, and handling flaky tests without teaching agents to ignore failures.
5 articles
Reproduce each intermittent failure under recorded conditions, give quarantined tests an owner and a list of what they block, tell agents to report and stop instead of retrying, and close an entry only when the same reproduction no longer fails.
Treat "all checks pass" as a claim about one run: ask for the command, directory, commit, exit status and test count, rule out empty, cached, masked and timed-out results, and accept only a pass on the commit you merge.
Treat every edit that changes what a test expects as a change to the requirement: find it in the diff, decide whether the test or the code is wrong, have the requirement's owner approve a changed expectation, and prove the…
Coverage shows which lines ran, not whether a test would notice them doing the wrong thing. Break the behaviour on purpose, read what each test asserts, add refusals and state checks, and use mutation testing on changed code.
Write the expected behaviour before any code exists, read why the first test failed, lock the tests while the agent implements, and ask for a record of both runs before you accept the change.
