> For the complete documentation index, see [llms.txt](https://argos-ci.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://argos-ci.com/docs/learn/reliability-and-flakiness/flaky-test-detection.md).

# Flaky test detection

Argos flags unstable tests so you can decide with confidence. See a flaky badge next to every changed test and dive into detailed history and stability scores on a dedicated test page

![Flaky indicator next to a test change](/files/c125950c0832cffbd468a956b1b0c610182a81a1)

*Example of the flaky indicator in a build review*

### View flaky indicators in your build review

1. Open any build in Argos
2. Spot the flaky badge beside each changed test
3. Hover over the badge to see details about the test's stability

### Explore the test page

By clicking on the flaky badge, you will be taken to the test page where you can see the full history of the test and its stability score.

![Test page showing history and flaky score](/files/71e19ef36f0c6e07dc139edd7a967dad203c6454)

*A sample test page with history timeline and score*

On the test page you will find:

* Timeline of every change that affected the test
* Stability graph showing pass rate over time
* Flakiness score from 0 to 100, summarizing the test's stability and consistency
* List of changes happened to the test

Use this information to approve stable tests or flag flaky ones for fixes.

### See all flaky tests at a glance

The test page focuses on a single test. For a project-wide view that ranks every test by flakiness score, open the [Tests dashboard](/docs/learn/reliability-and-flakiness/tests-dashboard.md).

### Ignore changes

When reviewing a build in Argos, you may encounter changes that are not relevant or are caused by flakiness. You can **ignore a specific change** directly from the UI.

From the build page or the test page, click the **Ignore** button next to the change you want to ignore.

Once ignored, Argos will no longer notify you if this **exact same change** happens again in future builds. This lets you filter out noise while keeping future regressions detectable.

Ignored screenshots are also reflected in the [pull request comment](/docs/learn/review-workflow/pull-request-comments.md): the **Details** column reports how many screenshots were ignored alongside the other counts (for example, `4 changed, 3 ignored`).

### Configure what Argos ignores

You control the ignore feature per project from **Project Settings → Flaky detection**.

The **Ignore changes** card has a single toggle, **Enable the ignore feature for this project**, which is on by default. When you turn it off:

* New builds ignore nothing — every change is treated as not ignored.
* Auto-ignore is turned off.
* The **Ignore** button is hidden when reviewing builds.

{% hint style="info" %}
Disabling the feature only changes how **new** builds are computed. Previous builds are not affected — changes already ignored stay ignored on those builds.
{% endhint %}

### Automatically ignore recurring flaky changes

When the ignore feature is enabled, Argos can automatically ignore recurring flaky changes across builds, so you don't have to ignore each one by hand.

To configure auto-ignore:

1. Open your project in Argos.
2. Go to **Project Settings → Flaky detection**.
3. In the **Automatically ignore flaky changes** card, enable **Auto-ignore flaky changes**.
4. Set **Minimum occurrences to consider a change flaky (last 7 days)**.
5. Click **Save**.

![Auto-ignore flaky changes in project settings](/files/ad28850a723cf42e6531a6a715adc1af282c259d)

A change is considered flaky once it appears at least this many times in auto-approved builds within the last 7 days. The default threshold is **3** occurrences.

#### Best use cases

* Flaky UI elements that appear/disappear randomly or render inconsistently.
* Non-deterministic image rendering (e.g. base64 previews, antialiasing issues).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://argos-ci.com/docs/learn/reliability-and-flakiness/flaky-test-detection.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.