![I have bad luck with Cypress](/_next/image?url=https%3A%2F%2Fassets.tina.io%2F4a740436-f084-4503-8432-4223974dac32%2Fcovers%2Fpexels-egor-kamelev-920160.jpg&w=3840&q=75)
I have bad luck with Cypress
Testing is all about being confident that your changes to the software can be deployed to production without problems. While unit or integration tests help you to test details — like the results of a calculation, or whether two parts of your system are working together — you don’t know whether all parts of your system are working together as they should. Systems are getting ever more complex and we try to cope with that by splitting it up into parts so that we can handle them or distribute the complexity over multiple teams. Teams develop and deploy small, loosely coupled Microservices that reassemble a bigger system. How do you know that everything works together and that a user can use it? This is where End-to-end (e2e) testing comes into play. And Cypress can be a nice tool for that.