How Cypress Works
Testing has been broken for too long—so we decided to fix it. Cypress makes setting up, writing, running and debugging tests easy for developers.
Start testing today
Choose a framework
Mocha, Jasmine, QUnit, Karma
Choose a Selenium wrapper
Choose an assertion library
Add additional libraries
An all-in-one testing framework, assertion library, with mocking and stubbing.
Can't say enough about @Cypress_io! Makes testing modern and legacy code a snap. The GUI tools are amazing and the CLI just works.
Nick DeNardis,Sr. Dir of Digital,Wayne State University
7 ways Cypress is different
Since its introduction, Cypress has quickly become the most developer-loved automated testing framework for modern web applications.
Cypress does not use Selenium.
Most end-to-end testing tools are Selenium-based, which is why they all share the same problems. To make Cypress different, we built a new architecture from the ground up. Whereas Selenium executes remote commands through the network, Cypress runs in the same run-loop as your application.
Cypress focuses on doing end-to-end testing REALLY well.
Cypress is not a general automation framework, nor is it a unit testing framework for your back end services. There are already great tools out there that do that. Rather, we specialize in one thing - creating a great experience while you write end to end tests for your web applications.
Cypress works on any front-end framework or website.
Cypress is all in one.
Writing end-to-end tests takes a lot of different tools to work together. With Cypress you get multiple tools in one. There is no need to install 10 separate tools and libraries (ie: Mocha, Jasmine, QUnit, Karmato, Protractor, Nightwatch, Webdriver, Selenium, Chai, Expect.js, Sinon, TestDouble) to get your test suite set up. We have taken some of the best-in-class tools you are likely already familiar with and made them all work together seamlessly.
Cypress is for developers and QA engineers.
One of our goals was to make test-driven development a reality for end-to-end testing. Cypress is at its best when you use it as you build your application. We give you the power to code as fast as possible.
Cypress runs much, much faster.
These architectural improvements unlock the ability to do TDD with full end-to-end tests for the very first time. Cypress has been built so that testing and development can happen simultaneously. You can develop faster while driving the entire dev process with tests because: you can see your application; you still have access to the developer tools; and changes are reflected in real time. The end result is that you will have developed more, your code will be better, and it will be completely tested. If you use Cypress Cloud, parallelization and automated load balancing will further supercharge your test speeds.
for those wanting to understand a bit more...
The architecture is completely different.
Most testing tools 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. Behind Cypress is a Node.js server process. Cypress and the Node.js 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.
Cypress also operates at the network layer by reading and altering web traffic on the fly. This enables Cypress to not only modify everything coming in and out of the browser, but also to change code that may interfere with its ability to automate the browser.
Cypress 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.
Because Cypress is installed locally on your machine, it can additionally tap into the operating system itself for automation tasks. This makes performing tasks such as taking screenshots, recording videos, general file system operations and network operations possible.
Cypress has native access to everything.
Because 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 Cypress. There is no object serialization, there is no over-the-wire protocol - you have access to everything at your fingertips.
A whole new kind of testing is possible.
Having ultimate control over your application, the network traffic, and native access to every host object unlocks a new way of testing that has never been possible before. Instead of being ‘locked out’ of your application and not being able to easily control it - Cypress instead lets you alter any aspect of how your application works. Instead of incredibly slow and expensive tests such as creating the state required for a given situation - you can simply create these states artificially like you do in an unit test. For instance you can:
- Stub the browser or your applications functions and force them to behave as needed in your test case.
- Expose data stores (like in Redux) so you can programmatically alter the state of your application directly from your test code.
- Test edge cases like ‘empty views’ by forcing your server to send empty responses.
- Test how your application responds to errors on your server by modifying response status codes to be 500.
- Modify DOM elements directly - like forcing hidden elements to be shown.
- Use 3rd party plugins programmatically. Instead of fussing with complex UI widgets like multi selects, autocompletes, drop downs, tree views or calendars, just call methods directly from your test code to control them.
- Prevent Google Analytics from loading before any of your application code executes when testing.
- Get synchronous notifications whenever your application transitions to a new page or when it begins to unload.
- Control time by moving forward or backward so that timers or polls automatically fire without having to wait for the required time in your tests.
- 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.
You can programmatically take shortcuts.
Trying to test hard to reach areas of your application? Don’t like the side effects an action creates? Tired of repeating the same repetitive and slow actions over and over again? You can simply skip them all. Cypress prevents you from being forced to always ‘act like a user’ to generate the state of a given situation. With Cypress you can programmatically interact and control your application. You no longer have to use your UI to build up state!
That means you no longer have to visit a login page, type in a username and password and wait for the page to load and/or redirect. Cypress gives you the ability to take shortcuts and programmatically log in. With commands like cy.request(), you can send HTTP requests directly, yet have those requests synchronized with the browser. Cookies are automatically sent and applied back. Worried about CORS? Don’t be, it’s completely bypassed. The power to choose when to test like a user and when to skip slow and repetitive parts is yours.
Cypress is not flaky.
Cypress knows and understands everything that happens in your application synchronously. It’s notified the moment the page loads, the moment the page unloads. It’s impossible for Cypress to miss elements when it fires events. Cypress even knows how fast an element is animating and will wait for it to stop! Additionally, it automatically waits for elements to become visible, to become enabled, and to stop being covered. When pages begin to transition, Cypress will pause command execution until the following page is fully loaded. You can even tell Cypress to wait on specific network requests to finish.
Debuggability is first class.
Above all else Cypress has been built for usability. There are hundreds of custom error messages describing the exact reason Cypress failed your test. There is a rich UI which visually shows you the command execution, assertions, network requests, spies, stubs, page loads, or URL changes. Cypress takes snapshots of your application and enables you to time travel back to the state it was in when commands ran. You can use the Dev Tools while your tests run, you can see every console message, every network request. You can inspect elements, and you can even use debugger statements in your spec code or your application code. There is no fidelity loss - you can use all the tools you’re already comfortable with. This enables you to test and develop all at the same time. If you’re using Cypress Cloud, you have access to even more detailed insights on your tests’ performance, helping you to optimize your runs, and ship faster with more confidence.
Didn't find what you're looking for?
Check out Learn Cypress, search our docs, or browse the FAQs.
Level up your testing knowledge in our all-new program focusing on the most practical elements of testing.
Our super thorough docs show you how to use and troubleshoot Cypress, step by step.
Not finding what you need in our docs? We may have answered your question in our FAQs.
Ready to try Cypress?
Fast, easy and reliable testing for anything that runs in a browser.
Install Cypress in seconds and take the pain out of front-end testing.