What's the worst part about E2E Testing for you?
Heya,
I'm doing some research on what the worst things about E2E Testing are, and I wanted to ask you guys for your opinion!
For me, it is definitely writing them (Takes a lot of time), and, even more so, maintaining these tests (Since, well, almost every change in the UI breaks these tests).
What is it for you? How did you tackle some of these problems?
Time. In daily work, there is often a lack of awareness that tests are helpful in the end. As a result, they tend to fall behind, especially when there is time pressure.
When I think of E2E testing I think of Selenium and Cypress. I've worked at companies that have used both, the most annoying thing about both was the flakiness and the slow execution.
I write a ton of tests for my API, but ZERO for my front end.
I'm with you on this one. E2E tests are the most expensive and slow to run by far and provide minimal value. Because they're slow, it's generally not feasible for them to provide much coverage. We use them, but generally avoid them where possible.
Probably the flakiness and the time overhead to build and maintain them. Front end E2E tests maintenance is the worst usually. I would only do it for mature and critical UI features when I work on my projects.
I recently learned that you can run Postman tests from a CI using their non package.
https://learning.postman.com/docs/running-collections/using-newman-cli/installing-running-newman/
I'm glad you asked!
The worst thing for me when new functionality was added to the app and I didn't create new tests to cover it.
I tackled the problem by inventing Headlamp. Now I know if I've missed any part of the app when I test.