what is the difference between test strategy and test plan?
Answer Posted / shwetketu rastogi
"Test strategy is an important yet little-described aspect
of test methodology. Let me introduce three definitions:
Test Plan: the set of ideas that guide a test project
Test Strategy: the set of ideas that guide test design
Test Logistics: the set of ideas that guide the application
of resources to fulfill a test strategy
I find these ideas to be a useful jumping-off point. Here
are some implications: •The test plan is the sum of test
strategy and test logistics.
•The test plan document does not necessarily contain a test
plan. This is because many test plan documents are created
by people who are following templates without understanding
them, or writing things to please their bosses, without
knowing how to fulfill their promises, or simply because it
once was a genuine test plan but now is obsolete.
•Conversely, a genuine test plan is not necessarily
documented. This is because new ideas may occur to you each
day that change how you test.
Is This Answer Correct ? | 0 Yes | 1 No |
Post New Answer View All Answers
Explain Operational Acceptance Testing with example ?
In Manual testing how to test proxy servers? can u please explain with example?
Hi, i am looking job in perfomance testing using Loadrunner can any body help me a project in any domine plz(Usah) chs_29@rediffmail.com
Can you explain the workbench concept?
What are the Major Functionality for a ATM machine ??
How to find that tools work well with your existing system?
What are the main key components in web applications?
What is ecp (equivalence class partition)?
Hi, I am planing to give ISTQB - Foundation level exam. Can anyone forward the ISTQB materials at laxmi_002@rediffmail.com mail ID.
What criteria would you use to select Web transactions for load testing?
Please Tell me About Fish-Bone Model. Thanks in Adv.
hi what are the test cases for web application..i need these example..please..mail me at mina_ims@yahoo.com
Can any one suggest how to write the bug reports effectively by optimizing what we want to describe?
If automating - what is your process for determining what to automate and in what order
what the purpose of requirement phase