Flakytests/billing.spec.js

confirms a declined card after the customer re-enters CVC

chromium · 20 runs analysed · 7 failed · 14 pass/fail flips · locator rule matched

What happened. Deterministic findings across 20 CI runs — the same answer every time. No AI involved yet.

Runs analysed

13 passed · 7 failed

Failure rate

35%

Failed in 7 of 20 runs

Recovered on retry

7/7

Failed runs that passed when retried

Pass/fail flips

Outcome changed between runs

Execution history

Outcome changed 14 times across 20 runs

Passed (13)Failed (7)Oldest run on the left

Failure pattern

Element / selector

Element was present but not ready for interaction when clicked

Playwright auto-waits for elements to be stable, visible, enabled, and not covered. The click timed out because one of these conditions was not met within the timeout.

Similar failures

2 other tests show a similar failure pattern

Browsers

chromium· this failurefirefoxwebkit

Error detail

Error message

locator.click: Timeout 15000ms exceeded.

Call log

  - waiting for getByTestId('confirm-payment')
  - locator resolved to <button data-testid="confirm-payment" disabled>…</button>
  - element is not enabled - waiting…

Code location

tests/billing.spec.js:74:32

Stack trace

Error: 
    at Object.confirmPayment (tests/billing.spec.js:74:32)
    at tests/billing.spec.js:69:5

Failure behaviour

14 transitions between pass and fail across 20 runs
Outcome alternates across runs — no stable pattern detected

How certain the analyzer is

14 pass/fail transitions in history (high noise)
Mixed results — recovered on retry in at least one run
2 other test(s) share this failure fingerprint (some corroboration)

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.