Automated Software Testing Gears

Several of our recent blogs have focused on making the business case for Automated Software Testing. We have described a process by which companies and development teams can evaluate the costs and benefits of a transition from manual testing to automation. Today’s blog will outline where we have been, address other considerations, and wrap up our focus on the business case.

To summarize, the main purposes of a business case are to:

  • Identify the business need—which will provide the reasoning for launching an Automated Software Testing initiative
  • Justify the business need in terms of costs and benefits, including a careful calculation of the ROI
  • Evaluate the expected risks of implementing Automated Software Testing

These areas are covered fully in previous blogs and also in the book Implementing Automated Software Testing (details below).

As you weigh a transition to Automated Software Testing, you may have some additional pressing questions or issues about your program, including:

  • How will your test team keep up with the ever increasing complexity of new technologies?
  • How will you continue to support and meet the expectations of the development team?
  • How quickly can you produce detailed artifacts that demonstrate a thorough testing effort?
  • How well-equipped are you to run the following tests: memory leak detection, stress testing performance testing and concurrency testing?
  • How do you capture and reuse the knowledge of the subject matter experts that your testing effort depends on?
  • Can you justify having testers work nights and overtime when an automated tool can be set a test in motion at days end and provide results first thing in the morning?

These and other questions may be answered by automation and should be included in your evaluation of a transition to a new method or tool for your software testing effort.

The market demands that software products continue to be delivered faster, cheaper and with increasing reliability. Testing is a significant portion of the time, cost, and quality equation. Automated Software Testing can play a big part in addressing these needs.

At Innovative Defense Technologies (IDT), our experience shows that it is important to procure buy-in from all the stakeholders for a new software testing effort. To do so, a solid business case needs to be established and approved. Broad internal support is an important factor in speeding the adoption of and transition to successful automation. Once committed to this new direction, an experienced software testing partner like IDT can also help. The results will speak for themselves.

Some information taken 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. This book was authored by three current IDT employees and is a comprehensive resource on AST.  Blog content may also reflect interviews with the authors.