Consider using Cypress for E2E testing
See original GitHub issueBug Report or Feature Request (mark with an x
)
- [ ] bug report -> please search issues before submitting
- [ x ] feature request
Desired functionality.
Cypress is a brand new E2E testing tool that allows devs to do so much more than protractor (CF this video).
It is now out of private beta and I’m aware that it might be a bit early to think of an integration with the CLI. But, I’m sure that opening this issue is not a bad idea so we can discuss pro/const and maybe see an integration in few (weeks ❤️?) months 😄.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:12
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Writing Your First E2E Test - Cypress Documentation
Generally speaking, the point of Cypress is to be a tool you use every day to build and test your own applications, not...
Read more >Let's Dive Into Cypress For End-to-End Testing
Cypress is an all-in-one testing framework that does not use Selenium or WebDriver. The tool uses Node.js to start a browser under special ......
Read more >How to use Cypress for end-to-end(e2e) testing - Medium
In a nutshell, Cypress is a front-end testing tool for the web. With Cypress, you can write end-to-end(E2E) tests, run them, and debug...
Read more >Great E2E testing with Cypress
Cypress is a testing tool that greatly improves your testing experience. It offers features such as: Time travel, it takes snapshots of your...
Read more >End to End testing with Cypress - Fathom
Cypress is a great tool for those who want to create useful end to end tests with very little effort. It also makes...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
+1 for Cypress support. Selenium is a pain, even with protractor to help. I think we all understand rewriting a test suite is time consuming. I think a discussion of the merits is well warranted.
Hi @maxime1992,
Thanks for the suggestion. This is interesting. However, supporting an e2e framework is hard enough already for us, adding support for another one (or switching altogether) is a lot of efforts. We won’t have the bandwidth to do it anytime soon, if ever.
This is something that might be mitigated by having extensibility in the CLI, which is planned further down the line. At which point, you could implement a plugin that changes our current e2e to use whatever you want.