{
"doc": {
"id": "app/get-started/why-cypress",
"title": "Cypress testing solutions | Cypress Documentation",
"description": "Explore Cypress documentation for a comprehensive guide on end-to-end, component, and accessibility testing. Discover features, commands, best practices, and get started with Cypress today",
"section": "app",
"source_path": "/llm/markdown/app/get-started/why-cypress.md",
"version": "3cf5b86b3403f604bdf7f3e35025c3bc3865e02c",
"updated_at": "2026-05-07T17:44:31.931Z",
"headings": [
{
"id": "app/get-started/why-cypress#why-cypress",
"text": "Why Cypress?",
"level": 1
},
{
"id": "app/get-started/why-cypress#what-youll-learn",
"text": "What you'll learn",
"level": 5
},
{
"id": "app/get-started/why-cypress#in-a-nutshell",
"text": "In a nutshell",
"level": 2
},
{
"id": "app/get-started/why-cypress#products",
"text": "Products",
"level": 2
},
{
"id": "app/get-started/why-cypress#features",
"text": "Features",
"level": 2
},
{
"id": "app/get-started/why-cypress#cypress-app",
"text": "Cypress App",
"level": 3
},
{
"id": "app/get-started/why-cypress#cypress-cloud",
"text": "Cypress Cloud",
"level": 3
},
{
"id": "app/get-started/why-cypress#cypress-accessibility",
"text": "Cypress Accessibility",
"level": 3
},
{
"id": "app/get-started/why-cypress#ui-coverage",
"text": "UI Coverage",
"level": 3
},
{
"id": "app/get-started/why-cypress#solutions",
"text": "Solutions",
"level": 2
},
{
"id": "app/get-started/why-cypress#end-to-end-testing",
"text": "End-to-end Testing",
"level": 3
},
{
"id": "app/get-started/why-cypress#component-testing",
"text": "Component Testing",
"level": 3
},
{
"id": "app/get-started/why-cypress#accessibility-testing",
"text": "Accessibility Testing",
"level": 3
},
{
"id": "app/get-started/why-cypress#ui-coverage",
"text": "UI Coverage",
"level": 3
},
{
"id": "app/get-started/why-cypress#other",
"text": "Other",
"level": 3
},
{
"id": "app/get-started/why-cypress#our-mission",
"text": "Our mission",
"level": 2
},
{
"id": "app/get-started/why-cypress#key-differences",
"text": "Key Differences",
"level": 2
},
{
"id": "app/get-started/why-cypress#architecture",
"text": "Architecture",
"level": 3
},
{
"id": "app/get-started/why-cypress#native-access",
"text": "Native access",
"level": 3
},
{
"id": "app/get-started/why-cypress#shortcuts",
"text": "Shortcuts",
"level": 3
},
{
"id": "app/get-started/why-cypress#flake-resistant",
"text": "Flake resistant",
"level": 3
},
{
"id": "app/get-started/why-cypress#debuggability",
"text": "Debuggability",
"level": 3
},
{
"id": "app/get-started/why-cypress#trade-offs",
"text": "Trade offs",
"level": 3
},
{
"id": "app/get-started/why-cypress#get-started",
"text": "Get Started",
"level": 2
},
{
"id": "app/get-started/why-cypress#cypress-in-the-real-world",
"text": "Cypress in the Real World",
"level": 2
}
]
},
"chunks": [
{
"id": "app/get-started/why-cypress#what-youll-learn",
"doc_id": "app/get-started/why-cypress",
"heading": "What you'll learn",
"heading_level": 5,
"content_markdown": "##### What you'll learn\n\n* The solutions Cypress provides for testing\n* The features of Cypress App, Cypress Cloud, UI Coverage, and Cypress Accessibility\n* Our mission and what we believe in\n* Key differences between Cypress and other testing tools\n",
"section": "app",
"anchors": [
"what-youll-learn"
],
"path": "/llm/json/chunked/app/get-started/why-cypress.json",
"token_estimate": 55
},
{
"id": "app/get-started/why-cypress#in-a-nutshell",
"doc_id": "app/get-started/why-cypress",
"heading": "In a nutshell",
"heading_level": 2,
"content_markdown": "## In a nutshell\n\nCypress is a next generation front end testing tool built for the modern web. We address the key pain points teams face when testing modern applications and maintaining test suites.\n\nOur users are typically developers, QA engineers, and teams looking to build web applications and increase the quality of their existing applications.\n\nCypress provides solutions for:\n\n* [End-to-end testing](#End-to-end-Testing)\n* [Component testing](#Component-Testing)\n* [Accessibility testing](#Accessibility-Testing)\n* [UI Coverage](#UI-Coverage-1)\n* [and more...](#Other)\n\nCypress can test anything that runs in a browser and surface insights into how to improve the health of your test suite and the quality of your application.\n",
"section": "app",
"anchors": [
"in-a-nutshell"
],
"path": "/llm/json/chunked/app/get-started/why-cypress.json",
"token_estimate": 137
},
{
"id": "app/get-started/why-cypress#products",
"doc_id": "app/get-started/why-cypress",
"heading": "Products",
"heading_level": 2,
"content_markdown": "## Products\n\n* [Cypress App](/llm/markdown/app/core-concepts/open-mode.md), a free, [open source](https://github.com/cypress-io/cypress), locally installed app for writing and running tests.\n* [Cypress Cloud](/llm/markdown/cloud/get-started/introduction.md), a paid service for recording tests, surfacing test results, and providing test analytics.\n* [UI Coverage](/llm/markdown/ui-coverage/get-started/introduction.md), a premium solution providing a visual overview of test coverage across every page and component of your app, offering clear insights into uncovered areas that everyone can understand.\n* [Cypress Accessibility](/llm/markdown/accessibility/get-started/introduction.md), a premium solution providing accessibility checks, which helps detect barriers for people with disabilities using your application.\n\nCypress is a robust solution that can improve the quality of your application.\n\n* **First:** Cypress helps you set up and start writing tests every day while you build your application locally. _Test Driven Development at its best!_\n* **Next:** After building up a suite of tests and [integrating Cypress](/llm/markdown/app/continuous-integration/overview.md) with your CI Provider, [Cypress Cloud](/llm/markdown/cloud/get-started/introduction.md) can record your test runs surfacing exactly what happened during the test in [Test Replay](/llm/markdown/cloud/features/test-replay.md). Use [Cloud MCP](/llm/markdown/cloud/integrations/cloud-mcp.md) to give your AI coding assistant the same run and failure context in your IDE. You'll never have to wonder: _Why did this fail?_\n* **Finally:** Add on [Cypress Accessibility](/llm/markdown/accessibility/get-started/introduction.md) to get continuous feedback on accessibility issues and regressions, and [UI Coverage](/llm/markdown/ui-coverage/get-started/introduction.md) to ensure you've tested every part of your application.\n",
"section": "app",
"anchors": [
"products"
],
"path": "/llm/json/chunked/app/get-started/why-cypress.json",
"token_estimate": 279
},
{
"id": "app/get-started/why-cypress#features",
"doc_id": "app/get-started/why-cypress",
"heading": "Features",
"heading_level": 2,
"content_markdown": "## Features\n\nBelow are listed some of the key features of each product.\n\n### Cypress App\n\n* **Time Travel:** Cypress takes snapshots as your tests run. Hover over commands in the [Command Log](/llm/markdown/app/core-concepts/open-mode.md#Command-Log) to see exactly what happened at each step.\n* **Debuggability:** Stop guessing why your tests are failing. [Debug directly](/llm/markdown/app/guides/debugging.md) from familiar tools like Developer Tools. Our readable errors and stack traces make debugging lightning fast.\n* **Automatic Waiting:** Never add waits or sleeps to your tests. Cypress [automatically waits](/llm/markdown/app/core-concepts/introduction-to-cypress.md#Cypress-is-Not-Like-jQuery) for commands and assertions before moving on. No more async hell.\n* **Spies, Stubs, and Clocks:** Verify and [control the behavior](/llm/markdown/app/guides/stubs-spies-and-clocks.md) of functions, server responses, or timers. The same functionality you love from unit testing is right at your fingertips.\n* **Network Traffic Control:** Easily [control, stub, and test edge cases](/llm/markdown/app/guides/network-requests.md) without involving your server. You can stub network traffic however you like.\n* **Consistent Results:** Our architecture doesn't use Selenium or WebDriver. Say hello to fast, consistent and reliable tests that are flake-free.\n* **Cypress Studio & Studio AI:** Record interactions in your app to generate and extend E2E tests, and let [Studio AI](/llm/markdown/app/guides/cypress-studio.md) recommend assertions automatically so you write less and cover more.\n* **Cross Browser Testing:** Run tests within Firefox and Chrome-family browsers (including Edge and Electron) locally and [in a Continuous Integration pipeline](/llm/markdown/app/guides/cross-browser-testing.md).\n\n### Cypress Cloud\n\n* **Test Replay:** Record to [Cypress Cloud](/llm/markdown/cloud/get-started/introduction.md) and replay the test exactly as it executed during the run for zero-configuration debugging using [Test Replay](/llm/markdown/cloud/features/test-replay.md).\n* **Smart Orchestration:** Once you're set up to record to Cypress Cloud, easily [parallelize](/llm/markdown/cloud/features/smart-orchestration/parallelization.md) your test suite, rerun failed specs first with [Spec Prioritization](/llm/markdown/cloud/features/smart-orchestration/spec-prioritization.md), and cancel test runs on failures with [Auto Cancellation](/llm/markdown/cloud/features/smart-orchestration/run-cancellation.md) for tight feedback loops.\n* **Flake Detection:** Discover and diagnose unreliable tests with Cypress Cloud's [Flaky test management](/llm/markdown/cloud/features/flaky-test-management.md).\n* **Branch Review:** Quickly identify the impact a pull request might have on your test suite in a single view using [Branch Review](/llm/markdown/cloud/features/branch-review.md). Compare which tests are failing, flaky, pending, added, or modified between the source and base branches and prevent the merging of low-quality code.\n* **Integrations:** Integrate with [GitHub](/llm/markdown/cloud/integrations/github.md), [GitLab](/llm/markdown/cloud/integrations/gitlab.md), or [Bitbucket](/llm/markdown/cloud/integrations/bitbucket.md) to see test results directly on every push or pull request. Cypress Cloud also integrates with [Slack](/llm/markdown/cloud/integrations/slack.md), [Jira](/llm/markdown/cloud/integrations/jira.md), and [Microsoft Teams](/llm/markdown/cloud/integrations/teams.md) to keep your team in the loop.\n* **Test Analytics:** Track test results over time with [Test Analytics](/llm/markdown/cloud/features/analytics/overview.md) to identify trends, regressions, and improvements in your test suite. Use our [Data Extract API](/llm/markdown/cloud/integrations/data-extract-api.md) to extract the data that is important to your team.\n* **Cypress Cloud MCP** : Give AI coding assistants a direct window into your application's health and stability by connecting to [Cypress Cloud MCP](/llm/markdown/cloud/integrations/cloud-mcp.md).\n\n### Cypress Accessibility\n\n* **Accessibility Checks:** Maximize the value of your existing Cypress tests by instantly adding thousands of [accessibility checks](/llm/markdown/accessibility/get-started/introduction.md) with no setup, code changes, or performance penalty.\n* **Run-level reports:** Get a detailed report of accessibility issues found in your test runs with [Run-level reports](/llm/markdown/accessibility/core-concepts/run-level-reports.md).\n* **Results where you work:** Use the [Results API](/llm/markdown/accessibility/guides/results-api.md) to integrate results into CI, and [Cloud MCP](/llm/markdown/cloud/integrations/cloud-mcp.md) to surface them in your AI agent for faster diagnosis and iteration.\n* **Branch Review:** Compare any report against a baseline to review only the new violations, without any noise from existing issues.\n\n### UI Coverage\n\n* **Visualize Coverage:** [UI Coverage](/llm/markdown/ui-coverage/get-started/introduction.md) provides a visual overview of test coverage across every page and component of your app, offering clear insights into uncovered areas that everyone can understand.\n* **Results API:** Use the UI Coverage [Results API](/llm/markdown/ui-coverage/results-api.md) to programmatically access test coverage data and integrate it into your existing workflows.\n* **Branch Review:** Compare runs to see newly introduced elements in your application or unexpected reductions in test coverage.\n",
"section": "app",
"anchors": [
"features"
],
"path": "/llm/json/chunked/app/get-started/why-cypress.json",
"token_estimate": 813
},
{
"id": "app/get-started/why-cypress#cypress-app",
"doc_id": "app/get-started/why-cypress",
"heading": "Cypress App",
"heading_level": 3,
"content_markdown": "### Cypress App\n\n* **Time Travel:** Cypress takes snapshots as your tests run. Hover over commands in the [Command Log](/llm/markdown/app/core-concepts/open-mode.md#Command-Log) to see exactly what happened at each step.\n* **Debuggability:** Stop guessing why your tests are failing. [Debug directly](/llm/markdown/app/guides/debugging.md) from familiar tools like Developer Tools. Our readable errors and stack traces make debugging lightning fast.\n* **Automatic Waiting:** Never add waits or sleeps to your tests. Cypress [automatically waits](/llm/markdown/app/core-concepts/introduction-to-cypress.md#Cypress-is-Not-Like-jQuery) for commands and assertions before moving on. No more async hell.\n* **Spies, Stubs, and Clocks:** Verify and [control the behavior](/llm/markdown/app/guides/stubs-spies-and-clocks.md) of functions, server responses, or timers. The same functionality you love from unit testing is right at your fingertips.\n* **Network Traffic Control:** Easily [control, stub, and test edge cases](/llm/markdown/app/guides/network-requests.md) without involving your server. You can stub network traffic however you like.\n* **Consistent Results:** Our architecture doesn't use Selenium or WebDriver. Say hello to fast, consistent and reliable tests that are flake-free.\n* **Cypress Studio & Studio AI:** Record interactions in your app to generate and extend E2E tests, and let [Studio AI](/llm/markdown/app/guides/cypress-studio.md) recommend assertions automatically so you write less and cover more.\n* **Cross Browser Testing:** Run tests within Firefox and Chrome-family browsers (including Edge and Electron) locally and [in a Continuous Integration pipeline](/llm/markdown/app/guides/cross-browser-testing.md).\n",
"section": "app",
"anchors": [
"cypress-app"
],
"path": "/llm/json/chunked/app/get-started/why-cypress.json",
"token_estimate": 275
},
{
"id": "app/get-started/why-cypress#cypress-cloud",
"doc_id": "app/get-started/why-cypress",
"heading": "Cypress Cloud",
"heading_level": 3,
"content_markdown": "### Cypress Cloud\n\n* **Test Replay:** Record to [Cypress Cloud](/llm/markdown/cloud/get-started/introduction.md) and replay the test exactly as it executed during the run for zero-configuration debugging using [Test Replay](/llm/markdown/cloud/features/test-replay.md).\n* **Smart Orchestration:** Once you're set up to record to Cypress Cloud, easily [parallelize](/llm/markdown/cloud/features/smart-orchestration/parallelization.md) your test suite, rerun failed specs first with [Spec Prioritization](/llm/markdown/cloud/features/smart-orchestration/spec-prioritization.md), and cancel test runs on failures with [Auto Cancellation](/llm/markdown/cloud/features/smart-orchestration/run-cancellation.md) for tight feedback loops.\n* **Flake Detection:** Discover and diagnose unreliable tests with Cypress Cloud's [Flaky test management](/llm/markdown/cloud/features/flaky-test-management.md).\n* **Branch Review:** Quickly identify the impact a pull request might have on your test suite in a single view using [Branch Review](/llm/markdown/cloud/features/branch-review.md). Compare which tests are failing, flaky, pending, added, or modified between the source and base branches and prevent the merging of low-quality code.\n* **Integrations:** Integrate with [GitHub](/llm/markdown/cloud/integrations/github.md), [GitLab](/llm/markdown/cloud/integrations/gitlab.md), or [Bitbucket](/llm/markdown/cloud/integrations/bitbucket.md) to see test results directly on every push or pull request. Cypress Cloud also integrates with [Slack](/llm/markdown/cloud/integrations/slack.md), [Jira](/llm/markdown/cloud/integrations/jira.md), and [Microsoft Teams](/llm/markdown/cloud/integrations/teams.md) to keep your team in the loop.\n* **Test Analytics:** Track test results over time with [Test Analytics](/llm/markdown/cloud/features/analytics/overview.md) to identify trends, regressions, and improvements in your test suite. Use our [Data Extract API](/llm/markdown/cloud/integrations/data-extract-api.md) to extract the data that is important to your team.\n* **Cypress Cloud MCP** : Give AI coding assistants a direct window into your application's health and stability by connecting to [Cypress Cloud MCP](/llm/markdown/cloud/integrations/cloud-mcp.md).\n",
"section": "app",
"anchors": [
"cypress-cloud"
],
"path": "/llm/json/chunked/app/get-started/why-cypress.json",
"token_estimate": 293
},
{
"id": "app/get-started/why-cypress#cypress-accessibility",
"doc_id": "app/get-started/why-cypress",
"heading": "Cypress Accessibility",
"heading_level": 3,
"content_markdown": "### Cypress Accessibility\n\n* **Accessibility Checks:** Maximize the value of your existing Cypress tests by instantly adding thousands of [accessibility checks](/llm/markdown/accessibility/get-started/introduction.md) with no setup, code changes, or performance penalty.\n* **Run-level reports:** Get a detailed report of accessibility issues found in your test runs with [Run-level reports](/llm/markdown/accessibility/core-concepts/run-level-reports.md).\n* **Results where you work:** Use the [Results API](/llm/markdown/accessibility/guides/results-api.md) to integrate results into CI, and [Cloud MCP](/llm/markdown/cloud/integrations/cloud-mcp.md) to surface them in your AI agent for faster diagnosis and iteration.\n* **Branch Review:** Compare any report against a baseline to review only the new violations, without any noise from existing issues.\n",
"section": "app",
"anchors": [
"cypress-accessibility"
],
"path": "/llm/json/chunked/app/get-started/why-cypress.json",
"token_estimate": 129
},
{
"id": "app/get-started/why-cypress#ui-coverage",
"doc_id": "app/get-started/why-cypress",
"heading": "UI Coverage",
"heading_level": 3,
"content_markdown": "### UI Coverage\n\n* **Visualize Coverage:** [UI Coverage](/llm/markdown/ui-coverage/get-started/introduction.md) provides a visual overview of test coverage across every page and component of your app, offering clear insights into uncovered areas that everyone can understand.\n* **Results API:** Use the UI Coverage [Results API](/llm/markdown/ui-coverage/results-api.md) to programmatically access test coverage data and integrate it into your existing workflows.\n* **Branch Review:** Compare runs to see newly introduced elements in your application or unexpected reductions in test coverage.\n",
"section": "app",
"anchors": [
"ui-coverage"
],
"path": "/llm/json/chunked/app/get-started/why-cypress.json",
"token_estimate": 99
},
{
"id": "app/get-started/why-cypress#solutions",
"doc_id": "app/get-started/why-cypress",
"heading": "Solutions",
"heading_level": 2,
"content_markdown": "## Solutions\n\nCypress can be used to ensure several different types of test. This can provide even more confidence that your application under test is working as intended and accessible to all users.\n\n### End-to-end Testing\n\nCypress was originally designed to run [end-to-end (E2E) tests](/llm/markdown/app/end-to-end-testing/writing-your-first-end-to-end-test.md) on anything that runs in a browser. A typical E2E test visits the application in a browser and performs actions via the UI just like a real user would.\n\n```\nit('adds todos', () => { cy.visit('https://example.cypress.io/') cy.get('[data-cy=\"new-todo\"]').type('write tests{enter}') // confirm the application is showing one item cy.get('[data-cy=\"todos\"]').should('have.length', 1)})\n```\n\n### Component Testing\n\nCypress [Component Testing](/llm/markdown/app/component-testing/get-started.md) provides a component workbench for you to quickly build and test components from multiple front-end UI libraries — no matter how simple or complex.\n\nLearn more about how to test components for [React](/llm/markdown/app/component-testing/react/overview.md), [Angular](/llm/markdown/app/component-testing/angular/overview.md), [Vue](/llm/markdown/app/component-testing/vue/overview.md), and [Svelte](/llm/markdown/app/component-testing/svelte/overview.md).\n\n* React\n* Angular\n* Vue\n* Svelte\n\n```\nimport Button from './Button'it('uses custom text for the button label', () => { cy.mount() // Assert that a button component has the correct text cy.get('button').should('contains.text', 'Click me!')})\n```\n\n```\nimport ButtonComponent from './button.component'it('uses custom text for the button label', () => { cy.mount('Click me!', { declarations: [ButtonComponent], }) // Assert that a button component has the correct text cy.get('button').should('contains.text', 'Click me!')})\n```\n\n```\nimport Button from './Button.vue'it('uses custom text for the button label', () => { cy.mount(Button, { slots: { default: 'Click me!', }, }) // Assert that a button component has the correct text cy.get('button').should('contains.text', 'Click me!')})\n```\n\n```\nimport Button from './Button.svelte'it('uses custom text for the button label', () => { cy.mount(Button, { props: { msg: 'Click me!' } }) // Assert that a button component has the correct text cy.get('button').should('contains.text', 'Click me!')})\n```\n\n### Accessibility Testing\n\nYou can write Cypress tests to check the accessibility of your application, and use plugins to run broad accessibility scans. When combined with [Cypress Accessibility](/llm/markdown/accessibility/get-started/introduction.md) in Cypress Cloud, insights can be surfaced when specific accessibility standards are not met through your testing - with no configuration required. See our [Accessibility Testing guide](/llm/markdown/app/guides/accessibility-testing.md) for more details.\n\n```\nit('adds todos', () => { cy.visit('https://example.cypress.io/') cy.get('img#logo') // Assert that an image has the correct alt text .should('have.attr', 'alt', 'Cypress Logo')})\n```\n\n### UI Coverage\n\nYou can increase release confidence by closing testing gaps in critical app flows using [UI Coverage](/llm/markdown/ui-coverage/get-started/introduction.md). Leverage data-driven insights to cover untested areas, reduce incidents, and improve app quality.\n\n### Other\n\nCypress can perform arbitrary HTTP calls, thus you can use it for API testing.\n\n```\nit('adds a todo', () => { cy.request('POST', '/todos', { title: 'Write API Tests' }) .its('body') .should('contain', { title: 'Write API Tests' })})\n```\n\nAnd through a large number of [official and 3rd party plugins](/llm/markdown/app/plugins/plugins-list.md) you can write many other types of tests!\n",
"section": "app",
"anchors": [
"solutions"
],
"path": "/llm/json/chunked/app/get-started/why-cypress.json",
"token_estimate": 607
},
{
"id": "app/get-started/why-cypress#end-to-end-testing",
"doc_id": "app/get-started/why-cypress",
"heading": "End-to-end Testing",
"heading_level": 3,
"content_markdown": "### End-to-end Testing\n\nCypress was originally designed to run [end-to-end (E2E) tests](/llm/markdown/app/end-to-end-testing/writing-your-first-end-to-end-test.md) on anything that runs in a browser. A typical E2E test visits the application in a browser and performs actions via the UI just like a real user would.\n\n```\nit('adds todos', () => { cy.visit('https://example.cypress.io/') cy.get('[data-cy=\"new-todo\"]').type('write tests{enter}') // confirm the application is showing one item cy.get('[data-cy=\"todos\"]').should('have.length', 1)})\n```\n",
"section": "app",
"anchors": [
"end-to-end-testing"
],
"path": "/llm/json/chunked/app/get-started/why-cypress.json",
"token_estimate": 81
},
{
"id": "app/get-started/why-cypress#component-testing",
"doc_id": "app/get-started/why-cypress",
"heading": "Component Testing",
"heading_level": 3,
"content_markdown": "### Component Testing\n\nCypress [Component Testing](/llm/markdown/app/component-testing/get-started.md) provides a component workbench for you to quickly build and test components from multiple front-end UI libraries — no matter how simple or complex.\n\nLearn more about how to test components for [React](/llm/markdown/app/component-testing/react/overview.md), [Angular](/llm/markdown/app/component-testing/angular/overview.md), [Vue](/llm/markdown/app/component-testing/vue/overview.md), and [Svelte](/llm/markdown/app/component-testing/svelte/overview.md).\n\n* React\n* Angular\n* Vue\n* Svelte\n\n```\nimport Button from './Button'it('uses custom text for the button label', () => { cy.mount() // Assert that a button component has the correct text cy.get('button').should('contains.text', 'Click me!')})\n```\n\n```\nimport ButtonComponent from './button.component'it('uses custom text for the button label', () => { cy.mount('Click me!', { declarations: [ButtonComponent], }) // Assert that a button component has the correct text cy.get('button').should('contains.text', 'Click me!')})\n```\n\n```\nimport Button from './Button.vue'it('uses custom text for the button label', () => { cy.mount(Button, { slots: { default: 'Click me!', }, }) // Assert that a button component has the correct text cy.get('button').should('contains.text', 'Click me!')})\n```\n\n```\nimport Button from './Button.svelte'it('uses custom text for the button label', () => { cy.mount(Button, { props: { msg: 'Click me!' } }) // Assert that a button component has the correct text cy.get('button').should('contains.text', 'Click me!')})\n```\n",
"section": "app",
"anchors": [
"component-testing"
],
"path": "/llm/json/chunked/app/get-started/why-cypress.json",
"token_estimate": 252
},
{
"id": "app/get-started/why-cypress#accessibility-testing",
"doc_id": "app/get-started/why-cypress",
"heading": "Accessibility Testing",
"heading_level": 3,
"content_markdown": "### Accessibility Testing\n\nYou can write Cypress tests to check the accessibility of your application, and use plugins to run broad accessibility scans. When combined with [Cypress Accessibility](/llm/markdown/accessibility/get-started/introduction.md) in Cypress Cloud, insights can be surfaced when specific accessibility standards are not met through your testing - with no configuration required. See our [Accessibility Testing guide](/llm/markdown/app/guides/accessibility-testing.md) for more details.\n\n```\nit('adds todos', () => { cy.visit('https://example.cypress.io/') cy.get('img#logo') // Assert that an image has the correct alt text .should('have.attr', 'alt', 'Cypress Logo')})\n```\n",
"section": "app",
"anchors": [
"accessibility-testing"
],
"path": "/llm/json/chunked/app/get-started/why-cypress.json",
"token_estimate": 108
},
{
"id": "app/get-started/why-cypress#ui-coverage",
"doc_id": "app/get-started/why-cypress",
"heading": "UI Coverage",
"heading_level": 3,
"content_markdown": "### UI Coverage\n\nYou can increase release confidence by closing testing gaps in critical app flows using [UI Coverage](/llm/markdown/ui-coverage/get-started/introduction.md). Leverage data-driven insights to cover untested areas, reduce incidents, and improve app quality.\n",
"section": "app",
"anchors": [
"ui-coverage"
],
"path": "/llm/json/chunked/app/get-started/why-cypress.json",
"token_estimate": 43
},
{
"id": "app/get-started/why-cypress#other",
"doc_id": "app/get-started/why-cypress",
"heading": "Other",
"heading_level": 3,
"content_markdown": "### Other\n\nCypress can perform arbitrary HTTP calls, thus you can use it for API testing.\n\n```\nit('adds a todo', () => { cy.request('POST', '/todos', { title: 'Write API Tests' }) .its('body') .should('contain', { title: 'Write API Tests' })})\n```\n\nAnd through a large number of [official and 3rd party plugins](/llm/markdown/app/plugins/plugins-list.md) you can write many other types of tests!\n",
"section": "app",
"anchors": [
"other"
],
"path": "/llm/json/chunked/app/get-started/why-cypress.json",
"token_estimate": 79
},
{
"id": "app/get-started/why-cypress#our-mission",
"doc_id": "app/get-started/why-cypress",
"heading": "Our mission",
"heading_level": 2,
"content_markdown": "## Our mission\n\nOur mission is to build a thriving testing solution that enhances productivity, makes testing an enjoyable experience, and generates developer happiness. We hold ourselves accountable to champion a testing process **that actually works**.\n\nWe believe our documentation should be approachable. This means enabling our readers to understand fully not just the **what** but the **why** as well.\n\nWe want to help developers build a new generation of modern applications faster, better, and without the stress and anxiety associated with managing tests. We aim to elevate the art of software development by leveraging test results to generate actionable insights for long-term stability by proactively identifying areas for improvement.\n\nWe know that in order for us to be successful we must enable, nurture, and foster an ecosystem that thrives on open source. Every line of test code is an investment in **your codebase**, it will never be coupled to us as a paid service or company. Tests will be able to run and work independently, _always_.\n\nWe believe testing needs a lot of ❤️ and we are here to build a tool, a service, and a community that everyone can learn and benefit from. We're solving the hardest pain points shared by every developer working on the web. We believe in this mission and hope that you will join us to make Cypress a lasting ecosystem that makes everyone happy.\n",
"section": "app",
"anchors": [
"our-mission"
],
"path": "/llm/json/chunked/app/get-started/why-cypress.json",
"token_estimate": 308
},
{
"id": "app/get-started/why-cypress#key-differences",
"doc_id": "app/get-started/why-cypress",
"heading": "Key Differences",
"heading_level": 2,
"content_markdown": "## Key Differences\n\n### Architecture\n\nMost testing tools (like Selenium) operate by running outside of the browser and executing remote commands across the network. _Cypress is the exact opposite._ Cypress is executed in the same run loop as your application.\n\nBehind Cypress is a Node server process. Cypress and the Node process constantly communicate, synchronize, and perform tasks on behalf of each other. Having access to both parts (front and back) gives us the ability to respond to your application's events in real time, while at the same time work outside of the browser for tasks that require a higher privilege.\n\nCypress ultimately controls the entire automation process from top to bottom, which puts it in the unique position of being able to understand everything happening in and outside of the browser. This means Cypress is capable of delivering more consistent results than any other testing tool.\n\nBecause Cypress is [installed locally](/llm/markdown/app/get-started/install-cypress.md) on your machine, it can additionally tap into the operating system for automation tasks. This makes performing tasks such as [taking screenshots, recording videos](/llm/markdown/app/guides/screenshots-and-videos.md), general [file system operations](/llm/markdown/api/commands/exec.md) and [network operations](/llm/markdown/api/commands/request.md) possible.\n\n### Native access\n\nBecause Cypress operates within your application, that means it has native access to every single object. Whether it is the `window`, the `document`, a DOM element, your application instance, a function, a timer, a service worker, or anything else - you have access to it in your Cypress tests.\n\nFor instance you can:\n\n* [Stub](/llm/markdown/api/commands/stub.md) the browser or your application's functions and force them to behave as needed in your test case.\n* Expose data stores so you can programmatically alter the state of your application directly from your test code.\n* Test edge cases like 'empty views' by forcing your server to send empty responses.\n* Test how your application responds to errors on your server by modifying response status codes to be 500.\n* Modify DOM elements directly - like forcing hidden elements to be shown.\n* Use 3rd party plugins programmatically. Instead of fussing with complex UI widgets like multi selects, autocompletes, drop downs, tree views or calendars, you can call methods directly from your test code to control them.\n* [Prevent Google Analytics from loading _before_ any of your application code executes](/llm/markdown/app/references/configuration.md#blockHosts) when testing.\n* Get synchronous notifications whenever your application transitions to a new page or when it begins to unload.\n* [Control time by moving forward or backward](/llm/markdown/api/commands/clock.md) so that timers or polls automatically fire without having to wait for the required time in your tests.\n* Add your own event listeners to respond to your application. You could update your application code to behave differently when under tests in Cypress. You can control WebSocket messages from within Cypress, conditionally load 3rd party scripts, or call functions directly on your application.\n* For [Component Tests](/llm/markdown/app/component-testing/get-started.md), Cypress is browser-based, allowing you to test not only your component's functionality but also styles and appearance. You can visually see your component in action and interact with it in the app.\n\n### Shortcuts\n\nCypress allows for browser context to be cached with [`cy.session()`](/llm/markdown/api/commands/session.md). This means as a user, you only need to perform authentication once for the entirety of your test suite, and restore the saved session between each test. That means you do not have to visit a login page, type in a username and password and wait for the page to load and/or redirect for every test you run. You can accomplish this once with [`cy.session()`](/llm/markdown/api/commands/session.md) and if needed, [`cy.origin()`](/llm/markdown/api/commands/origin.md).\n\n### Flake resistant\n\nCypress knows and understands everything that happens in your application synchronously. It is notified the moment the page loads and the moment the page unloads. Cypress even knows how fast an element is animating and will [wait for it to stop animating](/llm/markdown/app/core-concepts/interacting-with-elements.md#Animations). Additionally, it [automatically waits for elements to become visible](/llm/markdown/app/core-concepts/interacting-with-elements.md#Visibility), to [become enabled](/llm/markdown/app/core-concepts/interacting-with-elements.md#Disability), and to [stop being covered](/llm/markdown/app/core-concepts/interacting-with-elements.md#Covering). When pages begin to transition, Cypress will pause command execution until the following page is fully loaded. You can also tell Cypress to [wait](/llm/markdown/api/commands/wait.md) on specific network requests to finish.\n\n### Debuggability\n\nAbove all else Cypress is built for usability.\n\n* There are hundreds of custom error messages describing the exact reason Cypress failed your test.\n* There is a rich UI which visually shows you the command execution, assertions, network requests, spies, stubs, page loads, or URL changes.\n* The Cypress App takes snapshots of your application and enables you to time travel back to the state it was in when commands ran.\n* You can use the Developer Tools while your tests run to see every console message or network request. You can inspect elements and use debugger statements in your spec or application code - you can use all the tools you're already comfortable with. This enables you to test and develop all at the same time.\n\n### Trade offs\n\nWhile there are many new and powerful capabilities of Cypress - there are also important trade-offs that we've made in making this possible.\n\nIf you're interested in understanding more, we've written [an entire guide](/llm/markdown/app/references/trade-offs.md) on this topic.\n",
"section": "app",
"anchors": [
"key-differences"
],
"path": "/llm/json/chunked/app/get-started/why-cypress.json",
"token_estimate": 1124
},
{
"id": "app/get-started/why-cypress#architecture",
"doc_id": "app/get-started/why-cypress",
"heading": "Architecture",
"heading_level": 3,
"content_markdown": "### Architecture\n\nMost testing tools (like Selenium) operate by running outside of the browser and executing remote commands across the network. _Cypress is the exact opposite._ Cypress is executed in the same run loop as your application.\n\nBehind Cypress is a Node server process. Cypress and the Node process constantly communicate, synchronize, and perform tasks on behalf of each other. Having access to both parts (front and back) gives us the ability to respond to your application's events in real time, while at the same time work outside of the browser for tasks that require a higher privilege.\n\nCypress ultimately controls the entire automation process from top to bottom, which puts it in the unique position of being able to understand everything happening in and outside of the browser. This means Cypress is capable of delivering more consistent results than any other testing tool.\n\nBecause Cypress is [installed locally](/llm/markdown/app/get-started/install-cypress.md) on your machine, it can additionally tap into the operating system for automation tasks. This makes performing tasks such as [taking screenshots, recording videos](/llm/markdown/app/guides/screenshots-and-videos.md), general [file system operations](/llm/markdown/api/commands/exec.md) and [network operations](/llm/markdown/api/commands/request.md) possible.\n",
"section": "app",
"anchors": [
"architecture"
],
"path": "/llm/json/chunked/app/get-started/why-cypress.json",
"token_estimate": 241
},
{
"id": "app/get-started/why-cypress#native-access",
"doc_id": "app/get-started/why-cypress",
"heading": "Native access",
"heading_level": 3,
"content_markdown": "### Native access\n\nBecause Cypress operates within your application, that means it has native access to every single object. Whether it is the `window`, the `document`, a DOM element, your application instance, a function, a timer, a service worker, or anything else - you have access to it in your Cypress tests.\n\nFor instance you can:\n\n* [Stub](/llm/markdown/api/commands/stub.md) the browser or your application's functions and force them to behave as needed in your test case.\n* Expose data stores so you can programmatically alter the state of your application directly from your test code.\n* Test edge cases like 'empty views' by forcing your server to send empty responses.\n* Test how your application responds to errors on your server by modifying response status codes to be 500.\n* Modify DOM elements directly - like forcing hidden elements to be shown.\n* Use 3rd party plugins programmatically. Instead of fussing with complex UI widgets like multi selects, autocompletes, drop downs, tree views or calendars, you can call methods directly from your test code to control them.\n* [Prevent Google Analytics from loading _before_ any of your application code executes](/llm/markdown/app/references/configuration.md#blockHosts) when testing.\n* Get synchronous notifications whenever your application transitions to a new page or when it begins to unload.\n* [Control time by moving forward or backward](/llm/markdown/api/commands/clock.md) so that timers or polls automatically fire without having to wait for the required time in your tests.\n* Add your own event listeners to respond to your application. You could update your application code to behave differently when under tests in Cypress. You can control WebSocket messages from within Cypress, conditionally load 3rd party scripts, or call functions directly on your application.\n* For [Component Tests](/llm/markdown/app/component-testing/get-started.md), Cypress is browser-based, allowing you to test not only your component's functionality but also styles and appearance. You can visually see your component in action and interact with it in the app.\n",
"section": "app",
"anchors": [
"native-access"
],
"path": "/llm/json/chunked/app/get-started/why-cypress.json",
"token_estimate": 421
},
{
"id": "app/get-started/why-cypress#shortcuts",
"doc_id": "app/get-started/why-cypress",
"heading": "Shortcuts",
"heading_level": 3,
"content_markdown": "### Shortcuts\n\nCypress allows for browser context to be cached with [`cy.session()`](/llm/markdown/api/commands/session.md). This means as a user, you only need to perform authentication once for the entirety of your test suite, and restore the saved session between each test. That means you do not have to visit a login page, type in a username and password and wait for the page to load and/or redirect for every test you run. You can accomplish this once with [`cy.session()`](/llm/markdown/api/commands/session.md) and if needed, [`cy.origin()`](/llm/markdown/api/commands/origin.md).\n",
"section": "app",
"anchors": [
"shortcuts"
],
"path": "/llm/json/chunked/app/get-started/why-cypress.json",
"token_estimate": 108
},
{
"id": "app/get-started/why-cypress#flake-resistant",
"doc_id": "app/get-started/why-cypress",
"heading": "Flake resistant",
"heading_level": 3,
"content_markdown": "### Flake resistant\n\nCypress knows and understands everything that happens in your application synchronously. It is notified the moment the page loads and the moment the page unloads. Cypress even knows how fast an element is animating and will [wait for it to stop animating](/llm/markdown/app/core-concepts/interacting-with-elements.md#Animations). Additionally, it [automatically waits for elements to become visible](/llm/markdown/app/core-concepts/interacting-with-elements.md#Visibility), to [become enabled](/llm/markdown/app/core-concepts/interacting-with-elements.md#Disability), and to [stop being covered](/llm/markdown/app/core-concepts/interacting-with-elements.md#Covering). When pages begin to transition, Cypress will pause command execution until the following page is fully loaded. You can also tell Cypress to [wait](/llm/markdown/api/commands/wait.md) on specific network requests to finish.\n",
"section": "app",
"anchors": [
"flake-resistant"
],
"path": "/llm/json/chunked/app/get-started/why-cypress.json",
"token_estimate": 123
},
{
"id": "app/get-started/why-cypress#debuggability",
"doc_id": "app/get-started/why-cypress",
"heading": "Debuggability",
"heading_level": 3,
"content_markdown": "### Debuggability\n\nAbove all else Cypress is built for usability.\n\n* There are hundreds of custom error messages describing the exact reason Cypress failed your test.\n* There is a rich UI which visually shows you the command execution, assertions, network requests, spies, stubs, page loads, or URL changes.\n* The Cypress App takes snapshots of your application and enables you to time travel back to the state it was in when commands ran.\n* You can use the Developer Tools while your tests run to see every console message or network request. You can inspect elements and use debugger statements in your spec or application code - you can use all the tools you're already comfortable with. This enables you to test and develop all at the same time.\n",
"section": "app",
"anchors": [
"debuggability"
],
"path": "/llm/json/chunked/app/get-started/why-cypress.json",
"token_estimate": 173
},
{
"id": "app/get-started/why-cypress#trade-offs",
"doc_id": "app/get-started/why-cypress",
"heading": "Trade offs",
"heading_level": 3,
"content_markdown": "### Trade offs\n\nWhile there are many new and powerful capabilities of Cypress - there are also important trade-offs that we've made in making this possible.\n\nIf you're interested in understanding more, we've written [an entire guide](/llm/markdown/app/references/trade-offs.md) on this topic.\n",
"section": "app",
"anchors": [
"trade-offs"
],
"path": "/llm/json/chunked/app/get-started/why-cypress.json",
"token_estimate": 53
},
{
"id": "app/get-started/why-cypress#cypress-in-the-real-world",
"doc_id": "app/get-started/why-cypress",
"heading": "Cypress in the Real World",
"heading_level": 2,
"content_markdown": "## Cypress in the Real World\n\nCypress makes it quick and easy to start testing, and as you begin to test your app, **you'll often wonder if you're using best practices or scalable strategies**.\n\nTo guide the way, the Cypress team has created the [Real World App (RWA)](https://github.com/cypress-io/cypress-realworld-app), a full stack example application that demonstrates testing with **Cypress in practical and realistic scenarios.**\n\nThe RWA achieves full [code-coverage](/llm/markdown/app/tooling/code-coverage.md) with end-to-end tests [across multiple browsers](/llm/markdown/app/guides/cross-browser-testing.md) and [device sizes](/llm/markdown/api/commands/viewport.md), but also includes [visual regression tests](/llm/markdown/app/tooling/visual-testing.md), API tests, unit tests, and runs them all in an [efficient CI pipeline](https://cloud.cypress.io/projects/7s5okt). Use the RWA to **learn, experiment, tinker, and practice** web application testing with Cypress.\n\nThe app is bundled with everything you need, [just clone the repository](https://github.com/cypress-io/cypress-realworld-app) and start testing.\n",
"section": "app",
"anchors": [
"cypress-in-the-real-world"
],
"path": "/llm/json/chunked/app/get-started/why-cypress.json",
"token_estimate": 167
}
]
}