Changelog

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.

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

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.

Introducing Storybook Story Modes in Argos Storybook plugin. With the latest release, you can define and apply multiple Storybook globals (e.g., themes, viewports, locales) as “modes,” generating separate snapshots for each mode automatically.

• Multi-Config Testing: Capture different looks (dark/light, mobile/desktop, etc.) for each story without duplicating code.
• Easy Configuration: Define modes in .storybook/modes.js (or .ts) and apply them globally, component-wide, or story-by-story.
• Simple Parameter Usage: Configure Argos via parameters.argos. We also honor parameters.chromatic if you’re migrating from Chromatic.
• Isolated Baselines: Each mode maintains its own baseline and approval workflow, making changes easy to track and compare.

Upgrade to the latest version of @argos-ci/storybook to start testing your Storybook stories across every relevant configuration with fewer manual steps. Read the complete guide in story modes documentation.

Introducing the Changes Highlighter — a feature to pinpoint even the subtlest visual differences. With a simple button press, the diff positions are highlighted, and you can quickly navigate through all changes within a screenshot.

• Instant highlights: Quickly reveal diff positions with a single tap
• Easy navigation: Jump through changes to inspect every detail
• Enhanced clarity: Spot hard-to-detect differences effortlessly

Introduing screenshot diff variants, allowing you to view and select different variations of a screenshot diff based on viewport size or browser.

• Multi-viewport & multi-browser comparison: Quickly switch between different versions of a screenshot taken on various browsers and viewports.
• Faster debugging: Easily spot inconsistencies across different environments without switching context.
• Better accuracy: Ensure that visual regressions are correctly assessed across all targeted configurations.

This feature helps teams catch cross-browser and responsive issues faster. You can access screenshot diff variants directly from the diff viewer when inspecting a visual change.

Introducing Spend Management, a feature designed to help you monitor and control your team’s visual testing expenses effectively.

• Customizable Spend Limits: Set specific spending thresholds per billing cycle to manage your budget proactively.
• Alert Notifications: Receive email alerts at 50%, 75%, and 100% of your set spend amount, keeping you informed of your usage.
• Automated Project Pausing: Enable automatic pausing of all projects when your spending limit is reached, preventing unexpected overages.

Spend Management is available on Pro and Enterprise plans (usage-based). To get started, navigate to your team’s Settings tab and configure your spending preferences.

For detailed instructions, refer to our Spend Management documentation.

We’ve rolled out two new improvements to streamline your build workflow.

Build review history

Easily see who reviewed each build and when for improved collaboration. Quick timestamps and reviewer details help you track approvals and rejections at a glance. See the full review history by hovering over the build status.

Build filtering

Filter by status or type to quickly pinpoint the builds you need. This speeds up your workflow and helps you stay organized. Explore the new filters in your Builds tab today.

To wrap up the year on a high note, we’re introducing Team Analytics, a new dashboard that helps you track and understand your visual testing activity at a glance. Monitor builds, screenshots, and detailed usage to keep your team running efficiently.

• Build & Screenshot Trends: Compare how each project contributes to the total number of builds and screenshots, all in one place.
• Usage by period: Quickly review activity to spot trends and see how your test volume evolves over time.
• Screenshots by Project: Get a breakdown of each project’s screenshot usage, making it easy to allocate resources.
• Screenshots by Build: Dive deeper into each build’s screenshot count for a fine-grained analysis of your tests.

This feature is included in all plans. Head to your Analytics tab and see your team’s metrics in action.

Argos now lets you select a default role for all team contributors in a given project. Instead of assigning roles one-by-one, you can define a single default role: viewer, reviewer, or admin. This avoid repetitive manual assignments and ensures that every contributor has the correct level of access.

• Centralized control: Choose a default role to apply to every contributor in a project, cutting down on repetitive manual assignments.
• Flexible access: Continue customizing individual contributor roles as needed, ensuring that you maintain control and clarity for your entire team.
• Simplified management: Make onboarding new contributors easier by ensuring they’re immediately assigned a baseline level of permissions.

Check out the documentation for more details on setting default roles and refining access levels.