You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/learn/flaky-test-detection.mdx
+13Lines changed: 13 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,3 +42,16 @@ On the test page you will find:
42
42
- List of changes happened to the test
43
43
44
44
Use this information to approve stable tests or flag flaky ones for fixes.
45
+
46
+
## Ignore changes
47
+
48
+
When reviewing a visual test result 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.
49
+
50
+
From the build page or the test page, click on the "Ignore" button next to the change you want to ignore.
51
+
52
+
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.
53
+
54
+
### Best Use Cases
55
+
56
+
- Flaky UI elements that appear/disappear randomly or render inconsistently.
0 commit comments