In this blog post, I will cover why I went from using Protractor to start using Cypress for end-to-end testing. We will look at the flaws in Protractor and how Cypress is fixing them as well as looking into the 7 steps to Cypress e2e testing success. Let’s get started! If you have been working …
Why I Moved from Protractor to Cypress and the 7 Steps to Cypress E2E Testing Success Read More »
It seems that a lot of developer teams fall in one of these two categories for end-to-end testing: Have no end-to-end tests because they are too hard to create Have too many end-to-end tests, making many fulltime jobs to maintain Either one of these is not practical as the first one is causing the team …
End-To-End Testing with Protractor: A Pragmatic Guide to Get Started in Your Team Read More »
The last couple of months I have been working a lot with DevOps and automation along with Angular development. One of the core principles in Continuous Delivery is having your back covered with automatic testing. Without this automatization in place, you are forced to manually regression test the whole app before every release, which will not …
A central part of testing Angular apps is to be able to automate the end-to-end testing so you don’t manually have to click through the app every time. This sounds reasonable in theory but often end-to-end tests can be fragile and expensive to maintain. When end-to-end tests become flaky they start to become useless: This post covers some …
Life Saving Protractor Utilities to fix flaky end-to-end tests Read More »
When doing practices like continuous delivery and continuous integration, testing becomes a more important part of the work because it’s unreasonable to regression test all possible effects of a release manually. When doing five releases on a workday, you don’t get to do a full manual regression testing on every release as that would easily …
The Complete Guide to Angular Testing and a Weird Trick for Faster Unit Tests (2020) Read More »