Skip to content
Flakiness.io

Overview

The project dashboard is where you explore your test data. It has four views, each documented on its own page:

  • Tests — every test’s state for the selected day, with status cards and the tests table.
  • History — the branch’s commit feed with per-commit test stats and trends.
  • Runs — every uploaded run, newest first. Opening one shows the Single Run report.
  • Pull Requests — PRs with their check outcomes and regressions.

When you navigate to a project, flakiness.io shows you the default test report in the Tests view. This is an aggregated status view across all environments and all tests of the project’s default branch, for a single day – the day of the last commit, in the project’s timezone.

The default test report is also what powers other features:

Once on this page, you can navigate to a different day, environment, or branch. The controls below are shared across all dashboard views.

Hover or click a numbered region on the screenshot to jump to its explanation, or use the “On this page” outline on the right.

Flakiness.io project dashboard with annotated regions

Branch selector

Section titled “Branch selector”

Defaults to the repository’s main branch and lets you switch to any other branch. The branch defines the history window used throughout the dashboard; all testing data is scoped to the selected branch.

Scoping results to a single branch is essential to keep statistics and health signals unaffected by on-going development and testing on other branches. For example, a test that passes on main but fails on a feature branch is a regression on that branch, but not on main.

Branch Selector
  1. Branch filter — substring-matching filter over branch names.
  2. Recent branches — the 5 most recently modified branches that match the filter.
  3. Last Commit — the branch’s most recent commit, including committer and timestamp.

Environment selector

Section titled “Environment selector”

Shows every testing environment by default. You can filter by environment category, or pick a single environment (operating system, browser, or custom environment) to narrow results.

Environment Selector
  1. Categories — environments are grouped by category, usually by test runner. A project with Vitest front-end tests and pytest back-end tests will have two categories here: vitest and pytest.
  2. Category Environments — every environment inside the selected category.

Test Health Calendar

Section titled “Test Health Calendar”

A heat-map of last 3 months. Each cell is one day, coloured by its aggregated status by the end of the day: green (passed), yellow (flaked), red (failed & regressed). Click a cell to jump to that day’s report.

Test Health calendar
  1. Calendar view — opens a date picker to jump to any day.
  2. Range selector — sets the report range. The dashboard shows every test that ran at least once within the range, and each row reports the test’s last result inside the range.
  3. Last tested — jumps to the most recent day with test activity.
Section titled “FQL search”

Filters and slices the tests table using Flakiness Query Language (FQL).

Common filters:

  • click — tests whose name, suite, or file contains click
  • s:flaked — tests by status
  • f:login.spec.ts — tests by file name
  • @skip — tests by annotation
  • #smoke — tests by tag
  • duration>1s — tests by last-run duration
  • flip>0% — tests by flip rate
  • $timeout — tests whose error text contains timeout