In our last few blog entries, we’ve explored how to develop a compelling, whiz-bang case for test automation and how to develop an SDLC for automation development. In this entry, we’d like to answer the following question: How do you determine appropriate automation selection criteria?

In his article, “Automation Selection Criteria – Picking the “Right” Candidates,” Bob Galen makes the following two assumptions:

One of the basic assumptions I’m making for this article is that you’ve been creating test cases and manually testing as an organization for a while. That is, you’ve built up some sort of repository of manual test cases that are potential automation “candidates”. Given that you can’t automate everything at once, the question of where to start and how to properly orchestrate your efforts over time becomes a challenge. Read More>>

I’m also assuming that you do not have infinite resources nor time to produce visible results. That is, you have other testing responsibilities besides the automation, for example testing and releasing your products. So prioritization and establishing a work balance becomes a challenge as well. Read More>>

Galen then explores the behavioral patterns that impede testing automation, explains the common strategies that are succesful for testing automation, and how to change your selection criteria when your circumstances change.

This article is chock-full of a lot of thought and detail that we encourage you to read for yourself. Then we invite you to come back to our blog and share your experiences with testing automation—whether you’ve gotten mired down in impediments or you’ve tried one of Bob’s strategies for success successfully or how you accomplished a change in selection criteria.

In our last blog entry, we shared with you the steps for developing a compelling case for test automation. That leaves us with the question – How do you develop an Automation Development Lifecycle? Bob Galen proposes the answer in his article, “Establishing Your Automation Development Lifecycle”.

In Galen’s own words, his purpose for writing the article is:

… to help you “connect” your automation efforts to traditional SDLC activities. While some test teams are getting better at it, I still see far too many clients that manage their automation outside of good software development practices. I’d like to see that trend change much more aggressively. Read More>>

Bob’s four key points during the article include the following:

1) Establish the major drivers for creating an Automation SDLC

2) Explore a few of the key success criteria behind a solid Automation SDLC effort

3) Review Automation SDLC extensions from your own product SDLC

4) Finally, consider how to integrate automation correctly with your mainline development efforts Read More>>

He goes into a great deal of depth on each of his key points…too much depth for an online blog. We encourage you to go and read the article and then come back to our blog ready to discuss your views on how to best develop an Automation Development Lifecycle.