Unable to E2E Automated Testing Most User Stories? You Haven’t Tried Hard Enough. Part 1
The reason is simply a lack of capability. Good news: Motivated QA engineers can learn.
The article aims to address a frequently asked question, much like the one I received earlier this morning:
Firstly, “does not make sense to automate every test scenario” is a correct but meaningless statement. There is no such thing as 100% coverage in testing, even with an unlimited budget (such as moon-landing by NASA, No, there was still a limit). So, like most of the tasks we do in life, there is always cost consideration. But for Web E2E Test automation, I can confirm that most user stories (for web apps) can be automated tested at low cost while yielding great benefits.
When developing my apps, I think this way. I cover every user story with automated UI tests (in raw Selenium WebDriver), and run them (the whole suite) as regression testing. This will detect many regression errors (which is very true). If all tests pass (in a CT server), I immediately push the new build to production.
I managed to achieve that for all my apps, for over 10 years. Yes, there were some challenging ones, but with such great benefits, E2E test automaion is the highest priority in my software development process. So, little comprimse there.With that mindset, I find the “challenging-to-automated-test secnarios” often not hard at all. Of course, I learn and grow along the way.
In Agile, you should at least cover a user story with 1+ automated E2E (via) UI test. Otherwise, it is not “Done, Done”. — Zhimin Zhan
In Agile, we must automate (E2E) every necessary user scenario for regression testing. Please note the word “user”. If an end-user can perform, why can’t we cover it with automated testing? If so, how can a software team maintain and support the app effectively? (you cannot verify the change.)