Changelog

SAML Single Sign-On

You can now configure SAML Single Sign-On (SSO) for your Argos team on the Enterprise plan.

SAML settings are available for team owners in Team Settings -> Security and Privacy. Once configured, team members can authenticate with your identity provider, and users signing in with SAML for the first time are automatically added to the team. It also supports enforcing SAML authentication for team members, and you can share a team-specific login URL that shows only the SAML login option.

Learn more in the SAML SSO documentation.

Subset builds

Subset builds let you run Argos on a partial test suite while keeping feedback focused on what actually ran. When a build is marked as subset, Argos ignores removed screenshots and only reports changed and added screenshots from the tests that executed.

• Fast feature validation: Skip the full E2E suite on branches without losing visual insight.
• No false removals: Missing screenshots from skipped tests won’t be flagged.
• Baseline safe: Full runs on the main branch still power baseline builds.

Learn more in our Subset builds documentation.

Tests dashboard

The new Tests dashboard gives you a project-wide view of all tests ranked by flakiness, so you can quickly spot the most unstable areas and focus your efforts where they matter most. It’s another step in Argos’ complete flaky test management, helping teams stay ahead of noisy or unreliable tests.

• Flakiness-first sorting: Tests are ordered by instability so the biggest problems rise to the top.
• Project-wide coverage: See every test in one place to understand overall health at a glance.
• Faster prioritization: Focus on the tests most likely to cause noise in reviews and builds.

Learn more in our Tests dashboard documentation.

GitHub Merge Queue support

Argos now runs inside the GitHub Merge Queue so the visual checks you rely on during pull requests also guard queued merges. With the Argos GitHub App, Argos reads commit history to compute the right merge base and publish required checks, making sure only clean, intentional visual changes land on your protected branches.

• Queue-aware required checks: Argos computes the merge base against the last approved commit on the target branch and publishes required visual checks along the merge queue path, preventing regressions that only appear after rebases or batched merges.
• Straightforward setup: Listen to both pull_request and merge_group events so Argos runs for reviews and queued merges.

Read more in our documentation.

ARIA Snapshots in Playwright

Argos now supports ARIA Snapshots with the Playwright SDK, giving you a structured view of your page’s accessibility tree directly in your visual testing workflow.

• Easily review text changes: You can now easily spot changes in text content.
• Accessibility insights: Capture the ARIA representation of your pages to detect accessibility regressions over time.
• Combined or standalone: Use argosScreenshot with ariaSnapshot: true to capture both visuals and ARIA trees, or call argosAriaSnapshot for ARIA-only tests.

This feature helps teams combine visual and accessibility testing in one unified workflow, improving overall UI quality and inclusiveness.

Learn more in the docs

Visual Testing in Storybook with Vitest

Argos now supports the Storybook Vitest addon, making it simple to add visual tests right inside your stories.

• Run in CI: Argos captures screenshots during your CI runs for consistent, reproducible results.
• Use the play function: Take screenshots at any point in your play function to validate intermediate states.
• Unlimited execution time: Wait for interactions, async flows, or animations to finish before the screenshot is taken.

With this integration, you can validate not only the static render of your components but their full interactive behavior.

👉 Get started in the docs

Email Management

You can now add and manage multiple email addresses on your Argos account so you can receive notifications where you need them.

To get started, open your Personal Settings and add the desired email addresses.

Ignore Changes

You can now ignore a set of changes in your tests. When you ignore a change, Argos will not notify you if this specific change occurs again in the future. This is useful for multiple scenarios, such as:

• Flaky Elements: If a UI element is unstable, displayed inconsistently, or has rendering issues, you can ignore its changes to avoid unnecessary noise in your visual tests.
• Image Rendering Issues: If an image is rendered differently across environments or devices, ignoring its changes helps maintain focus on more critical visual regressions.

By ignoring a specific set of changes rather than an entire region, you ensure that real regressions can still be detected in the future. In contrast, ignoring a region suppresses all future notifications for that area, even if meaningful changes occur.

Combined with our Flaky Test Detection, this feature provides a powerful way to manage visual test noise. Especially with our "Ocurrences" stats that gives you the exact number of times a change has been seen.

This feature is now available to all users. Learn how to use it in the docs.

Flaky Test Detection

Spot unstable tests right in your build review: Argos now adds a flaky indicator next to each change so you know if a test is flaky before you approve

• Flaky Indicator: A badge on each change flags tests with instability so you can act confidently
• Test Page: Click through to a dedicated page showing every change, stability over time and a calculated flaky score
• Quick Decisions: Use stability history and score to decide if you can safely approve or need a fix
• Future Controls: We’ll layer on tools to ignore irrelevant noise and better manage flaky tests

Learn more in our Flaky Test Detection documentation

Slack Notifications

Keep your team in sync with real-time updates. Argos can now notify your Slack workspace when a build is completed or reviewed.

• Automated Alerts: Send notifications when a build finishes or is reviewed.
• Custom Rules: Configure exactly when and under what conditions messages are sent.
• Channel Targeting: Choose specific Slack channels for each notification.

Read the full setup guide in our Slack notifications documentation.