Changelog

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.

Argos now offers an official Storybook SDK to streamline visual testing within your component library. With our SDK, you can catch UI regressions early and ensure consistent design across your application.

• Effortless setup: Built with the Storybook test runner, our SDK allows a straightforward and quick integration process, so you can focus on testing.
• Component-level insights: Catch visual regressions early by running tests directly within your Storybook library, ensuring isolated and accurate results.
• Streamlined workflow: With Argos Storybook SDK, bring visual testing closer to your design system, reducing friction between design and development teams.

Get started today with our Storybook SDK documentation and unlock a new level of confidence in your component library.

We’re excited to announce the release of multi-branches in Argos, designed to make visual testing even more flexible and efficient.

Base branch inference

Argos now automatically infers the correct base branch for each pull request, ensuring visual tests are compared against the appropriate baseline. This removes the need for manual setup and guarantees that regressions are detected and resolved within the correct context.

Auto-approved branches

You can now specify which branches should be auto-approved, giving you more control over your testing flow. This feature reduces manual approval steps by allowing branches that meet your criteria to be auto-approved, streamlining your team’s workflow.

No additional configuration required

These improvements are automatically applied to all projects. You don’t need to configure anything to start benefiting from these features immediately. However, if you prefer, you can customize their behavior in the project settings.

For more details on how to configure multi-branch support, visit our documentation.

It is now possible to specify a sensitivity threshold for each screenshot. This enhancement enables you to adjust the sensitivity based on the nature of the application being tested.

For example, the Mermaid team, who use Argos to test their diagrams, can reduce the sensitivity threshold for their less flaky content. This ensures that your visual tests are more accurate and reduces false positives, providing you with more reliable results.

• Reduce false positives: Especially useful for less flaky content like Mermaid diagrams, leading to more consistent and dependable visual testing.
• Enhanced flexibility: Gives you greater control over your visual testing process, allowing for more nuanced adjustments and improved test outcomes.

The threshold option is now available in all SDKs under the argosScreenshot options. You can also apply it directly via the command line using the --threshold flag, which will be applied to all screenshots.

Introducing the Argos Change Highlighter, a vertical bar that marks zones of differences, designed to streamline and enhance your visual testing experience.

• Quick detection: The vertical Change Highlighter bar makes it easy to identify minor changes without scanning the entire screenshot.
• Efficiency boost: Speed up your visual testing reviews by focusing only on the highlighted differences.
• Enhanced accuracy: Ensure that no small change goes unnoticed, improving the reliability of your visual tests.

The Argos Change Highlighter is available now for all plans.

We finally introduce support for partial re-runs in GitHub Actions, a significant enhancement to streamline your CI/CD processes with Argos.

• Time savings: No more waiting for entire workflows to complete. Re-run only the steps that failed or need updating.
• Cost efficiency: Reduce computational costs by avoiding unnecessary re-execution of successful steps.
• Ecology concern: Lower energy consumption by minimizing redundant processing, contributing to a greener environment.

To benefit from this feature, update your SDK. If you don't use Playwright, set the ARGOS_PARALLEL_INDEX environment variable in your GitHub Actions workflow.

We are excited to announce major improvements to the quality of screenshots in Argos, ensuring your visual testing results are clearer and more accessible than ever.

Key Enhancements

• Lossless PNG Compression: Preserve the highest quality and detail in your screenshots with no artifacts.
• Sharp Display: Using image-rendering: pixelated at 1.5x zoom level for clear visuals even when zoomed in.
• Fast Rendering with AVIF: Optimized images for fast loading and efficient rendering without compromising quality.

Experience the difference in screenshot quality today and elevate your visual testing with Argos.

We have added a new feature: Monitoring Mode. This mode helps you track visual changes over time or before a release, providing additional assurance for your projects.

• Periodic Visual Checks: Set up Monitoring Mode to run visual tests periodically (e.g., daily or weekly) on a specific branch. This ensures any unexpected visual changes are detected early.
• Pre-release Validation: Use Monitoring Mode to run visual checks on your release branch, comparing the current state with the last approved build to ensure everything looks as expected before the final deployment.
• Post-deployment Monitoring: Configure Monitoring Mode to run after each deployment to staging or production environments to catch any discrepancies caused by environmental differences.
• Third-party Integrations: Regularly check the visual integration points of third-party services or widgets to ensure they remain consistent and do not disrupt the user experience.

For detailed instructions on how to use Monitoring Mode, please refer to our documentation.

Recognizing the critical importance of stability in continuous integration, Argos has introduced a dedicated section for handling retried test failures. This update is in direct response to your valuable feedback, aimed at minimizing disruptions and maximizing team productivity.

With this enhancement, you can still review the screenshots of test retries without cluttering your workspace with test failures that have finally passed.

Start experiencing the benefits of this refined approach today, and let us know your thoughts as we continue to refine and evolve Argos.

Argos now supports Google Authentication, offering users a streamlined and secure way to log in. This feature enables signing in with a Google account, eliminating the need for separate passwords and leveraging Google's advanced security protections. The integration is designed to enhance both convenience and safety for Argos users, reflecting ongoing improvements to the platform.

To get started, choose "Sign in with Google" on the login page. Feedback on this new feature is welcome as Argos continues to evolve and introduce new functionalities.