A phased approach to automated software testing

Most managers seem to believe that if you automate every manual test, then you reach "Zero Defects." Many failed projects are due to "biting off more than you can chew." Automation projects should be designed in phases.

Phase I: Proof of product and application under test (AUT). Can you automate it? Complete Phase I first and make sure you are ready to continue down the automation path before continuing.

Phase II: Automate deeper using a AUT functional or component approach. Use a subset of tests and when they are running correctly, build on this as a foundation.

Phase III and more: Continue automating deeper, making sure the previous phase deliverables still function. Then spread the word -- show the results and reap the benefits.

Requires Free Membership to View

This was first published in June 2007

There are Comments. Add yours.

TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.