This content originally appeared on DEV Community and was authored by Swimm 🤿
End-to-end testing. The holy grail of all testing types.
Here's everything we learned regarding the ins and outs of end-to-end testing - lessons, takeaways, mistakes, you name it.
So, let's start out with why
Swimm started growing, we added new features, and we found that we simply couldn't keep up with changes.
We realized that our goal for a testing solution had two parts:
- Find a solution that allowed us to catch regressions bugs DURING development
- Save manual regression QA time
E2E testing seemed to be the right answer to our testing paradigm.
We ended up choosing Cypress
Pros
Awesome community
Great documentation
Great features: automatic waiting, automatic sreenshots & videos, time travel
Cypress is intuitive & easy to set up
Writing tests is fun
Using Cypress' API applies for user behavior
Cons
Lack of multi-tab support
Difficulty with iFrames
Limited browser support (just Chrome-based browsers & firefox)
Challenges of E2E testing
Wins:
Identified & fixed a lot of bugs
Saved so much time by not having to repeat manual flows weekly
Dramatically increased stability & coverage
ChallengesHuman vs machine testing
We had zero experience with e2e tests
Monitoring tests that are less reliable
It takes more time than you think
Key takeaways
- Appoint an owner for E2E testing
- Patience, patience, patience
- Write stable tests
- Trust. Your. Tests.
- Stable tests = stable product
Here's a detailed blog on how we implemented E2E testing.
This content originally appeared on DEV Community and was authored by Swimm 🤿
Swimm 🤿 | Sciencx (2022-01-23T11:42:53+00:00) E2E testing: challenges & lessons learned. Retrieved from https://www.scien.cx/2022/01/23/e2e-testing-challenges-lessons-learned/
Please log in to upload a file.
There are no updates yet.
Click the Upload button above to add an update.