---
title: CI Insights
description: Optimize your CI run time, catch flaky tests, and give developers actionable insights so your team ships code faster.
---

import { Image } from "astro:assets"
import JobsScreenshot from "../images/ci-insights/jobs.png"
import TestsScreenshot from "../images/ci-insights/tests.png"
import Docset from '../../components/DocsetGrid/Docset.astro';
import DocsetGrid from '../../components/DocsetGrid/DocsetGrid.astro';

CI Insights helps you monitor your pipelines, detect flaky tests and jobs, and optimize
your CI efficiency. This guide walks you through enabling CI Insights via
GitHub and covers basic configuration steps.

> First time here? Follow these 3 steps to see data fast:
> 1. Install the Mergify GitHub App on a repo with existing CI.
> 2. Ensure your tests produce a supported format (JUnit XML, pytest, Jest, etc.) – pick a framework below if needed.
> 3. Re-run a workflow (or push a trivial commit) then refresh this page to view jobs & tests.

## Understanding CI Insights

### Components

CI Insights provides monitoring and analysis for two key components of your CI pipeline:

#### Jobs

Jobs are the individual tasks that run as part of your CI pipeline (e.g.,
build, test, deploy steps). CI Insights tracks job-level metrics and health
status.

<Image src={JobsScreenshot} alt="CI Insights Jobs" />

#### Tests

Tests are the individual test cases that run within your test suites. CI
Insights captures detailed test-level data to help identify problematic test
cases.

<Image src={TestsScreenshot} alt="CI Insights Tests" />

### Flaky Detection

CI Insights automatically detects flaky behavior in both jobs and tests using the same criteria:

A **flaky job** or **flaky test** is one that has 2 different conclusions on
the same SHA1. For example, if a job or test runs twice on the same commit and
once fails while the other succeeds, it's considered flaky because the outcome
is not consistent with the same code.

To set up systematic flaky test detection in your CI pipeline, see our
dedicated [Flaky Test Detection guide](/ci-insights/flaky-test-detection).

## CI Setup Guides

Select your CI system below to enable CI Insights and configure flaky test detection.

<DocsetGrid>
  <Docset
    title="GitHub Actions"
    path="/ci-insights/setup/github-actions"
    icon="simple-icons:githubactions"
  >
    Enable CI Insights & flaky test detection for GitHub Actions.
  </Docset>
  <Docset
    title="Jenkins"
    path="/ci-insights/setup/jenkins"
    icon="simple-icons:jenkins"
  >
    Enable CI Insights & flaky test detection for Jenkins.
  </Docset>
</DocsetGrid>

## Test Framework Configuration

CI Insights supports many test frameworks and captures test-level data from them.
Each framework requires a quick setup to ensure test results are parsed and uploaded properly.

Refer to the dedicated page for your specific framework to configure and verify your test output.

<DocsetGrid>
  <Docset
    title="Cypress"
    path="/ci-insights/test-frameworks/cypress"
    icon="simple-icons:cypress"
  >
    Integrate Cypress with CI Insights.
  </Docset>
  <Docset
    title="Go"
    path="/ci-insights/test-frameworks/golang"
    icon="simple-icons:go"
  >
    Integrate Go with CI Insights.
  </Docset>
  <Docset
    title="Jest"
    path="/ci-insights/test-frameworks/jest"
    icon="simple-icons:jest"
  >
    Integrate Jest with CI Insights.
  </Docset>
  <Docset
    title="JUnit"
    path="/ci-insights/test-frameworks/junit"
    icon="simple-icons:junit5"
  >
    Integrate JUnit with CI Insights.
  </Docset>
  <Docset
    title="Minitest"
    path="/ci-insights/test-frameworks/minitest"
    icon="simple-icons:ruby"
  >
    Integrate Minitest with CI Insights.
  </Docset>
  <Docset
    title="MSTest"
    path="/ci-insights/test-frameworks/mstest"
    icon="simple-icons:dotnet"
  >
    Integrate MSTest with CI Insights.
  </Docset>
  <Docset
    title="NUnit"
    path="/ci-insights/test-frameworks/nunit"
    icon="simple-icons:dotnet"
  >
    Integrate NUnit with CI Insights.
  </Docset>
  <Docset
    title="Pest"
    path="/ci-insights/test-frameworks/pest"
    icon="simple-icons:php"
  >
    Integrate Pest with CI Insights.
  </Docset>
  <Docset
    title="PHPUnit"
    path="/ci-insights/test-frameworks/phpunit"
    icon="simple-icons:php"
  >
    Integrate PHPUnit with CI Insights.
  </Docset>
  <Docset
    title="Playwright"
    path="/ci-insights/test-frameworks/playwright"
    icon="simple-icons:playwright"
  >
    Integrate Playwright with CI Insights.
  </Docset>
  <Docset
    title="Pytest"
    path="/ci-insights/test-frameworks/pytest"
    icon="simple-icons:pytest"
  >
    Integrate Pytest with CI Insights.
  </Docset>
  <Docset
    title="RSpec"
    path="/ci-insights/test-frameworks/rspec"
    icon="simple-icons:ruby"
  >
    Integrate RSpec with CI Insights.
  </Docset>
  <Docset
    title="Rust"
    path="/ci-insights/test-frameworks/rust"
    icon="simple-icons:rust"
  >
    Integrate Rust with CI Insights.
  </Docset>
  <Docset
    title="TestNG"
    path="/ci-insights/test-frameworks/testng"
    icon="simple-icons:testinglibrary"
  >
    Integrate TestNG with CI Insights.
  </Docset>
  <Docset
    title="Vitest"
    path="/ci-insights/test-frameworks/vitest"
    icon="simple-icons:vitest"
  >
    Integrate Vitest with CI Insights.
  </Docset>
</DocsetGrid>