Test strategy document vs. an acceptance test plan

RELATED CONTENT Software Testing and Quality Assurance How to approach JUnit for unit testing Why do performance testers write new scripts so often? How to create performance testing workload models Fixing Web application performance troubleshooting problems When should regression testing occur in an automated test plan? Achieving peak performance in integration testing Expert advises on implementation of Selenium IDE for effective software testing Getting answers about OpenSTA script problems Defining core software regression tests Breaking in functionality on UI application pages Software testing and quality assurance (QA) fundamentals Just-enough application lifecycle management (ALM) Variants between software quality assurance and software testing Nine ways to evaluate automated software testing tools Manipulating Business Intelligence to solve dense data warehouse testing issues How to deal with iteration issues in Agile Five steps to fostering better software tester and QA results Software Testing: New software testing technologies bring new challenges Testing strategies for complex environments Astronaut's STPCon advice: Teamwork delivers "The Right Stuff" How to make your software tamperproof Advice from Mike Kelly How to approach JUnit for unit testing Integration testing: Is it black box or white box testing? The future of software testing An approach to integration testing Choosing code coverage tools Performance testing and experimental design How to test software with dynamic requirements Test metrics and use case coverage during testing How to learn white box testing How to determine test coverage

RELATED GLOSSARY TERMS Terms from Whatis.com − the technology online dictionary build  (SearchSoftwareQuality.com) code review  (SearchSoftwareQuality.com) conformance testing  (SearchSoftwareQuality.com) error handling  (SearchSoftwareQuality.com) garbage in, garbage out  (SearchSoftwareQuality.com) load testing  (SearchSoftwareQuality.com) NUnit  (SearchSoftwareQuality.com) quality assurance  (SearchSoftwareQuality.com) stress testing  (SearchSoftwareQuality.com) white box  (SearchSoftwareQuality.com)

RELATED RESOURCES 2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems Search Bitpipe.com for the latest white papers and business webcasts Whatis.com, the online computer dictionary

EXPERT RESPONSE FROM: Mike Kelly Pose a Question Other Software Quality Categories Meet all Software Quality Experts Become an Expert for this site

ANSWERED November 2008:
I recently saw fellow SearchSoftwareQuality.com expert Karen N. Johnson give a talk on the topic of creating a test strategy at the Pacific Northwest Software Quality Conference in Portland, Ore.

A test strategy is your way of telling the rest of the project team what you will and won't be testing and how you plan to do that testing.

During the talk she had a fantastic quote: "The great thing about a test strategy is that if you don't write one, one will write itself." Karen continued, pointing out that a test strategy is not actually written by you, but by all the assumptions people have about what they think you're going to be testing. Only later will you find that you probably would have saved yourself a lot of time and energy by writing something down up front.

That's what a test strategy is all about. It's your way of telling the rest of the project team what you will and won't be testing and how you plan to do that testing. It's a high-level communication that conveys intent. Another idea that came out of Karen's talk is that you can also view the test strategy as a testing "bill of goods" or "statement of work." It's your way of telling people what you plan to deliver.

A test plan on the other hand is more about the specifics of your testing. It's logistics, test cases/scenarios, and resources, and it contains all the dependencies and risks that you need to focus on while testing. SearchSoftwareQuality.com expert Scott Barber talks a little more about the differences in his piece on test plans, strategies, and logistics. Karen Johnson and I also wrote an article that outlines some of the differences between test strategies and test plans. As both of those references illustrate, it's the document that's used to direct and guide the testing effort.

One of the problems that you may be struggling with is that in smaller projects, the strategy and plan sometimes morph into one document. It's OK if that happens. What's important is that you get the mileage out of the document that you need. Is it helpful to you and others in understanding what you'll be doing? Does it represent your testing bill of goods? If so, it's a strategy. If the document can also be used to guide the actual testing project and deals with some of the logistics, resources, and scenarios, then perhaps it's also your plan.

I also wrote a fun article in December 2004 about a project where our team drafted the basic test strategy on a whiteboard. And Karen has an excellent article that explains more about building a software test strategy.