Do we need ROI for Software Testing and Automation?

Posted on Posted in Exploratory Testing, Functional Testing, Software Testing, Test Automation

So what would be the ROI of reading this blog post? It’s possible that you get an idea which helps you in your test automation effort or removes myths you may have about software testing or you find that you are in software testing field because of wrong reasons and you leave this field altogether.

There are many possibilities, and all of them are difficult to quantify. In my opinion, it is hard to quantify most of the activities we perform in our field – software testing.

I have never done ROI calculations for any testing activity. My take on most of the activities I perform is straightforward and based on the MoSCoW model


Things like exploratory testing, robust test automation, Continuous Integration, NFRs, etc. are more or less MUST for projects I get involved in. We discuss and get agreement on how to implement / manage them but never on whether these should be done or not.


Things like screenshots on failure, randomization, cross-browser testing, increased coverage, testing dashboard across the project, visualization, etc. are kind of activities I tend to push if there is any bandwidth. However, I never use arguments like – if you use defect tracking system ten times in a week, it will take X min and cost you Y GBP based on your hourly rates. However, if we extract, visualize and put this data in on a dashboard, it will take two days and will save you Z GBP over a period of six months.

In my opinion, the cost is a major factor in decision making – but it should not be the only thing you have when you sell your idea. If there are no other benefits of extracting this information and putting it on a dashboard except saving Z GBP over a period of six months – maybe it’s not a good enough idea for should category – who knows if usage pattern will remain as it is for next six months or not?


If we run out of Musts and Shoulds, we can look at things like Archiving results, sessions, be reporting around exploratory testing sessions, increased coverage and depth of testing, development of tools/scripts to help us in the long run and so on..


Oh, there are plenty of things in this category, and I do not need ROI calculations to find that they are wasteful 🙂

My decision making (MoSCoW model in mind) is pretty simple. It is based on either my gut feeling (or a pattern I might have seen in past) or it relies on the opinion of someone I respect (who have demonstrated their expertise in the current project) or the team decides it after weighing available options.

I have never performed any ROI calculations to prove the need for testing, automation, CI, build pipeline etc. I have often used discussions & reasons to convince whenever needed.

I have mostly worked in an environment where ROI was never requested/needed – but what about service industry or outsourcing. Do they use ROI a lot, is it justified? What do you think about it? Have you done any ROI calculations to demonstrate the need for testing, automation or something else? Did you find it useful? Please leave your comments, and we can discuss.

Please follow and like us: