Artifacts

Test reporters capture files produced during test execution — screenshots, videos, trace files, HTML snapshots, terminal output, and any other artifacts — and include them in the Flakiness report. The Report Viewer displays these inline alongside test results.

Storage and quotas

Every uploaded artifact counts toward your organization’s storage quota, which is defined by the active organization plan. Once the quota is full, new uploads to any project in the organization will fail until storage is freed or the plan is upgraded.

Running out of space?

A few options:

• Most of the space is usually consumed by large artifacts like Playwright traces and videos. Flakiness.io supports a dedicated retention period for attachments, so you can keep test results for longer while letting heavy artifact files expire sooner. See Data Retention.
• Upgrade to a plan with a larger quota.
• Reach out to support@flakiness.io and we’ll be happy to negotiate higher limits for your organization.

Flakiness reporters auto-compress compressible artifacts before upload to save storage, and all artifacts are encrypted at rest.

The Flakiness JSON report itself is stored as an artifact, so the report’s own data also contributes to the quota. On average, 1 GB fits about 13 million test results.

How much fits in 1 GB?

Even with no screenshots, videos, or other captured files — just the test data itself — the budget goes a long way. A project with 1,000 tests run 100 times per day produces 100,000 results per day. About 100 days of that data fits in 1 GB.

Attribution to test steps

Where the test runner exposes step information (for example, Playwright Test’s test.step or built-in action steps), attachments are attributed to the step that produced them rather than the test as a whole. Failure context becomes much easier to scan: the screenshot taken right before an assertion failed sits next to the assertion, not at the bottom of the run.

For runners that don’t emit step events, attachments are attached to the test.

Attachment Types

Flakiness.io supports several attachment types natively.

HTML

HTML attachments render inside a sandboxed <iframe> in the Report Viewer, so you can inspect the exact markup produced at test time. This is useful for DOM snapshots, rendered email templates, or any other HTML artifact the test captured.

Image

Images are displayed inline with the test result. When multiple images are present, they are laid out in a flex-wrapped gallery.

Image Diffs

When a visual comparison test fails, reporters typically produce three images: expected, actual, and diff. The Report Viewer auto-detects these by naming convention (name-expected.png, name-actual.png, name-diff.png) and presents them in a tabbed interface with four views:

• Diff — the computed difference image
• Actual — what the test produced
• Expected — the baseline reference
• Slider — an interactive image comparer that lets you drag between actual and expected

Video

Video attachments render as inline <video> elements with playback controls.

Playwright Trace

Playwright traces receive special treatment. When the @flakiness/playwright reporter captures a trace file, the Report Viewer displays it with a dedicated thumbnail and a link that opens the trace in the Playwright Trace Viewer, which gives you a full timeline of actions, network requests, DOM snapshots, and console logs for that test.

Traces are automatically detected when an attachment has the name trace.

Terminal Logs

Reporters capture stdout and stderr output during test execution. Each test run shows its terminal output in a dedicated section with log entries displayed in chronological order.

Stderr entries are highlighted with a red background to make them visually distinct.

ANSI escape sequences are rendered as styled text, so colors, bold, and other formatting match what you’d see in your terminal.

Miscellaneous Files

Any other attachment type (logs, JSON files, data exports) is shown as a downloadable link.