Is end-to-end testing a painful topic for you? In this article, Ramona Schwering explains how to handle end-to-end testing with Cypress and make it make it not so tedious and expensive for yourself, but fun instead.
Hi, I'm Ramona Schwering!
Software Developer @shopware. International Speaker. Cypress Ambassador. OpenSource Lover ❤️
After my education as an application developer, I contributed to product development at shopware AG for about six years now: First in quality assurance and now, as Software Developer. I own both views of the product - that of a tester and that of a developer: I use this primarily to strengthen trust in test automation and to support the testers. The automation in the end-to-end area of shopware originates from my pen, and I continue to push it firmly.
Sometimes, our pipelines fail. If that happens on our own merge requests, we need to fix it - I can imagine you feel the same if you're working with Shopware's tests. These are my notes on common test automation traps in the context of working with Shopware.
When writing front-end tests, you’ll find a lot of pitfalls along the way. In sum, they can lead to lousy maintainability, slow execution time, and — in the worst case — tests you cannot trust. But it doesn’t have to be that way.