A fully successful execution of Automated Software Testing is preceded by gathering all of the stakeholders and spending time on the front end to make the business case for its value. A solid business case has a three-pronged focus:

  • Identify the business need—Articulate the reasons for initiating Automated Software Testing. For example, your company may be missing deadlines due to the time delays associated with manual software testing. Or perhaps your costs are too high due to the labor involved in traditional testing.
  • Justify the business need in terms of costs and benefits—Calculate the ROI. For example, if you invest the time up front to automate certain testing procedures, how quickly will you break even and begin reaping the benefits of automation? An experienced partner like IDT can help you with these calculations.
  • Include the expected risks—A thorough analysis will weigh potential risks in making procedural changes in your software development and testing. It is much better to consider these possibilities on the front end.

 In our experience, large-scale Automated Software Testing projects are much more successful when the team has thought through the specific reasons for implementing Automated Software Testing, is able to describe its costs and benefits, and has taken into account what is needed to be successful in terms of time, skills, and processes.  On the other hand, when the tool is purchased without real analysis or training, it is less effective because it isn’t completely utilized. When introducing Automated Software Testing to your team, we highly encourage the discipline of developing the business case for its use. Read additional IDT blogs about making the business case for AST.

Adapted from: Dustin, Elfriede, Thom Garrett, and Bernie Gauf. “Implementing Automated Software Testing: How to save Time and Lower Costs While Raising Quality”. Upper Saddle River, NJ: Addison-Wesley, 2009. 51-53.