Le Diagnostiqueur de Test Flaky : Transformez les Échecs CI Intermittents en Hypothèses de Cause Racine Classées
Pourquoi ce prompt est important
Flaky tests that get ignored quietly erode trust in the entire suite: engineers start re-running failed CI jobs by reflex instead of reading why they failed, which means a genuine regression can slip through disguised as 'oh, that test is just flaky.' Teams that let flaky tests accumulate past a small fraction of the suite typically see their mean time to detect real production bugs get significantly worse, because the signal-to-noise ratio of CI failures has collapsed.
À quoi nous l'utilisons
You're a backend engineer and your team's CI pipeline has a test that fails about 1 in 15 runs with no code changes. Nobody wants to spend a sprint chasing it, so it's been ignored for three weeks -- and now two more tests in the same suite are starting to flake too.
Prompt
Act as a senior test infrastructure engineer who specializes in diagnosing intermittent, non-deterministic CI test failures ("flaky tests").
CONTEXT:
- Test name / file: [TEST NAME OR FILE PATH]
- Test framework and language: [e.g. "pytest, Python" or "Jest, TypeScript"]
- Failure frequency: [e.g. "1 in 15 runs" or "roughly once a week, no clear pattern"]
- Failure logs from 3-5 recent failed runs (paste full stack traces / error output, not summaries): [PASTE FAILURE LOGS HERE, SEPARATED BY RUN]
- Recent changes to the test or the code it covers, if known: [DESCRIBE OR PASTE RELEVANT DIFF, OR WRITE "NONE KNOWN"]
- What the test is actually verifying (in plain English): [ONE-SENTENCE DESCRIPTION OF TEST INTENT]
TASK:
Analyze the failure patterns across the provided logs and produce ranked root-cause hypotheses. Consider these common flaky-test categories and rule each in or out based on the evidence: timing/race conditions, shared state or test pollution from other tests, external dependency instability (network, third-party API, database), resource exhaustion (memory, connection pool, file handles), non-deterministic test ordering, and environment differences between CI and local runs.
CONSTRAINTS:
- Do not simply conclude "the test is flaky" without committing to at least 2 specific, falsifiable hypotheses ranked by likelihood
- Every hypothesis must cite specific evidence from the pasted logs -- if the logs don't support a hypothesis, don't include it
- Clearly distinguish between issues safe to quarantine now and investigate later, versus issues that likely mask a real production bug and must be fixed before quarantining
- If the provided logs don't contain enough information to diagnose confidently, say exactly that, and specify precisely what additional logging or instrumentation to add before the next failure
OUTPUT FORMAT:
1. A ranked table: Hypothesis | Confidence (High/Medium/Low) | Evidence From Logs | Suggested Fix
2. A single recommended immediate action: Quarantine and Investigate Later / Must Fix Before Quarantining / Needs More Data First
3. If "Needs More Data First": the exact logging statements or CI configuration change to add so the next failure captures what's missingRésultat
Diagnosis: test_checkout_confirms_payment_status (pytest, Python)
Failure frequency: ~1 in 12 CI runs, no clear time-of-day pattern.
| Hypothesis | Confidence | Evidence From Logs | Suggested Fix |
|---|---|---|---|
| Race condition between async payment webhook handler and the assertion checking order status | High | All 3 failed runs show the assertion firing at order.status == 'pending' rather than 'confirmed' -- the webhook handler logs show it completing 40-180ms AFTER the assertion ran in 2 of 3 failures | Replace the fixed 100ms sleep before the assertion with an explicit poll-until-status-or-timeout helper (max 2s), and add a log line at the exact moment the webhook handler acquires its DB lock |
| Shared test database state from a preceding test in the same suite | Medium | One failure log shows an order ID that doesn't match the expected sequence, suggesting a prior test's order wasn't cleaned up -- but this only appears in 1 of 3 logs, so it's a contributing factor, not the primary cause | Add explicit teardown assertion verifying zero leftover orders before this test starts; run this test in isolation for 20 iterations to confirm whether it still flakes without the suite context |
| Third-party payment sandbox API latency spike | Low | No log evidence of elevated response times from the payment sandbox in any of the 3 failures -- ruled out based on available data | N/A -- not supported by current evidence |
Recommended Immediate Action: Must Fix Before Quarantining
This is not safe to quarantine. The race condition hypothesis is high-confidence and points to a genuine bug: the webhook handler and the test assertion have no synchronization mechanism between them, which means the SAME race condition could cause a real customer to see a stale "pending" payment status in production under load. Quarantining this test would hide a real timing bug, not just a test artifact. Fix the polling logic first; if the test still flakes after that fix, investigate the shared-state hypothesis as the secondary cause.
Chaque équipe d'ingénierie accumule des tests flaky, et chaque équipe développe la même mauvaise habitude en réponse : quelqu'un relance, le test passe la deuxième fois, et tout le monde passe à autre chose sans jamais comprendre pourquoi il a échoué la première fois. Cette habitude est corrosive. Une fois qu'une équipe commence à traiter les échecs CI comme du bruit par défaut, une régression réelle finit par se cacher dans ce bruit et est déployée en production.
Ce prompt impose une discipline différente. Au lieu d'accepter un vague diagnostic « c'est flaky », il exige que le modèle lise les logs d'échec réels de plusieurs exécutions et s'engage sur au moins deux hypothèses falsifiables spécifiques — classées par confiance, chacune étayée par une ligne de preuve précise des logs plutôt qu'une supposition générique. Les causes racines les plus courantes sont les conditions de course (Race Conditions), l'état partagé des tests, l'instabilité des dépendances externes, l'épuisement des ressources et la dérive environnementale entre CI et local ; le prompt parcourt chacune systématiquement au lieu de sauter sur celle qui semble la plus familière.
La partie la plus utile de la sortie est le verdict que la plupart des équipes sautent complètement : est-il sûr de mettre ce test en quarantaine pour le revoir plus tard, ou le flaky révèle-t-il en fait un vrai bug qui pourrait affecter la production dans les mêmes conditions ? Une condition de course entre un gestionnaire de Webhook asynchrone et une vérification de statut, par exemple, n'est pas qu'un problème de test — c'est le même bug qu'un vrai client pourrait rencontrer sous charge. Mettre ce test en quarantaine cacherait un problème de production derrière une coche verte. Faire cette distinction correctement, à chaque fois, est ce qui sépare les équipes avec un signal CI fiable des équipes qui ont silencieusement cessé de faire confiance à leur propre suite de tests.