Analytics

Monitor your project's test health at a glance with summary cards, trend charts, and flaky test detection — all calculated automatically from your run history.

Overview

The Analytics dashboard (the Project Dashboard page) provides a comprehensive view of your project's testing health. It aggregates data from all test runs in a project and presents it through summary cards, a 30-day trend chart, flaky test detection, and a test health breakdown.

To access the dashboard, navigate to your project's test list and click the Dashboard link. The dashboard loads data from three API endpoints: summary, trends, and flaky tests.

Summary Cards

The top of the dashboard displays four summary cards that give you an immediate snapshot of your project's health:

The summary endpoint returns all four values in a single response:

{
  "totalTests": 24,
  "totalRuns": 156,
  "passRate": 87,
  "avgDuration": 4523,
  "testStatusCounts": {
    "passing": 18,
    "failing": 4,
    "noRuns": 2
  }
}

Trend Chart

The trend section displays a 30-day stacked bar chart showing daily pass and fail counts. Each bar represents a single day, with green segments for passed runs and red segments for failed runs. A pass rate percentage is calculated for each day.

The trend data is fetched from the trends endpoint, which accepts an optional days query parameter (defaults to 30):

GET /api/projects/:projectId/analytics/trends?days=30

The response contains a dailyStats array sorted chronologically. Each entry includes:

{
  "dailyStats": [
    {
      "date": "2026-01-21",
      "totalRuns": 12,
      "passed": 10,
      "failed": 2,
      "passRate": 83
    },
    {
      "date": "2026-01-22",
      "totalRuns": 8,
      "passed": 8,
      "failed": 0,
      "passRate": 100
    }
  ]
}

The chart groups runs by the date portion of their createdAt timestamp (the YYYY-MM-DD part). Days with no runs are omitted from the array. The pass rate per day is calculated as Math.round((passed / totalRuns) * 100).

Flaky Test Detection

The flaky tests section identifies tests with inconsistent results. A flaky test is one that alternates between passing and failing across recent runs, which makes it unreliable and difficult to trust.

Flakiness Algorithm

QA Studio calculates a flakiness score for each test using the following algorithm:

flakinessScore = alternations / (recentRuns.length - 1)

Here are some example scores to illustrate:

Flaky Test Display

The flaky tests list is sorted by flakiness score in descending order (most flaky first). Each entry shows:

• Test name — links to the test in the builder
• Flakiness score — the numerical score (0.00 to 1.00)
• Recent result dots — a row of colored circles representing the last 10 runs: green dots for passed runs and red dots for failed runs

{
  "flakyTests": [
    {
      "testId": "abc123",
      "testName": "Login Flow",
      "flakinessScore": 0.67,
      "recentResults": [
        { "status": "passed", "createdAt": "2026-02-20T10:00:00Z" },
        { "status": "failed", "createdAt": "2026-02-19T10:00:00Z" },
        { "status": "passed", "createdAt": "2026-02-18T10:00:00Z" },
        { "status": "passed", "createdAt": "2026-02-17T10:00:00Z" }
      ]
    }
  ]
}

Test Health Breakdown

The summary endpoint also returns a testStatusCounts object that categorizes every test in the project into one of three groups based on its most recent run:

The breakdown is displayed visually on the dashboard, often as a pie chart or segmented bar, giving you a quick understanding of how many tests are healthy versus needing attention.

Accessing the Dashboard

To open the analytics dashboard:

API Endpoints

The analytics feature exposes three REST endpoints, all scoped to a specific project: