> 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.md).

# Reliability & flakiness

Detect unstable tests and use Argos tools and strategies to track and fix flakiness in your visual suite.

Flaky tests fail or change without a meaningful code change and erode trust in your suite. Argos detects unstable screenshots automatically, ranks them so you know where to act, and gives you a playbook to fix the root causes.

* [Flaky test detection](/docs/learn/reliability-and-flakiness/flaky-test-detection.md) – How Argos flags unstable tests and ignores noisy changes
* [Tests dashboard](/docs/learn/reliability-and-flakiness/tests-dashboard.md) – A project-wide view that ranks tests by flakiness
* [Test page](/docs/learn/reliability-and-flakiness/test-page.md) – Everything Argos knows about one test: its metrics, its changes, and its discussion
* [Ignored changes](/docs/learn/reliability-and-flakiness/ignored-changes.md) – Review what a project ignores and unignore the changes that went quiet
* [Fix flaky tests with AI agents](/docs/learn/reliability-and-flakiness/fix-flaky-tests-with-ai-agents.md) – Hand a flaky test to an agent and let it find the non-determinism
* [Stabilize screenshots](/docs/learn/reliability-and-flakiness/flaky-tests.md) – Strategies for writing stable, deterministic visual tests


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.