← Overview
Consistently failingtests/billing.spec.js
generates the monthly invoice for an enterprise plan
chromium · 20 runs analysed · 20 failed · network rule matched
What happened. Deterministic findings across 20 CI runs — the same answer every time. No AI involved yet.
Runs analysed
20
0 passed · 20 failed
Failure rate
100%
Failed in 20 of 20 runs
Recovered on retry
None
No retry recovery observed
Pass/fail flips
0
Outcome never changed
Execution history
Every one of the 20 runs failed1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
Passed (0)Failed (20)Oldest run on the left
Failure pattern
Network
Internal server error — the backend encountered an unexpected condition
The backend server threw an unhandled error. This is a server-side issue that requires investigation of backend logs and service health.
Similar failures
2 other tests show a similar failure pattern
Browsers
chromium· this failurefirefoxwebkit
Error detail
Error message
POST /api/v2/billing/invoices responded 500 Internal Server Error — proration ledger returned a negative line item
Call log
- the invoice engine failed to reconcile a mid-cycle plan downgrade
Code location
tests/billing.spec.js:151:35
Stack trace
Error:
at tests/billing.spec.js:151:35Failure behaviour
- All 20 runs failed
- Failure reproduced consistently — not flaky
How certain the analyzer is
- History is fully consistent — every run had the same outcome
- Every run failed — no recovery observed
- 2 other test(s) share this failure fingerprint (some corroboration)
- 20+ runs analyzed with a consistent pattern (strong statistical basis)
Not captured for this failure: retry behaviour.
The rules established the facts. Now ask what they mean.
The deterministic engine says what happened. AI weighs those signals against each other to attribute the failure — and may disagree, hedge, or decline.