Before you automate
Do your analysis, identify your biggest risks and choose how you can mitigate those risks. This is abstract, so wh...
For further actions, you may consider blocking this person and/or reporting abuse
I really like this article. People can spend long days, weekends, and nights writing up every single test in the book. However, when a production issue hits and it was not caught by an extensive regression test people will start wondering if automation is worth it or not. When that starts to creep in then it's all downhill from there.
This is so often misunderstood. Daily I'm trying to eliminate swaths of tests to get the most out of the time testing.
When I work with others on the automation being written I ask what is this testing for and the answer is often specific to the incident and not the issue. Which prevents a generic test to catch other case.
That's been the rub. The people doing the work typically are not looking at the big picture and likely find it difficult to think that way.
I would love to know, do these incident specific tests catch regressions?
I would love to know that too.
We haven't had good review of failure analysis and have spent so much time updating these "incident" tests I don't really believe the claim that they have found bugs.
But I do have bias because I like to evaluate risk of an issue reoccurring, severity if it happens, cost to maintain the test due to routine changes of a release.
Benjamin, I can understand where you are coming from. 100% test automation is anyway more harmful than 100% manual testing. You atleast still have control over what is being tested and how it is being tested. But, I believe that one should not skip regression testing entirely. Automated regression testing can be applied to some of the more static components, and the dynamic one can be saved for manual discretion. You might like to check this out - cigniti.com/blog/alert-need-regres...
Absolutely! I have nothing against targetted automated regression. But I wanted to be clear that the goal of "Fully automated regression" can be dangerous and expensive. Automation is not trivial to "Right size". Any some automation is usually better than none.
Love the idea of using spark joy for one's tests. I have definitely seen teams not delete tests due to fear.
I've seen this as well, but in some ways I can understand a bit. Some people don't want to delete tests because they are afraid that product managers will change their minds in the last minute. However, if done right with version control, I don't think this should even be a problem.
This actually goes for all regression tests not just automated ones. :)