What is Cypress? Cypress is a quality platform for testing browser-based web applications. Its documented test types include end-to-end, component, API, and accessibility testing. The free, open-source Cypress App runs tests locally; the separate Cypress Cloud service records runs and provides hosted results and analytics.
What Cypress is designed to test
Cypress is centered on web applications: the pages users open in a browser, the components rendered in those pages, and the HTTP services those applications call. It is not one single test mode. Each test type answers a different question, so a serious project may use several of them rather than choosing one for everything.
| Test type | Primary question | Scope |
|---|---|---|
| End-to-end (E2E) | Can a user complete an important journey? | The running application, with browser interactions and potentially backend and third-party integrations |
| Component | Does one UI component render and behave correctly? | A mounted component in a real browser |
| API | Do HTTP endpoints return the expected behavior? | Requests and responses at the API boundary |
| Accessibility | Does the application meet the accessibility requirements being checked? | Pages or components evaluated against accessibility expectations |
End-to-end tests are appropriate for flows such as signing in, searching, paying, or completing a form. Component tests narrow the scope to a single widget, such as a date picker or navigation menu, which makes failures easier to localize. API tests exercise endpoints without requiring every screen in the interface. Accessibility tests address a separate quality dimension and should not be treated as a substitute for manual accessibility review.
What makes Cypress different architecturally
Cypress describes its architecture as running in the same run loop as the application under test. A Node server process communicates with code running in the browser. This design gives Cypress close access to application objects and browser behavior while a test is executing.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →That architecture explains Cypress’s characteristic workflow: you can watch the browser while commands run, inspect the application state around a failure, and use the runner’s command history to see what happened. Cypress presents this as a design distinction intended to make browser testing more direct and consistent. Those are product claims about its architecture, not an independently established benchmark showing that it is universally less flaky or faster than every alternative.
End-to-end, component, API, and accessibility testing in practice
End-to-end testing
An E2E test starts from the application as a user would see it and follows a meaningful flow through multiple screens or states. It can include calls to your backend and interactions with third-party services. Because the scope is broad, an E2E failure can indicate a problem in routing, authentication, frontend code, backend behavior, data setup, or an external dependency. Keep these tests focused on high-value journeys rather than trying to encode every visual detail of every page.
Component testing
Cypress mounts a component in a real browser instead of relying on a simulated DOM. That lets the test exercise the browser’s rendering and interaction environment while keeping the setup smaller than a full application journey. Component tests are useful for states that are difficult to reach reliably through the entire product, such as loading, validation, empty, and error states.
API testing
API tests focus on HTTP endpoints. They are useful for checking status codes, response bodies, validation, authentication rules, and error handling close to the service boundary. They do not prove that a user can reach the endpoint through the interface, so teams commonly pair them with a smaller set of E2E journeys.
Accessibility testing
Accessibility testing checks the accessibility requirements your team has chosen to enforce. It can catch issues earlier in development, but automated checks cannot represent every interaction or assistive-technology experience. Treat results as actionable engineering feedback and supplement them with human review.
The Cypress App and Cypress Cloud are separate
The distinction between the two products matters when someone asks whether Cypress is free.
| Product | What it does | Cost information established here |
|---|---|---|
| Cypress App | Local application for writing and running Cypress tests | Free, open source, MIT-licensed; Cypress says it is always free to use |
| Cypress Cloud | Hosted web application for recording runs, viewing results, and team analytics | Has a free plan and paid offerings; current prices and entitlements change, so use the pricing page when budgeting |
“The Cypress App is a free, open source (MIT license) application. This is always free to use.” — Cypress official FAQ
You can therefore run Cypress locally without buying Cloud. Cloud becomes relevant when a team wants hosted run history, shared results, and analytics across CI executions. Premium offerings, including UI Coverage and Cypress Accessibility, have separate pricing. Do not assume that a Cloud plan’s current limits or features remain unchanged without checking the current pricing information.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Browser and framework support
The currently documented browser set includes Chrome-family browsers and Firefox, with WebKit support described as experimental. Experimental support should be treated as a qualification, not as parity with the established browser paths.
For component testing, Cypress documents official mounting libraries for React, Angular, Vue, and Svelte. Framework, bundler, browser, and Cypress release compatibility can move over time. Confirm the support matrix for the exact versions in your project before standardizing a setup, especially if WebKit coverage is a requirement.
How to decide which Cypress test type you need
- Start with the risk. If the risk is that a customer cannot complete a business journey, begin with an E2E test.
- Reduce the scope for UI behavior. If the risk is isolated to a reusable component, use a component test in a real browser.
- Check service contracts separately. If the risk concerns request validation or response behavior, add API tests.
- Make accessibility explicit. Add accessibility checks to the pages or components where those requirements matter.
- Combine types deliberately. A component test does not prove that routing and authentication work, and an API test does not prove that a user can operate the interface.
This approach avoids the common mistake of asking one broad E2E suite to provide every kind of assurance. The right mix depends on what must be protected, how expensive a failure is, and which parts of the system change most often.
A practical Cypress workflow
- Install the Cypress App in the project. Use the package-manager instructions and release-compatible configuration for your application rather than copying an old version-specific command.
- Choose E2E or Component testing in the App. Cypress creates the corresponding configuration and example structure for the selected mode.
- Write a small, user-meaningful spec. Keep setup deterministic and use selectors that represent stable application intent rather than fragile layout details.
- Run it interactively first. The browser runner lets you watch commands, inspect the page at the failure point, and rerun a focused spec while developing.
- Run the same suite in CI. Capture artifacts and logs that help distinguish an application failure from an environment or dependency failure.
- Decide whether Cloud adds value. Connect recording only when shared history, hosted results, or analytics justify the additional service.
Strengths and boundaries to consider
- Useful browser feedback: tests run against a real browser context, and the interactive runner exposes the sequence of commands and application state.
- Multiple scopes: E2E, component, API, and accessibility testing can be combined around the same product.
- Local-first cost: the App is free and open source, so a team can begin without a Cloud subscription.
- Cloud is optional but separate: hosted recording and analytics are not the same product as the local runner.
- Moving compatibility boundary: browser, framework, bundler, and WebKit support need periodic verification.
- Scope trade-off: broad E2E tests cover realistic journeys but usually require more environment and data coordination than focused component or API tests.
Using ScreenshotNeo alongside browser tests
Cypress verifies behavior through tests. If you also need an HTTP service that captures a page for documentation, review artifacts, or a separate visual record, ScreenshotNeo is a complementary website screenshot API and MCP server. It is not a replacement for Cypress assertions and does not turn a screenshot into a functional test.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsRank #4
ScreenshotNeo accepts a URL and can return PNG, JPEG, WebP, or PDF. Before capture, it can accept the cookie or consent banner like a visitor and remove more than 60 known consent platforms, newsletter popups, and chat widgets; each cleanup step can be disabled. Only clean shots are billed. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers identify the page verdict and whether it was billed.
For teams using AI tooling, its MCP server exposes take_screenshot, get_page_info, and capture_pdf for Claude, Cursor, and other MCP clients. Other available controls include full-page capture with lazy images loaded, CSS-selector element capture, dark mode, device presets or custom viewports, retina scale, PDF paper and margin settings, custom CSS and JavaScript, pre-capture clicks, selector or network-idle waits, request and resource blocking, headers, cookies, user agents, authorization, timezone and geolocation, transparent backgrounds, resizing, configurable-TTL caching, signed image links, asynchronous jobs with signed webhooks, bulk capture of up to 100 URLs per call, a usage API, and an OpenAPI specification. Parameter names used by other screenshot APIs also work, which can simplify migration.
Or skip the browser setup
One GET request is enough to request a capture. See the ScreenshotNeo documentation for the complete option reference.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://www.cypress.io -o shot.webpCookie banners, popups, and chat widgets can be removed before the shot. Bot checks, blank pages, and failed loads are never billed. An MCP server lets AI agents take screenshots. The Free plan includes 1,000 screenshots a month with no card, and paid plans start at $5 for 3,000. Create a free ScreenshotNeo account.
Troubleshooting common Cypress problems
The test cannot find an element
First determine whether the element was never rendered, rendered later, covered by another element, or identified by a selector that changed. Inspect the page at the failure point, verify the application state and test data, and replace layout-dependent selectors with stable attributes owned by the application.
A component will not mount
Check that the component’s framework adapter, required providers, styles, and fixture data are included in the component-test setup. A component that depends on routing, state, or context may need a focused test harness rather than a bare mount.
Best Value
A test passes locally but fails in CI
Compare browser choice, environment variables, base URL, test data, network availability, and timing assumptions. Replace arbitrary delays with conditions that represent readiness, and preserve the CI failure artifacts so the first divergent command can be identified.
Cloud results are missing
Confirm that the CI job is actually configured to record runs, that it is using the intended project identity and credentials, and that the job reaches the recording step. A locally passing test does not automatically create a Cloud record.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Keeping a Cypress setup current
As of September 29, 2026, browser support, experimental WebKit status, framework and bundler compatibility, Cypress releases, and Cloud pricing should all be rechecked against the current official pages before a long-lived project plan is approved. Treat those details as version-sensitive rather than permanent characteristics of the product.
Frequently Asked Questions
Why do Cypress support details need periodic rechecking?
The documented browser matrix, experimental WebKit status, framework and bundler compatibility, release behavior, and Cypress Cloud pricing can change. Verify the current official documentation for the versions and plan you intend to use.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
