Cypress logo

Cypress

Better, faster, and more reliable testing for anything that runs in a browser.
578
641
+ 1
62

What is Cypress?

Cypress is a front end automated testing application created for the modern web. Cypress is built on a new architecture and runs in the same run-loop as the application being tested. As a result Cypress provides better, faster, and more reliable testing for anything that runs in a browser. Cypress works on any front-end framework or website.
Cypress is a tool in the Javascript Testing Framework category of a tech stack.
Cypress is an open source tool with 20.4K GitHub stars and 1.2K GitHub forks. Here鈥檚 a link to Cypress's open source repository on GitHub

Who uses Cypress?

Companies
156 companies reportedly use Cypress in their tech stacks, including Revolut, CircleCI, and Intuit.

Developers
404 developers on StackShare have stated that they use Cypress.
Private Decisions at about Cypress

Here are some stack decisions, common use cases and reviews by members of with Cypress in their tech stack.

Ross Hendry
Ross Hendry
Lead Developer at KPV Lab | 6 upvotes 190.6K views
Shared insights
on
CypressCypressPercyPercy

We use Cypress because it's made browser testing simple and fast. The speed of both writing and executing the tests means that we're able to gain good coverage with minimal effort.

By building out browser tests we've been able to refactor large parts of the application and have a good degree of faith that everything is working. Next step is going to be adding Percy into the mix.

See more
Henry Eagar
Henry Eagar
Open Source Software Architect at Hal Eagar | 3 upvotes 178.8K views
Shared insights
on
CypressCypress

I use Cypress for testing apps developed with Javascript front end frameworks because it provides stable tests. A benefit is that it's fast and has great documentation, but the killer is how well it "just works" with frameworks like angular and react where in the past I've struggled webdriver due to inconsistent network latency in commands.

See more
Shared insights
on
CypressCypress

Cypress Browser Testing tool that becomes popular recently. Looking forward to exploring it

See more
Shared insights
on
CypressCypressJestJest

As we all know testing is an important part of any application. To assist with our testing we are going to use both Cypress and Jest. We feel these tools complement each other and will help us get good coverage of our code. We will use Cypress for our end to end testing as we've found it quite user friendly. Jest will be used for our unit tests because we've seen how many larger companies use it with great success.

See more
Yildiz Dila
Yildiz Dila
testmanager/automation tester at medicalservice | 5 upvotes 4.8K views

In the company I will be building test automation framework and my new company develops apps mainly using AngularJS/TypeScript. I was planning to build Protractor-Jasmine framework but a friend of mine told me about Cypress and heard that its users are very satisfied with it. I am trying to understand the capabilities of Cypress and as the final goal to differentiate these two tools. Can anyone advice me on this in a nutshell pls...

See more
Public Decisions about Cypress

Here are some stack decisions, common use cases and reviews by companies and developers who chose Cypress in their tech stack.

Kamil Kowalski
Kamil Kowalski
Engineering Manager at Fresha | 27 upvotes 472.9K views

When you think about test automation, it鈥檚 crucial to make it everyone鈥檚 responsibility (not just QA Engineers'). We started with Selenium and Java, but with our platform revolving around Ruby, Elixir and JavaScript, QA Engineers were left alone to automate tests. Cypress was the answer, as we could switch to JS and simply involve more people from day one. There's a downside too, as it meant testing on Chrome only, but that was "good enough" for us + if really needed we can always cover some specific cases in a different way.

See more
Robert Zuber
Robert Zuber
CTO at CircleCI | 17 upvotes 541K views

We are in the process of adopting Next.js as our React framework and using Storybook to help build our React components in isolation. This new part of our frontend is written in TypeScript, and we use Emotion for CSS/styling. For delivering data, we use GraphQL and Apollo. Jest, Percy, and Cypress are used for testing.

See more
Shared insights
on
CypressCypressJestJest

As we all know testing is an important part of any application. To assist with our testing we are going to use both Cypress and Jest. We feel these tools complement each other and will help us get good coverage of our code. We will use Cypress for our end to end testing as we've found it quite user friendly. Jest will be used for our unit tests because we've seen how many larger companies use it with great success.

See more
Shared insights
on
CypressCypressPercyPercy
at

When I saw the founders of Cypress introduce it in some conference I knew I found the tool we needed to start writing E2E testing. What I like about it is that it provides a comprehensive solution for the whole lifecycle of writing E2E tests for your application, from the API you need to write the tests to showing you why they fail. It's also nice that other tools/services in the testing space, like Percy, integrate with them now.

See more
Ross Hendry
Ross Hendry
Lead Developer at KPV Lab | 6 upvotes 190.6K views
Shared insights
on
CypressCypressPercyPercy

We use Cypress because it's made browser testing simple and fast. The speed of both writing and executing the tests means that we're able to gain good coverage with minimal effort.

By building out browser tests we've been able to refactor large parts of the application and have a good degree of faith that everything is working. Next step is going to be adding Percy into the mix.

See more
Yildiz Dila
Yildiz Dila
testmanager/automation tester at medicalservice | 5 upvotes 4.8K views

In the company I will be building test automation framework and my new company develops apps mainly using AngularJS/TypeScript. I was planning to build Protractor-Jasmine framework but a friend of mine told me about Cypress and heard that its users are very satisfied with it. I am trying to understand the capabilities of Cypress and as the final goal to differentiate these two tools. Can anyone advice me on this in a nutshell pls...

See more

Cypress's Features

  • Time Travel
  • Debuggability
  • Automatic Waiting
  • Spies, Stubs, and Clocks
  • Network Traffic Control
  • Consistent Results
  • Screenshots and Videos

Cypress Alternatives & Comparisons

What are some alternatives to Cypress?
Selenium
Selenium automates browsers. That's it! What you do with that power is entirely up to you. Primarily, it is for automating web applications for testing purposes, but is certainly not limited to just that. Boring web-based administration tasks can (and should!) also be automated as well.
TestCafe
It is a pure node.js end-to-end solution for testing web apps. It takes care of all the stages: starting browsers, running tests, gathering test results and generating reports.
Puppeteer
Puppeteer is a Node library which provides a high-level API to control headless Chrome over the DevTools Protocol. It can also be configured to use full (non-headless) Chrome.
WebdriverIO
WebdriverIO lets you control a browser or a mobile application with just a few lines of code. Your test code will look simple, concise and easy to read.
Jest
Jest provides you with multiple layers on top of Jasmine.
See all alternatives

Cypress's Followers
641 developers follow Cypress to keep up with related blogs and decisions.
sreekanth reddy
Mary Fekry
Nghiep Tran
Inna Curdvanovschi
Allan Freitas
Yan Naing
Hern谩n Gimenez
Danel Ramirez
Suhas G
swillyco