Flaky Test
Casefile

Playwright reporter / local evidence

Find the first thing that changed.

Casefile turns intermittent retries into compact failure signatures—then marks the earliest network or DOM divergence. No upload. No AI guesses. Just comparable evidence.

Install the reporterOpen a sample casefile
  • 01 Normalize timing noise
  • 02 Cluster matching symptoms
  • 03 Export one static file
Three Playwright retry evidence strips converging on one red fault marker on a blueprint drafting sheet
PLATE 01 Retry evidence converges on the first divergence.

One pass through the evidence

From rerun pile to diagnosis

  1. A

    Collect attempts

    The reporter uses Playwright’s documented callbacks and keeps artifacts on disk.

  2. B

    Match symptoms

    Volatile ports, IDs, timestamps, line numbers, and retry durations stop splitting the same failure.

  3. C

    Mark divergence

    An optional page probe finds the first changed request, response, console error, or DOM landmark.

Working field viewer

Inspect a real casefile shape

This sample contains three attempts of a seeded checkout test. Load a local casefile.json to inspect yours; the file never leaves this browser.

Showing the built-in sample.

CASE / FC-7K2M9Q

Checkout submit waits forever

FLAKY
2 / 3 attempts

First divergence / event 07

Baseline200 · POST /api/payment
Failed retry503 · POST /api/payment
NETWORK2 OCCURRENCESHEADERS REDACTED

Two-minute setup

A reporter, not another platform.

Add one reporter entry. The result is a portable report your CI can retain like any other artifact.

playwright.config.ts
reporter: [
  ['line'],
  ['flaky-test-casefile', {
    outputDir: 'casefile-report'
  }]
]

Evidence stays on your runner.

No telemetry or account. Traces and videos are excluded by default. Credential headers are redacted, and configured masks are baked into exported PNG pixels.

Read privacy details