Who Should Use Cypress?

Find out if Cypress is for you, see who already trusts the tool and adopts it in their workflow, and learn the vision behind it.

We saw in the introduction that Cypress is promising. But who is it for? If you are a developer or a QA engineer building web applications, then Cypress is for you.

It can be used to write end-to-end, integration, and unit tests.

The complexity of your tests will grow as you move from unit to E2E testing, but the number of tests will decrease.
The complexity of your tests will grow as you move from unit to E2E testing, but the number of tests will decrease.

If your application runs in a browser, Cypress can test it no matter the scope or functionality.


Who should not use Cypress?

Cypress is not for everyone. It is not designed for building native desktop or mobile applications. Cypress is perfect for you if you want to build web applications.

However, you can control the viewport with Cypress, which lets you test your web application in mobile view. This means you can create test cases to verify if your site is truly responsive and is working as expected. This is for mobile, tablet, and desktop.

A web application on the left and native application on the right. Note the color of the status bar and how Chrome's navigation takes up extra space.
A web application on the left and native application on the right. Note the color of the status bar and how Chrome's navigation takes up extra space.

Who uses Cypress?

Though not for everyone, Cypress is already trusted and used by large companies such as Adobe, Codepen, Shopify, and many more.

In the next two lessons, we will look into the ecosystem of Cypress and what its developer team wants to achieve in the long term.


The mission of Cypress

The mission of Cypress is to build an open-source tool that improves the productivity and happiness of developers around testing. While building the tool, they also built a helpful community that everyone can benefit from.

For the most part, developers associate stress and anxiety with managing and maintaining tests and think testing is tedious and time-consuming. We will see how Cypress tries to change things by making testing an enjoyable experience.

Their documentation is in-depth and explains not just the hows but the whys as well, which is often left out when documenting a tool. For this reason, we will refer to their official documentation throughout the course to provide additional context where appropriate.

If you would like to learn more about the future of Cypress, they have an official roadmap that outlines upcoming changes, such as new features, important bug fixes, or general improvements. You can also follow Cypress on Twitter for important updates.

From the next lesson, we will see what sets Cypress apart from other test runners. Then, we will dive into its core features.