I am a Protractor user since 2014, and I think I have mastered it, having shared hands-on videos about how to use it, writing blog posts about it, maintaining an npm module that helps writing reliable e2e tests, writing “code-labs” on GitHub with tips and tricks, having written a book with a collection of practices for e2e testing of web applications, and of course, using it with success in many different projects.
When I started using Protractor, I thought their documentation was much better than Selenium, and IMO, at that time it was. But Selenium 4 is coming, and their new docs are pretty good, just to mention.
After using Protractor for some time, I noticed that many details were missing, which was one of the reasons I decided to write the book (to collect them all in a single place.)
Note: the book was published at the end of 2016, and it is undoubtedly outdated regarding what I know and how I use the tool today.
Since last Friday I have been reading Cypress’ documentation and experimenting it in different web projects, and it is working great. One of the nicest things about their documentation is that the details are not only about how to use the framework properly, but also about how to write smart e2e tests, and maybe even more important, the documentation “teaches” its readers how to not write flaky, and not well-thought tests.
If you go deeply through Cypress’ documentation, you will find ways to go around all of the mentioned cons of this post and have very well written and maintainable e2e tests. Finally, Cypress is a tool for developers and QA engineers.
Cypress, I’m in!