# Cypress

> Cypress is a modern end-to-end testing framework for web applications, designed for developers to write, run, and debug tests easily.

This index links the markdown for every page of the Cypress documentation.
Every page is published at its own URL plus `.md`, so dropping the `.md` from
any link below gives the HTML page, and the same file is served from
`https://docs.cypress.io/llm/markdown/<page-path>.md`. Fetch markdown rather than HTML: it is
the same content without the site chrome.

## Documentation formats

- [Full corpus](https://docs.cypress.io/llms-full.txt): every page listed below, concatenated into one markdown file (5.0 MB, 325 pages). Use it to index the whole corpus, not to answer one question.
- [Markdown corpus index](https://docs.cypress.io/llm/markdown/index.md): browsable directory listing of `/llm/markdown/`, which mirrors the `docs/` tree.
- [Page markdown](https://docs.cypress.io/app/get-started/why-cypress.md): any documentation URL plus `.md`, also served at `https://docs.cypress.io/llm/markdown/app/get-started/why-cypress.md`.
- [Page section markdown](https://docs.cypress.io/app/get-started/why-cypress/features.md): a single `##` section of a page, at `<page-path>/<h2-slug>.md`. Prefer it over the whole page when you only need one topic.
- [Chunked JSON index](https://docs.cypress.io/llm/json/chunked/index.json): every page split at its headings, with token estimates. Use for retrieval and embeddings.
- [Full JSON index](https://docs.cypress.io/llm/json/full/index.json): whole documents as structured JSON. Use when you want complete context for one page.
- [Docs manifest](https://docs.cypress.io/docs-manifest.json): machine-readable project metadata and the same list of endpoints.
- [Agent skills](https://docs.cypress.io/.well-known/agent-skills/index.json): Cypress skills for AI coding agents.

## Cypress App

- [AI in Cypress: test generation, agent skills, and agentic debugging](https://docs.cypress.io/app/ai/overview.md): A map of every AI capability in Cypress: author tests with Cypress Studio and cy.prompt, give AI coding agents real Cypress context with skills and Cloud MCP, and analyze runs with Cypress AI.
- [Angular API](https://docs.cypress.io/app/component-testing/angular/api.md): API for mounting Angular components in Cypress tests.
- [Angular examples](https://docs.cypress.io/app/component-testing/angular/examples.md): Learn how to mount an Angular component, pass data to an Angular component, test multiple scenarios of Angular components, test Angular signals, and customize `cy.mount()` for Angular.
- [Angular component testing](https://docs.cypress.io/app/component-testing/angular/overview.md): Learn how to set up component tests in Angular and configure Cypress for Angular projects.
- [Configure component tests](https://docs.cypress.io/app/component-testing/component-framework-configuration.md): Configure Cypress for component testing with dev servers, bundlers, custom index files, and spec patterns.
- [Custom frameworks](https://docs.cypress.io/app/component-testing/custom-frameworks.md): Learn how to create a custom Framework Definition and Mount Adapter for your favorite library or framework.
- [Get started with component testing](https://docs.cypress.io/app/component-testing/get-started.md): Write Cypress component tests in React, Angular, Vue, or Svelte. Learn how to set up, write, and run your first component test in a real browser with full debugging capabilities.
- [React API](https://docs.cypress.io/app/component-testing/react/api.md): API for mounting React components in Cypress tests.
- [React examples](https://docs.cypress.io/app/component-testing/react/examples.md): Learn how to mount a React component, pass data to a React component, test event handlers, and customize cy.mount() for React Router and Redux.
- [React component testing](https://docs.cypress.io/app/component-testing/react/overview.md): Learn how to set up component tests in React and use Cypress with different React frameworks and bundlers.
- [Test your component's styles](https://docs.cypress.io/app/component-testing/styling-components.md): Learn how to test your component's markup, styles, and script logic with Cypress Component Testing
- [Svelte API](https://docs.cypress.io/app/component-testing/svelte/api.md): API for mounting Svelte components in Cypress tests.
- [Svelte examples](https://docs.cypress.io/app/component-testing/svelte/examples.md): Learn how to test Svelte components with Cypress Component Testing.
- [Svelte component testing](https://docs.cypress.io/app/component-testing/svelte/overview.md): Learn how to set up component tests in Svelte, configure Cypress for Svelte projects, and test Svelte components with Vite and a custom Webpack config.
- [Vue API](https://docs.cypress.io/app/component-testing/vue/api.md): API for mounting Vue components in Cypress tests.
- [Vue examples](https://docs.cypress.io/app/component-testing/vue/examples.md): Examples for testing Vue components with Cypress.
- [Vue component testing](https://docs.cypress.io/app/component-testing/vue/overview.md): Learn how to set up component tests in Vue and configure Cypress for Vue projects.
- [Run Cypress tests in AWS CodeBuild: step-by-step guide](https://docs.cypress.io/app/continuous-integration/aws-codebuild.md): Learn how to set up and run Cypress tests in AWS CodeBuild, cache dependencies and build artifacts, run tests in parallel, and use Cypress Cloud with AWS CodeBuild.
- [Run Cypress tests in Bitbucket Pipelines: step-by-step guide](https://docs.cypress.io/app/continuous-integration/bitbucket-pipelines.md): Run Cypress tests in Bitbucket Pipelines with Docker images, caching, parallelization, and Cypress Cloud.
- [Run Cypress tests in CircleCI: step-by-step guide](https://docs.cypress.io/app/continuous-integration/circleci.md): Set up CircleCI to run Cypress tests with the Cypress Orb, cache dependencies and build artifacts, and parallelize Cypress tests.
- [Run Cypress tests in GitHub Actions: step-by-step guide](https://docs.cypress.io/app/continuous-integration/github-actions.md): Set up GitHub Actions to run Cypress tests, cache dependencies and build artifacts, and parallelize Cypress tests.
- [Run Cypress in GitLab CI: step-by-step guide](https://docs.cypress.io/app/continuous-integration/gitlab-ci.md): Set up GitLab CI/CD to run Cypress tests with Docker images, caching, parallelization, and Cypress Cloud.
- [Continuous Integration with Cypress: Run Tests in CI](https://docs.cypress.io/app/continuous-integration/overview.md): Set up Cypress in CI: install and run commands, boot your server, record to Cypress Cloud, run in parallel, and use Cypress Docker images on any CI provider.
- [Cypress best practices](https://docs.cypress.io/app/core-concepts/best-practices.md): Best practices for organizing tests, selecting elements, and controlling state in Cypress.
- [Interacting with elements in Cypress](https://docs.cypress.io/app/core-concepts/interacting-with-elements.md): Learn how Cypress determines if an element is actionable, how to debug when elements are not actionable, and how to ignore Cypress' actionability checks.
- [Introduction to Cypress](https://docs.cypress.io/app/core-concepts/introduction-to-cypress.md): Learn the basics of Cypress, including querying elements, chaining commands, and interacting with elements.
- [Open mode in the Cypress app](https://docs.cypress.io/app/core-concepts/open-mode.md): Learn how Cypress open mode works, including the Test Runner, Command Log, Cypress Studio for recording interactions and inline edits, and tools for debugging tests in the Cypress app.
- [Retry-ability in Cypress](https://docs.cypress.io/app/core-concepts/retry-ability.md): Understand how Cypress retries commands, queries, and assertions to help you write faster tests with fewer run-time surprises.
- [Test isolation in Cypress](https://docs.cypress.io/app/core-concepts/test-isolation.md): Learn how Cypress ensures test isolation and how to configure test isolation in end-to-end and component testing.
- [End-to-end, component, API, and accessibility testing in Cypress](https://docs.cypress.io/app/core-concepts/testing-types.md): Learn the differences between Cypress end-to-end, component, API, and accessibility tests, the benefits and considerations for each type of test, and common scenarios for each type of test.
- [Variables and aliases in Cypress](https://docs.cypress.io/app/core-concepts/variables-and-aliases.md): Learn how to handle asynchronous code in Cypress, when to assign variables, how to use aliases to share objects between hooks and tests, and how to alias DOM elements, intercepts, and requests.
- [Writing and organizing Cypress tests](https://docs.cypress.io/app/core-concepts/writing-and-organizing-tests.md): Learn how to structure a Cypress project and write reliable tests, covering supported spec files, folder structure, hooks, test isolation, configuration, assertions, and test statuses.
- [Effective E2E testing in Cypress](https://docs.cypress.io/app/end-to-end-testing/testing-your-app.md): Strategies for end-to-end testing your own app in Cypress: seeding state, handling logins, and choosing reliable selectors.
- [End-to-end testing: your first test with Cypress](https://docs.cypress.io/app/end-to-end-testing/writing-your-first-end-to-end-test.md): Write your first Cypress end-to-end test step by step: visit a page, query elements, make assertions, and debug failures.
- [Frequently asked questions: Cypress App](https://docs.cypress.io/app/faq.md): Get answers to common questions about Cypress, including cy.prompt, how-to questions, and more.
- [Install using npm, Yarn, pnpm, or Bun](https://docs.cypress.io/app/get-started/install-cypress.md): The fastest way to get Cypress running. Check requirements, install it in your project, and start testing today.
- [Open the Cypress app: step-by-step guide](https://docs.cypress.io/app/get-started/open-the-app.md): Open the Cypress app to run tests interactively, watch them execute in a real browser, and debug failures visually, with guided setup that configures your project for you.
- [Why Cypress? End-to-end, component & accessibility testing](https://docs.cypress.io/app/get-started/why-cypress.md): Why teams choose Cypress for end-to-end, component, and accessibility testing — its architecture, features, and trade-offs.
- [Accessibility testing in Cypress](https://docs.cypress.io/app/guides/accessibility-testing.md): Learn how to ensure your application works for users with disabilities, and how to write accessibility-specific tests in Cypress.
- [Generate tests with cy.prompt](https://docs.cypress.io/app/guides/ai-test-generation.md): Write Cypress E2E tests in natural language with cy.prompt. Generate tests from plain steps, get self-healing selectors, export the generated code, and reduce end-to-end test maintenance.
- [API testing in Cypress](https://docs.cypress.io/app/guides/api-testing.md): Learn how to test REST and GraphQL APIs in Cypress with cy.request(): authentication, CRUD workflows, error responses, polling, and combining API calls with UI tests.
- [Testing Amazon Cognito authentication in Cypress](https://docs.cypress.io/app/guides/authentication-testing/amazon-cognito-authentication.md): Test Amazon Cognito login in Cypress using the Amplify SDK and cy.session() to reuse authenticated state.
- [Testing Auth0 authentication in Cypress](https://docs.cypress.io/app/guides/authentication-testing/auth0-authentication.md): Test Auth0 login flows in Cypress with cy.origin(), and reuse authenticated sessions across tests with cy.session().
- [Testing Azure Active Directory authentication in Cypress](https://docs.cypress.io/app/guides/authentication-testing/azure-active-directory-authentication.md): Learn how to set up Cypress to test against an Azure Active Directory web app and authenticate with Azure Active Directory using `cy.origin()`.
- [Testing Google authentication in Cypress](https://docs.cypress.io/app/guides/authentication-testing/google-authentication.md): Test Google (OAuth) login in Cypress using cy.origin(), and cache authenticated sessions with cy.session().
- [Testing Okta authentication in Cypress](https://docs.cypress.io/app/guides/authentication-testing/okta-authentication.md): Test Okta login in Cypress end-to-end tests using cy.origin(), and cache sessions with cy.session().
- [Testing social authentication in Cypress](https://docs.cypress.io/app/guides/authentication-testing/social-authentication.md): Authenticate with common social authentication platforms with cy.origin() and use cy.session() to cache authenticated users.
- [Conditional testing in Cypress](https://docs.cypress.io/app/guides/conditional-testing.md): Learn how to do conditional testing in Cypress without relying on the DOM.
- [Cross browser testing in Cypress](https://docs.cypress.io/app/guides/cross-browser-testing.md): Learn how to run tests across multiple browsers and strategies for incorporating cross-browser testing into your CI process.
- [Cross origin testing in Cypress](https://docs.cypress.io/app/guides/cross-origin-testing.md): Learn how to test cross-origin content with Cypress.
- [Cypress Studio AI](https://docs.cypress.io/app/guides/cypress-studio.md): Record interactions, get AI-powered assertion recommendations, and build more complete E2E tests without writing every line by hand.
- [Debugging in Cypress](https://docs.cypress.io/app/guides/debugging.md): Learn how to use debugger, .debug(), .pause(), and the Developer Tools to debug Cypress tests.
- [Environment variables and secrets in Cypress](https://docs.cypress.io/app/guides/environment-variables.md): Learn how to manage environment variables and secrets in Cypress. Understand when to use cy.env(), when to use Cypress.expose(), and how to safely pass values across environments.
- [Migrate from Playwright to Cypress: complete migration guide](https://docs.cypress.io/app/guides/migration/playwright-to-cypress.md): Step-by-step guide to migrate end-to-end and component tests from Playwright to Cypress. Compare syntax, learn retry-ability, network stubbing, auth patterns, CI parallelization, and Cloud features.
- [Migrate from Protractor to Cypress: complete migration guide](https://docs.cypress.io/app/guides/migration/protractor-to-cypress.md): Migrate from Protractor to Cypress with this guide. Learn how to work with the DOM, write assertions, and use the Angular schematic to configure Cypress.
- [Migrate from Selenium to Cypress: complete migration guide](https://docs.cypress.io/app/guides/migration/selenium-to-cypress.md): Step-by-step guide to migrate Selenium WebDriver tests to Cypress. Map locators, waits, WebDriver lifecycle, assertions, alerts, frames, network stubbing, Page Objects, Grid, and CI side by side.
- [Native network interception in Cypress](https://docs.cypress.io/app/guides/native-network-interception.md): How Cypress intercepts test traffic on the native browser network in Chrome, Chromium, and Edge, which testing behaviors change as a result, and how to update tests that depend on them.
- [Intercepting network requests](https://docs.cypress.io/app/guides/network-requests.md): Observe, wait on, and stub your application network requests with cy.intercept(), including fixtures, aliases, assertions, and GraphQL queries and mutations.
- [Capture screenshots and videos in Cypress](https://docs.cypress.io/app/guides/screenshots-and-videos.md): Capture screenshots and videos of your tests with Cypress and configure settings for them.
- [Stubs, spies, and clocks in Cypress](https://docs.cypress.io/app/guides/stubs-spies-and-clocks.md): Learn how to use `cy.stub()`, `cy.spy()`, and `cy.clock()` in Cypress to manipulate your application's behavior and time.
- [Optimizing test performance](https://docs.cypress.io/app/guides/test-performance.md): Diagnose slow Cypress tests and fix them. Covers benchmarks, high-leverage optimizations, CI configuration, and parallelization.
- [Test retries in Cypress](https://docs.cypress.io/app/guides/test-retries.md): Learn how to configure test retries in Cypress to help detect test flakiness and continuous integration (CI) build failures.
- [How to Use Cypress Plugins: Install, Register, and Verify](https://docs.cypress.io/app/plugins/plugins-guide.md): Install Cypress plugins from npm, register them in setupNodeEvents or your support file, and troubleshoot plugin issues. Includes a @cypress/grep example.
- [Cypress Plugins: Official & Community Extensions](https://docs.cypress.io/app/plugins/plugins-list.md): Browse official and community Cypress plugins that extend and customize your tests, with badges and maintenance signals to help you pick the right one.
- [Advanced installation in Cypress: custom binary, cache & proxy](https://docs.cypress.io/app/references/advanced-installation.md): Configure advanced Cypress installation: install a custom binary or version, change the cache folder, install behind a proxy, mirror, or custom CA, and skip the binary download.
- [Assertions in Cypress](https://docs.cypress.io/app/references/assertions.md): Assertions available in Cypress with Chai, Chai-jQuery, and Sinon-Chai assertions
- [Bundled Libraries in Cypress](https://docs.cypress.io/app/references/bundled-libraries.md): Cypress bundles Mocha, Chai, Chai-jQuery, Sinon, Sinon-Chai, Lodash, jQuery, and more, so you can write tests immediately with no extra installation or configuration.
- [Changelog: Cypress App](https://docs.cypress.io/app/references/changelog.md): Release notes for the Cypress App.
- [Configure client certificates in Cypress](https://docs.cypress.io/app/references/client-certificates.md): Configure certificate authority (CA) and client certificates to test mTLS (mutual TLS) protected endpoints in Cypress on a per-URL basis.
- [Command line interface (CLI) commands and options in Cypress](https://docs.cypress.io/app/references/command-line.md): Learn how to run Cypress from the command line using npm, Yarn, or pnpm.
- [Configuration in Cypress](https://docs.cypress.io/app/references/configuration.md): Change the default behavior of Cypress by configuring options in the Cypress configuration file.
- [Content security policy (CSP) in Cypress](https://docs.cypress.io/app/references/content-security-policy.md): Why Cypress manages Content Security Policy (CSP), how to tell when you need to configure it, and how to allow your policy through for testing.
- [Common error messages in Cypress](https://docs.cypress.io/app/references/error-messages.md): Common error messages you may encounter while using Cypress and how to resolve them.
- [Experimental features in Cypress App](https://docs.cypress.io/app/references/experiments.md): Enable experimental features in Cypress by configuring specific options.
- [Launching browsers in Cypress: Chrome, Firefox, Edge & WebKit](https://docs.cypress.io/app/references/launching-browsers.md): Learn how Cypress launches and controls Chrome, Firefox, Edge, Electron, and WebKit. Choose and customize browsers, run headless, and fix launch issues.
- [Upgrade Cypress: version migration guide](https://docs.cypress.io/app/references/migration-guide.md): A guide to help you upgrade to the latest version of Cypress.
- [Module API: how to run Cypress via Node.js](https://docs.cypress.io/app/references/module-api.md): Require Cypress as a node module from your application under test and run Cypress via Node.js.
- [Proxy configuration in Cypress](https://docs.cypress.io/app/references/proxy-configuration.md): Why Cypress needs proxy configuration behind a corporate proxy, how it resolves your proxy settings, and how to configure them on macOS, Linux, and Windows
- [Recipes in Cypress: how to test common scenarios](https://docs.cypress.io/app/references/recipes.md): Cypress Recipes show you how to test common scenarios in Cypress. Learn how to test the DOM, log in, use preprocessors, and more.
- [Release Stages for Cypress App](https://docs.cypress.io/app/references/release-stages.md): Learn about the release stages for the Cypress App, including strategies for releasing and communicating changes in each stage.
- [Trade-offs in Cypress](https://docs.cypress.io/app/references/trade-offs.md): Learn about the trade-offs you make when using Cypress, and how to work around them.
- [Troubleshooting: Cypress App](https://docs.cypress.io/app/references/troubleshooting.md): Resources to help you troubleshoot Cypress App issues and common steps to isolate and resolve problems.
- [Cypress AI Skills](https://docs.cypress.io/app/tooling/ai-skills.md): Cypress AI Skills teach AI coding agents like Cursor, Claude Code, and GitHub Copilot to write, review, explain, and debug Cypress tests using best practices.
- [Measuring code coverage in Cypress](https://docs.cypress.io/app/tooling/code-coverage.md): Learn how to measure code coverage in Cypress and the difference between UI Coverage and Code Coverage.
- [Drive Cypress with AI agents using cypress tap](https://docs.cypress.io/app/tooling/cypress-tap.md): Let Cursor, Claude Code, or any AI agent run your Cypress tests from the terminal, read the failures, and verify fixes against a live Cypress session.
- [IDE Integration with Cypress: VS Code, JetBrains, and More](https://docs.cypress.io/app/tooling/IDE-integration.md): Set up Cypress in your IDE with IntelliSense code completion, extensions for VS Code and JetBrains, ESLint rules, and one-click file opening from the Cypress app.
- [Built-in and custom reporters in Cypress: setup guide](https://docs.cypress.io/app/tooling/reporters.md): Learn how to use custom reporters in Cypress to output test results in different formats.
- [TypeScript support in Cypress](https://docs.cypress.io/app/tooling/typescript-support.md): Learn how to set up TypeScript in Cypress, configure TypeScript for custom commands, assertions, and plugins and more
- [Visual testing in Cypress](https://docs.cypress.io/app/tooling/visual-testing.md): Learn how visual testing catches appearance regressions that functional tests miss, how to choose between visual testing plugins and services, and how to write reliable visual tests.

## API

- [cy.and()](https://docs.cypress.io/api/commands/and.md): Create an assertion. Assertions are automatically retried as part of the previous command until they pass or time out.
- [cy.as()](https://docs.cypress.io/api/commands/as.md): Assign an alias for later use in Cypress. Reference the alias later within a cy.get() query or cy.wait() command with an `@` prefix.
- [cy.blur()](https://docs.cypress.io/api/commands/blur.md): Blur a focused element in Cypress.
- [cy.check()](https://docs.cypress.io/api/commands/check.md): Check checkbox(es) or radio(s) in Cypress.
- [cy.children()](https://docs.cypress.io/api/commands/children.md): Get the children of each DOM element within a set of DOM elements in Cypress.
- [cy.clear()](https://docs.cypress.io/api/commands/clear.md): Clear the value of an input or textarea in Cypress.
- [cy.clearAllCookies()](https://docs.cypress.io/api/commands/clearallcookies.md): Clear all browser cookies in Cypress.
- [cy.clearAllLocalStorage()](https://docs.cypress.io/api/commands/clearalllocalstorage.md): Clear all localStorage data in Cypress.
- [cy.clearAllSessionStorage()](https://docs.cypress.io/api/commands/clearallsessionstorage.md): Clear all session storage data in Cypress.
- [cy.clearCookie()](https://docs.cypress.io/api/commands/clearcookie.md): Clear a specific browser cookie in Cypress.
- [cy.clearCookies()](https://docs.cypress.io/api/commands/clearcookies.md): Clear browser cookies for a domain in Cypress.
- [cy.clearLocalStorage()](https://docs.cypress.io/api/commands/clearlocalstorage.md): Clear data in localStorage for current domain and subdomain in Cypress.
- [cy.click()](https://docs.cypress.io/api/commands/click.md): Click a DOM element in Cypress.
- [cy.clock()](https://docs.cypress.io/api/commands/clock.md): Override native global functions related to time allowing them to be controlled synchronously via cy.tick() or the yielded clock object.
- [cy.closest()](https://docs.cypress.io/api/commands/closest.md): Get the first DOM element that matches the selector in Cypress (whether it be itself or one of its ancestors).
- [cy.contains()](https://docs.cypress.io/api/commands/contains.md): Get the DOM element containing the text in Cypress.
- [cy.dblclick()](https://docs.cypress.io/api/commands/dblclick.md): Double-click a DOM element in Cypress.
- [cy.debug()](https://docs.cypress.io/api/commands/debug.md): Set a debugger in Cypress and log what the previous command yields.
- [cy.document()](https://docs.cypress.io/api/commands/document.md): Get the window.document of the page that is currently active.
- [cy.each()](https://docs.cypress.io/api/commands/each.md): Iterate through an array like structure in Cypress (arrays or objects with a length property).
- [cy.env()](https://docs.cypress.io/api/commands/env.md): Securely read environment variables in Cypress tests using cy.env(). Learn syntax, examples, security benefits, and how to migrate from Cypress.env().
- [cy.eq()](https://docs.cypress.io/api/commands/eq.md): Get a DOM element at a specific index in an array of elements in Cypress.
- [cy.filter()](https://docs.cypress.io/api/commands/filter.md): Get the DOM elements that match a specific selector in Cypress.
- [cy.find()](https://docs.cypress.io/api/commands/find.md): Get the descendent DOM elements of a specific selector in Cypress.
- [cy.first()](https://docs.cypress.io/api/commands/first.md): Get the first DOM element within a set of DOM elements in Cypress.
- [cy.fixture()](https://docs.cypress.io/api/commands/fixture.md): Load a fixed set of data located in a file in Cypress.
- [cy.focus()](https://docs.cypress.io/api/commands/focus.md): Focus on a DOM element in Cypress.
- [cy.focused()](https://docs.cypress.io/api/commands/focused.md): Get the DOM element that is currently focused in Cypress.
- [cy.get()](https://docs.cypress.io/api/commands/get.md): Get one or more DOM elements by selector or alias in Cypress.
- [cy.getAllCookies()](https://docs.cypress.io/api/commands/getallcookies.md): Get all browser cookies in Cypress.
- [cy.getAllLocalStorage()](https://docs.cypress.io/api/commands/getalllocalstorage.md): Get localStorage data for all origins with which the test has interacted in Cypress.
- [cy.getAllSessionStorage()](https://docs.cypress.io/api/commands/getallsessionstorage.md): Get sessionStorage data for all origins with which the test has interacted in Cypress.
- [cy.getCookie()](https://docs.cypress.io/api/commands/getcookie.md): Get a browser cookie by its name in Cypress.
- [cy.getCookies()](https://docs.cypress.io/api/commands/getcookies.md): Get browser cookies for the current domain or the specified domain in Cypress.
- [cy.go()](https://docs.cypress.io/api/commands/go.md): Navigate back or forward to the previous or next URL in the browser's history in Cypress.
- [cy.hash()](https://docs.cypress.io/api/commands/hash.md): Get the current URL hash of the page that is currently active in Cypress.
- [hover: workarounds](https://docs.cypress.io/api/commands/hover.md): Cypress does not have a cy.hover() command: See common workarounds
- [cy.intercept()](https://docs.cypress.io/api/commands/intercept.md): Spy and stub network requests and responses.
- [cy.invoke()](https://docs.cypress.io/api/commands/invoke.md): Invoke a function on the previously yielded subject in Cypress.
- [cy.its()](https://docs.cypress.io/api/commands/its.md): Get a property's value on the previously yielded subject in Cypress.
- [cy.last()](https://docs.cypress.io/api/commands/last.md): Get the last DOM element within a set of DOM elements in Cypress.
- [cy.location()](https://docs.cypress.io/api/commands/location.md): Get the global window.location object of the page that is currently active in Cypress.
- [cy.log()](https://docs.cypress.io/api/commands/log.md): Print a message to the Cypress Command Log.
- [cy.mount()](https://docs.cypress.io/api/commands/mount.md): Set up a mount command in your support file for Cypress Component Testing
- [cy.next()](https://docs.cypress.io/api/commands/next.md): Get the immediately following sibling of each DOM element within a set of DOM elements in Cypress.
- [cy.nextAll()](https://docs.cypress.io/api/commands/nextall.md): Get all following siblings of each DOM element in a set of matched DOM elements in Cypress.
- [cy.nextUntil()](https://docs.cypress.io/api/commands/nextuntil.md): Get all following siblings of each DOM element in a set of matched DOM elements up to, but not including, the element provided in Cypress.
- [cy.not()](https://docs.cypress.io/api/commands/not.md): Filter DOM element(s) from a set of DOM elements in Cypress.
- [cy.origin()](https://docs.cypress.io/api/commands/origin.md): Visit multiple domains of different origin in a single test in Cypress.
- [cy.parent()](https://docs.cypress.io/api/commands/parent.md): Get the parent DOM element of a set of DOM elements in Cypress.
- [cy.parents()](https://docs.cypress.io/api/commands/parents.md): Get the parent DOM elements of a set of DOM elements in Cypress.
- [cy.parentsUntil()](https://docs.cypress.io/api/commands/parentsuntil.md): Get all ancestors of each DOM element in a set of matched DOM elements up to, but not including, the element provided in Cypress.
- [cy.pause()](https://docs.cypress.io/api/commands/pause.md): Stop Cypress commands from running and allow interaction with the application under test.
- [cy.press()](https://docs.cypress.io/api/commands/press.md): Trigger native key events in your application to simulate keyboard interactions.
- [cy.prev()](https://docs.cypress.io/api/commands/prev.md): Get the immediately preceding sibling of each element in a set of the elements in Cypress.
- [cy.prevAll()](https://docs.cypress.io/api/commands/prevall.md): Get all previous siblings of each DOM element in a set of matched DOM elements in Cypress.
- [cy.prevUntil()](https://docs.cypress.io/api/commands/prevuntil.md): Get all previous siblings of each DOM element in a set of matched DOM elements up to, but not including, the element provided in Cypress.
- [cy.prompt()](https://docs.cypress.io/api/commands/prompt.md): AI-powered Cypress command for developers and QA teams. Generate Cypress tests from natural language, get self-healing selectors, and reduce end-to-end test maintenance with cy.prompt.
- [cy.readFile()](https://docs.cypress.io/api/commands/readfile.md): Read a file and yield its contents in Cypress.
- [cy.reload()](https://docs.cypress.io/api/commands/reload.md): Reload the page in Cypress.
- [cy.request()](https://docs.cypress.io/api/commands/request.md): Make an HTTP request in Cypress.
- [cy.rightclick()](https://docs.cypress.io/api/commands/rightclick.md): Right click a DOM element in Cypress.
- [cy.root()](https://docs.cypress.io/api/commands/root.md): Get the root DOM element in Cypress.
- [cy.screenshot()](https://docs.cypress.io/api/commands/screenshot.md): Take a screenshot of the application under test and, optionally, the Cypress Command Log.
- [cy.scrollIntoView()](https://docs.cypress.io/api/commands/scrollintoview.md): Scroll an element into view in Cypress.
- [cy.scrollTo()](https://docs.cypress.io/api/commands/scrollto.md): Scroll to a specific position in the window or element in Cypress.
- [cy.select()](https://docs.cypress.io/api/commands/select.md): Select an option within a select in Cypress.
- [cy.selectFile()](https://docs.cypress.io/api/commands/selectfile.md): Select a file or files in an HTML5 input element or simulate dragging a file or files into the browser in Cypress.
- [cy.session()](https://docs.cypress.io/api/commands/session.md): Cache and restore cookies, localStorage, and sessionStorage in order to recreate a consistent browser context between tests in Cypress.
- [cy.setCookie()](https://docs.cypress.io/api/commands/setcookie.md): Set a browser cookie in Cypress.
- [cy.shadow()](https://docs.cypress.io/api/commands/shadow.md): Traverse into the shadow DOM of an element in Cypress.
- [cy.should()](https://docs.cypress.io/api/commands/should.md): Create an assertion in Cypress.
- [cy.siblings()](https://docs.cypress.io/api/commands/siblings.md): Get sibling DOM elements in Cypress.
- [cy.spread()](https://docs.cypress.io/api/commands/spread.md): Expand an array into multiple arguments in Cypress.
- [cy.spy()](https://docs.cypress.io/api/commands/spy.md): Wrap a method in a spy in order to record calls to and arguments of the function in Cypress.
- [cy.stub()](https://docs.cypress.io/api/commands/stub.md): Replace a function, record its usage and control its behavior in Cypress.
- [cy.submit()](https://docs.cypress.io/api/commands/submit.md): Submit a form in Cypress.
- [cy.task()](https://docs.cypress.io/api/commands/task.md): Execute code in Node.js via the task plugin event in Cypress.
- [cy.then()](https://docs.cypress.io/api/commands/then.md): Enables you to work with the subject yielded from the previous command in Cypress.
- [cy.tick()](https://docs.cypress.io/api/commands/tick.md): Move time after overriding a native time function with `cy.clock()` in Cypress.
- [cy.title()](https://docs.cypress.io/api/commands/title.md): Get the document.title property of the page that is currently active in Cypress.
- [cy.trigger()](https://docs.cypress.io/api/commands/trigger.md): Trigger an event on a DOM element in Cypress.
- [cy.type()](https://docs.cypress.io/api/commands/type.md): Type into a DOM element in Cypress.
- [cy.uncheck()](https://docs.cypress.io/api/commands/uncheck.md): Uncheck checkbox(es) in Cypress.
- [cy.url()](https://docs.cypress.io/api/commands/url.md): Get the current URL of the page that is currently active in Cypress.
- [cy.viewport()](https://docs.cypress.io/api/commands/viewport.md): Control the size and orientation of the screen for your application in Cypress.
- [cy.visit()](https://docs.cypress.io/api/commands/visit.md): Visit a remote URL in Cypress
- [cy.wait()](https://docs.cypress.io/api/commands/wait.md): Wait for a number of milliseconds or wait for an aliased resource to resolve before moving on to the next command in Cypress.
- [cy.window()](https://docs.cypress.io/api/commands/window.md): Get the window object of the page that is currently active in Cypress.
- [cy.within()](https://docs.cypress.io/api/commands/within.md): Scopes all subsequent Cypress commands to within the element.
- [cy.wrap()](https://docs.cypress.io/api/commands/wrap.md): Yield the object passed into .wrap() in Cypress
- [cy.writeFile()](https://docs.cypress.io/api/commands/writefile.md): Write to a file with the specified contents in Cypress.
- [Cypress.arch](https://docs.cypress.io/api/cypress-api/arch.md): Cypress.arch returns you the CPU architecture name of the underlying OS.
- [Cypress.browser](https://docs.cypress.io/api/cypress-api/browser.md): Cypress.browser returns you properties of the browser.
- [Catalog of Events](https://docs.cypress.io/api/cypress-api/catalog-of-events.md): Events that Cypress emits as it runs in your browser.
- [Cypress.config()](https://docs.cypress.io/api/cypress-api/config.md): Get and set configuration options in your tests.
- [Cypress.Cookies](https://docs.cypress.io/api/cypress-api/cookies.md): Generate logs to the console whenever any cookies are modified in Cypress.
- [Cypress.currentRetry](https://docs.cypress.io/api/cypress-api/currentretry.md): Cypress.currentRetry is a number representing the current test retry count.
- [Cypress.currentTest](https://docs.cypress.io/api/cypress-api/currenttest.md): Cypress.currentTest is an object representing the currently executing test instance, with properties to access the title of the test.
- [Custom Commands in Cypress](https://docs.cypress.io/api/cypress-api/custom-commands.md): Learn how to create custom Cypress commands and overwrite existing commands.
- [Custom Queries in Cypress](https://docs.cypress.io/api/cypress-api/custom-queries.md): Learn how to create custom queries in Cypress, which are synchronous, retriable, and idempotent.
- [Cypress.log()](https://docs.cypress.io/api/cypress-api/cypress-log.md): The internal API for controlling what gets printed to the Command Log of Cypress.
- [Cypress.dom](https://docs.cypress.io/api/cypress-api/dom.md): Cypress.dom.method() is a collection of DOM related helper methods in Cypress
- [Cypress.ElementSelector](https://docs.cypress.io/api/cypress-api/element-selector-api.md): Customize how Cypress chooses selectors in Studio and cy.prompt() by setting your preferred selector strategy.
- [Cypress.ensure](https://docs.cypress.io/api/cypress-api/ensure.md): Cypress.ensure is a collection of helper methods for making assertions. They are mostly useful when writing custom queries or custom commands.
- [Cypress.expose()](https://docs.cypress.io/api/cypress-api/expose.md): Read and write public configuration values in Cypress using Cypress.expose(). Learn syntax, examples, security considerations, and how it differs from cy.env().
- [Cypress.isBrowser()](https://docs.cypress.io/api/cypress-api/isbrowser.md): Check if the current browser matches the given name or filter.
- [Cypress.isCy()](https://docs.cypress.io/api/cypress-api/iscy.md): Cypress.isCy checks if a variable is a valid instance of cy or a cy chainable in Cypress.
- [Cypress.Keyboard](https://docs.cypress.io/api/cypress-api/keyboard-api.md): Set the default values for how the .type() command is executed in Cypress.
- [Cypress.platform](https://docs.cypress.io/api/cypress-api/platform.md): Get the underlying OS name as returned from Node's os.platform() in Cypress.
- [Cypress.require()](https://docs.cypress.io/api/cypress-api/require.md): Utilize dependencies within the cy.origin() callback function in Cypress.
- [Cypress.Screenshot](https://docs.cypress.io/api/cypress-api/screenshot-api.md): Set defaults for how screenshots are captured during .screenshot() and automatically on test failures in Cypress.
- [Cypress.session](https://docs.cypress.io/api/cypress-api/session.md): A collection of async session-related helper methods intended to be used alongside the cy.session() command.
- [Cypress.spec](https://docs.cypress.io/api/cypress-api/spec.md): Get the properties of the spec under test in Cypress
- [Cypress.stop()](https://docs.cypress.io/api/cypress-api/stop.md): Stop Cypress on failure or any other conditions
- [Cypress.testingType](https://docs.cypress.io/api/cypress-api/testing-type.md): Get the current testing type in Cypress.
- [Cypress.version](https://docs.cypress.io/api/cypress-api/version.md): Get the current version of Cypress you are running.
- [after:run event](https://docs.cypress.io/api/node-events/after-run-api.md): The after:run event fires after a run is finished in Cypress.
- [after:screenshot event](https://docs.cypress.io/api/node-events/after-screenshot-api.md): The after:screenshot event fires after a screenshot is taken in Cypress.
- [after:spec event](https://docs.cypress.io/api/node-events/after-spec-api.md): The after:spec event fires after a spec file is run in Cypress.
- [before:run event](https://docs.cypress.io/api/node-events/before-run-api.md): The before:run event fires before a run starts in Cypress.
- [before:spec event](https://docs.cypress.io/api/node-events/before-spec-api.md): The before:spec event fires before a spec file is run in Cypress.
- [before:browser:launch event](https://docs.cypress.io/api/node-events/browser-launch-api.md): The before:browser:launch event gives you the opportunity to modify the browser preferences, install extensions, add and remove command-line arguments, and modify other options before Cypress launches a browser.
- [Configuration API](https://docs.cypress.io/api/node-events/configuration-api.md): Modify configuration values and environment variables from your Cypress configuration.
- [Overview of Node Events in Cypress](https://docs.cypress.io/api/node-events/overview.md): Node event hooks enable you to tap into, modify, or extend the internal behavior of Cypress.
- [Preprocessors API](https://docs.cypress.io/api/node-events/preprocessors-api.md): Prepare support and spec files for the browser with preprocessors.
- [Cypress API: Table of Contents](https://docs.cypress.io/api/table-of-contents.md): Cypress commands, assertions, actions, and other commands to help write tests.
- [Cypress._](https://docs.cypress.io/api/utilities/_.md): Cypress automatically includes lodash and exposes it as Cypress._.
- [Cypress.$](https://docs.cypress.io/api/utilities/$.md): Cypress automatically includes jQuery and exposes it as Cypress.$.
- [Cypress.Blob](https://docs.cypress.io/api/utilities/blob.md): Cypress automatically includes a Blob library and exposes it as Cypress.Blob.
- [Cypress.Buffer](https://docs.cypress.io/api/utilities/buffer.md): Cypress automatically includes a Buffer polyfill for the browser and exposes it as Cypress.Buffer.
- [Cypress.minimatch()](https://docs.cypress.io/api/utilities/minimatch.md): Cypress automatically includes minimatch and exposes it as Cypress.minimatch.
- [Cypress.Promise()](https://docs.cypress.io/api/utilities/promise.md): Cypress automatically includes Bluebird and exposes it as Cypress.Promise.
- [Cypress.sinon](https://docs.cypress.io/api/utilities/sinon.md): Cypress automatically includes Sinon.JS and exposes it as Cypress.sinon.

## Cypress Cloud

- [Billing & usage in Cypress Cloud](https://docs.cypress.io/cloud/account-management/billing-and-usage.md): Understand your Cypress Cloud plan and the Billing & Usage page: how test results and AI prompts are metered, what happens when you reach your limit, how to set usage notifications, manage your payment method and billing email, download invoices, and request a free Open Source plan.
- [Data storage and controls in Cypress Cloud](https://docs.cypress.io/cloud/account-management/data-storage-and-masking.md): Learn how to mask and control test data that is sent to Cypress Cloud
- [Single sign-on (SSO) in Cypress Cloud](https://docs.cypress.io/cloud/account-management/enterprise-sso.md): Configure SSO with an enterprise identity provider such as Okta, SAML, Azure AD, or OneLogin for your Cypress Cloud organization.
- [Organizations in Cypress Cloud: how to manage application quality at scale](https://docs.cypress.io/cloud/account-management/organizations.md): Cypress Cloud organizations group your projects, users, teams, billing, and integrations in one place to manage application quality and access control at scale.
- [How to manage projects in Cypress Cloud](https://docs.cypress.io/cloud/account-management/projects.md): Learn how to set up a project to record test runs, manage project settings, transfer ownership of a project, and how to integrate with third party integrations.
- [Manage teams and project access in Cypress Cloud](https://docs.cypress.io/cloud/account-management/teams.md): Cypress Cloud teams group users to control which projects they can access. Learn to create teams, assign users and projects, and follow setup best practices.
- [Manage Users in Cypress Cloud: Invites, Roles & Permissions](https://docs.cypress.io/cloud/account-management/users.md): Learn how to invite users, assign roles and permissions, approve access requests, and manage user accounts in Cypress Cloud for secure, scalable team access.
- [Frequently asked questions (FAQ) in Cypress Cloud](https://docs.cypress.io/cloud/faq.md): Get answers to common questions about Cypress Cloud.
- [Enterprise reporting in Cypress Cloud](https://docs.cypress.io/cloud/features/analytics/enterprise-reporting.md): Enterprise Reporting in Cypress Cloud provides insights and data access to help you spot trends and anomalies, track usage, and govern your overall test program across all projects in your organization.
- [Types of analytics in Cypress Cloud](https://docs.cypress.io/cloud/features/analytics/overview.md): Compare the analytics available in Cypress Cloud — run trends, test suite size, flake rates, and enterprise reporting.
- [Project analytics & insights in Cypress Cloud](https://docs.cypress.io/cloud/features/analytics/project-analytics.md): Cypress Cloud provides Analytics to offer insight into metrics like runs over time, run duration and visibility into tests suite size over time.
- [Compare branches and runs in Cypress Cloud](https://docs.cypress.io/cloud/features/branch-review.md): Branch Review in Cypress Cloud surfaces the impact of Pull Requests on your test suite so you can catch regressions before they merge. Compare test results between branches and learn best practices for grouping test runs.
- [AI features in Cypress](https://docs.cypress.io/cloud/features/cypress-ai-features.md): Learn about AI-powered testing capabilities and tools in Cypress — including cy.prompt(), Studio AI, and Cloud AI features for test generation, self-healing, and failure analysis.
- [Detect and fix flaky tests in Cypress Cloud](https://docs.cypress.io/cloud/features/flaky-test-management.md): Detect, score, alert on, and fix flaky tests with Cypress Cloud. Track test suite reliability across CI and prioritize the flaky tests that matter most.
- [Recorded runs in Cypress Cloud](https://docs.cypress.io/cloud/features/recorded-runs.md): View and analyze recorded test runs in Cypress Cloud.
- [Load balancing specs in Cypress Cloud](https://docs.cypress.io/cloud/features/smart-orchestration/load-balancing.md): Cypress Cloud automatically balances your spec files across the machines in your CI provider to minimize run time, cut CI costs, and eliminate manual tuning.
- [Overview of smart orchestration in Cypress Cloud](https://docs.cypress.io/cloud/features/smart-orchestration/overview.md): Cypress Cloud provides Smart Orchestration features for use in CI to speed up test runs, accelerate debugging workflows, and reduce costs.
- [Parallelize tests in Cypress Cloud](https://docs.cypress.io/cloud/features/smart-orchestration/parallelization.md): Run tests in parallel across multiple machines to save time and money in Continuous Integration.
- [Re-run optimization | Re-run Failed Specs or Tests](https://docs.cypress.io/cloud/features/smart-orchestration/rerun-optimization.md): Re-run only the specs or tests that failed in CI and skip what already passed to reach a passing build faster and cut CI cost, with Cypress Cloud's experimental Re-run optimization feature.
- [Stop failed CI runs early with auto cancellation in Cypress Cloud](https://docs.cypress.io/cloud/features/smart-orchestration/run-cancellation.md): Stop wasting CI minutes on runs that have already failed. Auto Cancellation cancels a Cypress run once failures cross a threshold you control, saving time and money.
- [Run failed specs first with spec prioritization in Cypress Cloud](https://docs.cypress.io/cloud/features/smart-orchestration/spec-prioritization.md): Run previously failed specs first with Cypress Cloud Spec Prioritization to surface failures sooner, debug faster, and cut CI costs.
- [Debug failed and flaky tests with test replay in Cypress Cloud](https://docs.cypress.io/cloud/features/test-replay.md): Test Replay in Cypress Cloud allows developers to accurately and efficiently debug failed and flaky continuous integration test runs. It captures every test run detail, enabling developers to replay it and inspect the DOM, network requests, console logs, JavaScript errors, and element rendering as they happened in CI.
- [Try Cypress Cloud free for 30 days](https://docs.cypress.io/cloud/get-started/free-trial.md): Start a free 30-day trial of Cypress Cloud and experience every Enterprise feature, including 50,000 test results, with no credit card required.
- [Introduction to Cypress Cloud](https://docs.cypress.io/cloud/get-started/introduction.md): Cypress Cloud records your test runs to give you Test Replay, flake detection, parallelization, and analytics across CI.
- [Set up your project to record in Cypress Cloud](https://docs.cypress.io/cloud/get-started/setup.md): Connect your project to Cypress Cloud and record your first run to unlock Test Replay, parallelization, and analytics.
- [Debug failing tests in CI with Cypress Cloud](https://docs.cypress.io/cloud/guides/debug-failing-tests.md): Debug failing and flaky Cypress tests in CI with Cypress Cloud. Use Test Replay, AI error summaries, Branch Review, and Cloud MCP to find the root cause of a CI failure without reproducing it locally.
- [Integrate Bitbucket with Cypress Cloud](https://docs.cypress.io/cloud/integrations/bitbucket.md): Configure Bitbucket status checks and pull request comments to show Cypress test results from Cypress Cloud.
- [Cypress Cloud CLI: Debug CI failures from your terminal](https://docs.cypress.io/cloud/integrations/cloud-cli.md): Query Cypress Cloud runs, tests, and Test Replay data from the command line with the cy-cloud CLI. Built for developers and AI agents.
- [Cypress Cloud MCP: Agentic debugging](https://docs.cypress.io/cloud/integrations/cloud-mcp.md): Give AI coding assistants real-time access to your Cypress test results.
- [Cypress Cloud API for enterprise reporting](https://docs.cypress.io/cloud/integrations/data-extract-api.md): See test status, browsers tested, spec results, average run duration, and flaky test rates with the Cypress Cloud Data Extract API.
- [Integrate GitHub with Cypress Cloud](https://docs.cypress.io/cloud/integrations/github.md): Configure GitHub status checks and pull request comments to show Cypress test results from Cypress Cloud.
- [Integrate GitLab with Cypress Cloud](https://docs.cypress.io/cloud/integrations/gitlab.md): Configure GitLab status checks and merge request comments to show Cypress test results from Cypress Cloud.
- [Integrate Jira with Cypress Cloud](https://docs.cypress.io/cloud/integrations/jira.md): Create Jira issues directly from failing tests in Cypress Cloud, track issue history per test case, and link every issue back to the exact test run that surfaced the failure.
- [Integrate Microsoft Teams with Cypress Cloud](https://docs.cypress.io/cloud/integrations/microsoft-teams.md): Setup Microsoft Teams notifications for your Cypress Cloud organization and projects.
- [Integrate Slack with Cypress Cloud](https://docs.cypress.io/cloud/integrations/slack.md): Setup Slack notifications on failed runs, passed runs, flaky tests, and more for your Cypress Cloud organization and projects.
- [Integrate Webhooks with Cypress Cloud](https://docs.cypress.io/cloud/integrations/webhooks.md): Send Cypress Cloud run events to your own HTTPS endpoints, and verify their authenticity with a signing secret.

## Cypress Accessibility

- [Cypress Accessibility Release Notes](https://docs.cypress.io/accessibility/changelog.md): Stay up to date with the latest features, improvements, and bug fixes for Cypress Accessibility.
- [attributeFilters: control element identification in Cypress Accessibility](https://docs.cypress.io/accessibility/configuration/attributefilters.md): Use attributeFilters to stop dynamic, auto-generated, or state-based attributes from splitting one element into many or mis-grouping violations in Cypress Accessibility reports.
- [Axe Core® configuration in Cypress Accessibility](https://docs.cypress.io/accessibility/configuration/axe-core-configuration.md): How Cypress Accessibility runs the Axe Core® ruleset, which rules are off by default, and how Cypress can tune rules for your project.
- [components: add component and team context to Cypress Accessibility selectors](https://docs.cypress.io/accessibility/configuration/components.md): Make Cypress Accessibility append component-identifying attributes, such as data-component-name, data-team, or data-page-area, to violation target selectors so every finding shows which component, team, or region it belongs to.
- [elementFilters: ignore elements in Cypress Accessibility](https://docs.cypress.io/accessibility/configuration/elementfilters.md): Ignore elements in Cypress Accessibility reports with elementFilters, so third-party widgets and out-of-scope elements stop counting against your accessibility score.
- [data-a11y-ignore: ignore accessibility rules per element](https://docs.cypress.io/accessibility/configuration/ignoring-rules-per-element.md): Use the data-a11y-ignore attribute to exclude specific accessibility rules from elements in Cypress Accessibility.
- [Configure Cypress Accessibility](https://docs.cypress.io/accessibility/configuration/overview.md): Configure Cypress Accessibility to get an accessibility score you can trust: group URLs into views, ignore third-party elements, identify violations by your own attributes, and scope reports to the application you own.
- [profiles: apply config overrides by run tag](https://docs.cypress.io/accessibility/configuration/profiles.md): Use the profiles property to apply different Cypress Accessibility configuration to different runs, whether a narrow pull request gate, a full regression run, or per-team reports, selected automatically by run tag, without changing your test code.
- [significantAttributes: identify elements by your attributes in Cypress Accessibility](https://docs.cypress.io/accessibility/configuration/significantattributes.md): Make Cypress Accessibility identify elements and build violation target selectors from your own HTML attributes, such as data-component, aria-label, or data-automation-id, by adding them to the priority list of significant attributes.
- [viewFilters: exclude URLs from scans](https://docs.cypress.io/accessibility/configuration/viewfilters.md): The viewFilters configuration excludes URLs from Cypress Accessibility, so third-party pages and other URLs outside your control are left out of your accessibility reports.
- [views: group URLs with URL patterns in Cypress Accessibility](https://docs.cypress.io/accessibility/configuration/views.md): The views configuration groups related URLs into a single view in Cypress Accessibility using URL patterns, so accessibility reports and scores are organized around the real pages of your application instead of the shape of your test data.
- [Download an Accessibility report](https://docs.cypress.io/accessibility/connect-and-extend/download-reports.md): Export a Cypress run's accessibility violations as a CSV or JSON file for offline analysis, sharing, or handing to an AI agent.
- [Connect & extend Cypress Accessibility](https://docs.cypress.io/accessibility/connect-and-extend/overview.md): Ways to get Cypress Accessibility results out of Cypress Cloud and into your own files, pipelines, AI workflows, and reporting systems.
- [Accessibility Results API: enforce standards in CI](https://docs.cypress.io/accessibility/connect-and-extend/results-api.md): Programmatically fetch Accessibility results in a CI environment and fail your pipeline if your standards are not met.
- [How the accessibility score is calculated](https://docs.cypress.io/accessibility/core-concepts/accessibility-score.md): Cypress produces a top-line percentage score that indicates a general sense of accessibility for a project.
- [Cypress accessibility rules](https://docs.cypress.io/accessibility/core-concepts/cypress-rules.md): The custom accessibility rules Cypress layers on top of Axe Core® and how each one is evaluated.
- [How Cypress Accessibility identifies elements](https://docs.cypress.io/accessibility/core-concepts/element-identification.md): How Cypress Accessibility uniquely identifies elements across views and snapshots using HTML attributes, location, and other DOM signals.
- [How Cypress Accessibility works](https://docs.cypress.io/accessibility/core-concepts/how-it-works.md): Accessibility checks are powered by Axe Core® from Deque Systems based on common accessibility standards.
- [Cypress Accessibility FAQ](https://docs.cypress.io/accessibility/faq.md): Common Cypress Accessibility questions: which WCAG rules run, what the score means, inspecting and sharing a violation, fixing and ignoring violations, and configuring views and profiles.
- [What is Cypress Accessibility?](https://docs.cypress.io/accessibility/get-started/introduction.md): Cypress Accessibility provides organized, visual, and actionable accessibility reports, based completely on the tests you record to Cypress Cloud, and powered by Axe Core® by Deque Systems.
- [Set up Cypress Accessibility by recording a run in Cypress](https://docs.cypress.io/accessibility/get-started/setup.md): Set up Cypress Accessibility by recording a run. No code changes or configuration required.
- [Accessibility automation principles](https://docs.cypress.io/accessibility/guides/accessibility-automation.md): Apply these core principles to maximize the impact of Cypress Accessibility's automation: complement automation with human judgment for deeper insights, manage false positives effectively, and ensure robust assistive technology support.
- [Block pull requests and set policies in Cypress Accessibility](https://docs.cypress.io/accessibility/guides/block-pull-requests.md): Set policies and block pull requests automatically with Cypress Accessibility's Results API, enabling custom CI workflows to enforce accessibility standards and prevent regressions.
- [Compare accessibility reports in Cypress Accessibility](https://docs.cypress.io/accessibility/guides/compare-reports.md): Compare accessibility reports between two Cypress runs to spot new violations, regressions, and fixes before they merge.
- [Catch accessibility regressions: compare runs, block builds, track trends](https://docs.cypress.io/accessibility/guides/detect-changes.md): Catch new accessibility violations the moment they appear: compare two Cypress runs in Branch Review, block builds with the Results API, and track trends in analytics.
- [Fix accessibility violations: prioritize and work through a backlog](https://docs.cypress.io/accessibility/guides/improve-accessibility.md): Turn a large Cypress Accessibility report into work your team can finish: scope the report to the code you own, pick a first rule, fix it, and prove the fix landed before the code merges.
- [Cypress Accessibility guides](https://docs.cypress.io/accessibility/guides/introduction.md): Learn how to set goals and make progress using Cypress Accessibility, generate reports during local development cycles, and monitor a production website.
- [Accessibility feedback during local development](https://docs.cypress.io/accessibility/guides/local-development.md): Record one spec from your machine to get a full Cypress Accessibility report without waiting for CI: confirm a fix, catch the violation it introduced, and compare against your base branch before you push.
- [Maintain accessibility](https://docs.cypress.io/accessibility/guides/maintain-accessibility.md): Learn how to maintain long-term accessibility with Cypress, using continuous feedback and monitoring to prevent regressions and keep your application accessible.
- [Maximize coverage](https://docs.cypress.io/accessibility/guides/maximize-coverage.md): Expand accessibility testing by combining Cypress Accessibility's automated checks with custom assertions tailored to your application.
- [Monitor accessibility issues in production](https://docs.cypress.io/accessibility/guides/production-monitoring.md): Monitor accessibility issues in production by running scheduled Cypress tests against live environments, capturing dynamic content changes, and generating automated reports for a comprehensive accessibility overview.
- [Inspect accessibility results: element details and DOM snapshots](https://docs.cypress.io/accessibility/reports/element-detail-view.md): Open a failing accessibility rule in Cypress Cloud: pin the failing element in a live DOM snapshot, read the checks it failed, and hand the fix off as a deep link, a Markdown snippet, or a Jira issue.
- [Accessibility run-level reports](https://docs.cypress.io/accessibility/reports/run-level-reports.md): Review the main areas to pay attention to when first reviewing an accessibility report for a Cypress run.
- [Troubleshooting: Cypress Accessibility](https://docs.cypress.io/accessibility/troubleshooting.md): Fix common Cypress Accessibility report problems: ignored elements that still appear, scores that do not improve, rules you cannot resolve yet, noise from third-party UI, unstable violation selectors, and configuration that has no effect.
- [Work with AI agents in Cypress Accessibility](https://docs.cypress.io/accessibility/work-with-ai-agents.md): Use AI assistants alongside Cypress Accessibility: query Cloud results with Cypress Cloud MCP, file violations into Jira or another issue tracker without duplicates, align reports with component identification settings, and explore local browser LLM workflows.

## UI Coverage

- [Changelog: UI Coverage](https://docs.cypress.io/ui-coverage/changelog.md): Track new features, improvements, and bug fixes for Cypress UI Coverage, including configuration options, CI integrations, and Results API updates.
- [additionalInteractionCommands: count custom commands as coverage in UI Coverage](https://docs.cypress.io/ui-coverage/configuration/additionalinteractioncommands.md): Make Cypress UI Coverage count your custom Cypress commands and third-party commands, such as cypress-real-events realClick and realType, as interactions so the elements they touch are marked as tested.
- [allowedInteractionCommands: choose which commands count as coverage](https://docs.cypress.io/ui-coverage/configuration/allowedinteractioncommands.md): Use allowedInteractionCommands to control which Cypress interaction commands count as coverage for specific elements, so you can require a meaningful interaction or accept commands UI Coverage ignores by default.
- [attributeFilters: control element identification](https://docs.cypress.io/ui-coverage/configuration/attributefilters.md): Use attributeFilters to stop dynamic, auto-generated, or state-based attributes from splitting one element into many or mis-grouping elements in Cypress UI Coverage reports.
- [elementFilters: exclude elements from UI Coverage](https://docs.cypress.io/ui-coverage/configuration/elementfilters.md): Exclude elements from Cypress UI Coverage reports and scores with elementFilters, so third-party widgets and other untestable elements stop counting as untested.
- [elementGroups: group related elements in UI Coverage](https://docs.cypress.io/ui-coverage/configuration/elementgroups.md): The elementGroups configuration in Cypress UI Coverage groups related elements into a single unit, so testing one element counts as testing them all.
- [elements: rename and stabilize element identity in UI Coverage](https://docs.cypress.io/ui-coverage/configuration/elements.md): Rename elements and give them a stable identity in Cypress UI Coverage reports, so dynamic attributes do not create duplicate untested elements.
- [Configure UI Coverage in Cypress](https://docs.cypress.io/ui-coverage/configuration/overview.md): Configure Cypress UI Coverage to get a coverage score you can trust: ignore dynamic attributes, filter out noise, group elements, shape views, and count the interactions that matter.
- [profiles: apply config overrides by run tag](https://docs.cypress.io/ui-coverage/configuration/profiles.md): Use the profiles property to apply UI Coverage configuration overrides based on run tags.
- [significantAttributes: identify elements by your attributes in UI Coverage](https://docs.cypress.io/ui-coverage/configuration/significantattributes.md): Make Cypress UI Coverage identify, name, and group elements using your own HTML attributes, such as data-component, data-analytics-id, or aria-label, by adding them to the priority list of significant attributes.
- [viewFilters: exclude URLs from UI Coverage](https://docs.cypress.io/ui-coverage/configuration/viewfilters.md): The viewFilters configuration excludes URLs from UI Coverage reports and scores, so third-party pages, error pages, and the links that point to them stop counting against your coverage.
- [views: group URLs with URL patterns in UI Coverage](https://docs.cypress.io/ui-coverage/configuration/views.md): The `views` configuration groups related URLs into a single view in UI Coverage using URL patterns, so reports and scores reflect the actual pages of your application.
- [How UI Coverage groups related elements](https://docs.cypress.io/ui-coverage/core-concepts/element-grouping.md): UI Coverage automatically groups repeated interactive elements so they count once and a single test can cover the whole set. Learn the automatic grouping rules and how to customize them.
- [How UI Coverage identifies elements](https://docs.cypress.io/ui-coverage/core-concepts/element-identification.md): How Cypress UI Coverage gives each interactive element a stable, unique identity across DOM snapshots, using test attributes like data-cy, an id and name fallback, and DOM structure, so the same control counts once and your coverage score stays accurate.
- [How UI Coverage detects interactive elements](https://docs.cypress.io/ui-coverage/core-concepts/interactivity.md): Understand what drives your UI Coverage score: the interactive elements Cypress tracks, the commands that mark them as tested, and the links to unvisited pages it flags, plus the overrides that make each one match your app.
- [Views: pages and components in UI Coverage](https://docs.cypress.io/ui-coverage/core-concepts/views.md): How UI Coverage groups the URLs your tests visit into views: URL pattern rules, per-view coverage scores, and configuration to group or exclude URLs.
- [Cypress UI Coverage FAQ](https://docs.cypress.io/ui-coverage/faq.md): Answers to common questions about Cypress UI Coverage: how it differs from code coverage, coverage scores, closing gaps, configuration, and the Results API.
- [What is UI Coverage?](https://docs.cypress.io/ui-coverage/get-started/introduction.md): UI Coverage turns your recorded Cypress runs into a visual map of which interactive elements your tests cover, and which they miss. No code changes needed.
- [Get started with Cypress UI Coverage](https://docs.cypress.io/ui-coverage/get-started/setup.md): Record a run with Test Replay, read your UI Coverage report, and tune it with App Quality configuration — no code changes or instrumentation required.
- [Address coverage gaps with UI Coverage](https://docs.cypress.io/ui-coverage/guides/address-coverage-gaps.md): A workflow for closing UI Coverage gaps: confirm each gap is worth testing, close it with an AI agent, Test Generation, or a targeted test, then validate and enforce the coverage you gained so it stays closed.
- [Block pull requests with UI Coverage policies](https://docs.cypress.io/ui-coverage/guides/block-pull-requests.md): Block pull requests with Cypress UI Coverage: use the Results API to fail a build when coverage drops below a threshold or a run introduces new untested elements.
- [Compare UI Coverage reports across runs](https://docs.cypress.io/ui-coverage/guides/compare-reports.md): Compare two UI Coverage reports to see which parts of your UI lost or gained test coverage between runs, using Branch Review in Cypress Cloud or the Cypress Cloud MCP from your editor, so you can catch new gaps before they merge.
- [Identify coverage gaps with UI Coverage](https://docs.cypress.io/ui-coverage/guides/identify-coverage-gaps.md): A step-by-step workflow to find the untested buttons, forms, links, and pages in your app using Cypress UI Coverage reports, with no code instrumentation required.
- [Ignore elements in UI Coverage reports](https://docs.cypress.io/ui-coverage/guides/ignore-elements.md): Exclude third-party widgets, chat launchers, cookie banners, and other out-of-scope elements from Cypress UI Coverage with elementFilters, so your coverage score and untested-elements list stay focused on real gaps.
- [Ignore views and links in UI Coverage](https://docs.cypress.io/ui-coverage/guides/ignore-views-and-links.md): Exclude third-party pages, error redirects, and links you never plan to test from UI Coverage with viewFilters, so your coverage score reflects only the parts of your app you own and intend to test.
- [Monitor UI Coverage changes over time](https://docs.cypress.io/ui-coverage/guides/monitor-changes.md): Set up a repeatable workflow to catch UI Coverage regressions before they merge and track coverage trends across your projects.
- [Reduce noise in UI Coverage reports](https://docs.cypress.io/ui-coverage/guides/reduce-noise.md): A workflow for turning a noisy UI Coverage report into an actionable one: recognize the noise, diagnose its cause, apply the matching fix, and validate.
- [Reduce test duplication with UI Coverage](https://docs.cypress.io/ui-coverage/guides/reduce-test-duplication.md): A step-by-step workflow for using Cypress UI Coverage to find the elements your suite tests far more than it needs to, then consolidate that repeated setup to cut CI time without losing coverage.
- [UI Coverage Results API: enforce coverage in CI](https://docs.cypress.io/ui-coverage/results-api.md): Programmatically fetch UI Coverage results in CI with @cypress/extract-cloud-results, then block pull requests or fail the build when coverage drops below your thresholds.
- [Troubleshooting: UI Coverage](https://docs.cypress.io/ui-coverage/troubleshooting.md): Fix common Cypress UI Coverage report problems: duplicate elements, mis-grouped elements, tested elements shown as untested, configuration that has no effect, and unexpected coverage scores.
- [Use AI agents with UI Coverage](https://docs.cypress.io/ui-coverage/work-with-ai-agents.md): Use AI agents with UI Coverage and Cypress Cloud MCP to pull coverage scores and untested elements from recorded runs and turn gaps into drafted tests.