Naming Runs

You'll need

• Getting Started complete

You'll have

• runs appearing on the dashboard with clear, human-readable titles like “Unit Tests” or “E2E Tests”.

Run title

A run title is a human-readable label for a single run. It’s purely cosmetic: it shows up on the Runs page and when you open an individual run, but it doesn’t affect grouping, history, or any analytics. Unlike environment, two runs with different titles but the same environment still live in the same history.

How it works

By default, runs have no title. On the dashboard they show up labeled by commit SHA, time, and environment — which is fine most of the time.

You set a title explicitly when you want runs to be distinguishable at a glance — typically when multiple CI jobs on the same commit run different test suites (unit + e2e, say).

Setting the title

Three options, in order of convenience:

• FLAKINESS_TITLE environment variable — supported by all official reporters. Set it in the CI job and the reporter attaches it to the report.

  export FLAKINESS_TITLE="Unit Tests"

• CLI flag — when uploading or converting directly: flakiness upload --title "My Suite" ./flakiness-report or flakiness convert-junit --title "My Suite" ./test-results.

• Programmatic (reporter config) — each reporter exposes its own config API. Check your runner’s page under Test Runners for the exact option name.

Example: unit + e2e in one commit

The example below uses GitHub Actions and Playwright Test. The general pattern applies to any CI/runner.

.github/workflows/tests.yml

jobs:
  unit:
    runs-on: ubuntu-latest
    permissions: { contents: read, id-token: write }
    env:
      FLAKINESS_TITLE: Unit Tests
    steps:
      - uses: actions/checkout@v4
      - run: npm ci
      - run: npx playwright test tests/unit

  e2e:
    runs-on: ubuntu-latest
    permissions: { contents: read, id-token: write }
    env:
      FLAKINESS_TITLE: E2E Tests
    steps:
      - uses: actions/checkout@v4
      - run: npm ci
      - run: npx playwright test tests/e2e

Both jobs run on the same commit and upload to the same project. Each sets FLAKINESS_TITLE, so the dashboard shows both runs for that commit labeled Unit Tests and E2E Tests.

Related

• Configuring Environments — when you want the runs in separate histories rather than labeled within the same one.