DOCSEARCHbyAlgolia
Submit Docs

Argos Visual Testing

website·Indexed 35 days ago

https://docs.argos-ci.com/

A visual testing platform that catches visual regressions before they reach production. Argos provides SDKs for Playwright, Vitest, Storybook, Cypress, WebdriverIO, and Puppeteer, as well as a CLI for any test framework. It features deterministic pixel diffing, baseline build management, flaky test detection, and AI agents to help summarize visual changes and fix unstable tests.

Tokens
60.7K
Snippets
225
Records
456
Agent score
51%

What's inside Argos

  1. Overview of migrating visual tests to Argos

    Migrating to Argos typically involves swapping the SDK, the snapshot call, and the CI step without rewriting the entire test suite. Argos integrates with Playwright, Cypress, Storybook, WebdriverIO, and Puppeteer. Key architectural differences include:

    • Git-based Baselines: Baselines are selected automatically from Git history; reference images are not committed to the repository.
    • PR-centric Review: Diffs are approved/rejected in the Argos app and reported via commit statuses and PR comments.

  2. Overview of Argos Deployments

    Argos Deployments allow you to host a static build (most commonly a Storybook) on a unique, immutable URL for every pull request. This enables developers to share live previews with stakeholders and browse the history of deployed builds across branches and commits without maintaining their own hosting infrastructure. Each deployment is immutable; re-running the deploy command creates a new URL while the previous one remains active.

  3. Overview of Argos Automations

    Argos Automations allow you to create rules that react to build events and notify Slack, Microsoft Teams, or Discord. Automations are configured per project and require project settings permissions to view and manage. A rule consists of three parts: a trigger (When), optional filters (If), and an action (Then).

  4. Overview of Passkeys in Argos

    Passkeys allow users to sign in to Argos using device-native unlock methods (Touch ID, Face ID, Windows Hello, screen locks) or hardware security keys (e.g., YubiKey). Passkeys are bound to argos-ci.com, making them resistant to phishing and database leaks. They are available on all plans and function as an additional login method alongside email, Google, GitHub, GitLab, or SAML sign-in.

  5. Overview of SAML Single Sign-On in Argos

    SAML SSO allows Argos team members to authenticate using third-party identity providers (e.g., Okta, Auth0). It is a paid add-on costing $200/month for teams on Stripe-based subscriptions, though it is included in the Enterprise plan. Only users with the 'owner' role can configure SAML SSO. When enabled, new users signing in via SAML are automatically added to the team.

  6. Overview of Argos Visual Testing

    Argos is a visual testing platform designed to catch visual regressions before they reach production. It integrates with CI pipelines to capture screenshots, compare them against a baseline, and provide visual diffs for review on pull requests. It supports various tools including Playwright, Storybook, Cypress, and Vitest. Beyond image comparison, Argos can compare non-image files, detect flaky tests, and deploy previews of Storybook or static sites on every pull request.

  7. Overview of Argos Media sharing

    Argos Media sharing allows users to upload standalone images or videos (independent of builds or test runs) to get a shareable URL and ready-to-paste Markdown. This is particularly useful for CI jobs or agents that cannot authenticate with GitHub to attach files to pull requests. Media is associated with a project and inherits its access permissions. Note: This is not visual testing; it does not compare images to baselines or gate builds.

  8. Overview of Storybook story modes in Argos

    Storybook story modes allow Argos to capture multiple visual snapshots of a single story by applying different combinations of Storybook globals, such as themes, viewports, and locales. Each named mode creates a separate visual baseline in Argos, enabling automatic testing across various configurations (e.g., "dark mode", "mobile view", or a combination of both).

  9. Overview of Microsoft Teams integration for Argos

    The Microsoft Teams integration allows Argos to send build notifications (created, reviewed, approved, or rejected) as adaptive cards to a Teams channel.

    Key constraints:

    • Available only on Pro and Enterprise plans.
    • Configured at the team level.
    • Requires a Microsoft 365 work or school account (personal accounts at teams.live.com are not supported).
    • One webhook is required per channel; there is no URL unfurling for Argos links pasted directly into Teams.

  10. Overview of the Argos MCP Server

    The Argos MCP server is a remote server that allows AI assistants (such as Claude, Cursor, and VS Code) to interact with Argos projects using the Model Context Protocol (MCP). It uses the streamable HTTP transport, meaning no local package installation is required. The official server URL is https://mcp.argos-ci.com.
    URL: https://mcp.argos-ci.com
Transport: http (or streamable-http)

  11. Overview of Argos AI agent integration tools

    Argos provides a suite of tools designed to allow AI agents (such as Claude, Cursor, or Copilot) to interact with visual regression tests and build data. The core offerings include:

    • MCP Server: Uses the Model Context Protocol to let assistants list builds, inspect diffs, review changes, and manage projects.
    • CLI: A command-line interface for uploading screenshots, inspecting builds, and submitting reviews via scripts or terminal workflows.
    • Agent Skills: Installable skill sets that teach assistants how to use the Argos CLI and execute a full pull-request visual review workflow.
    • AI-ready Documentation: LLM-optimized documentation featuring Markdown pages, llms.txt indexes, and a dedicated docs MCP server.

  12. Overview of Argos Discord integration

    The Discord integration allows Argos to send build notifications (creation, review, approval, or rejection) to a Discord channel via an incoming webhook. Notifications are rendered as embeds containing build status, project, commit, branch, pull request, and a direct link to the build.

    Key constraints:

    • Available only on Pro and Enterprise plans.
    • Configured at the team level.
    • One webhook is required per Discord channel.
    • Connection is outbound only; Argos does not install a bot and does not support URL unfurling (pasting an Argos URL in Discord will not produce a preview).