AS we know, in the test plan, it shouod include test strategy. Normally I believe every company has his own test plan template. In the template, it may define Test Approach, Risk Assesment, Test Criteria and some Metrics.
But sometimes, What QAs' job is just filling Feature test in the template, they don't care about test strategy in the template.
Why we think little about test strategy in test plan? Below is the status:
First, I guess the majority QA just regard it as virtual thing. QA just goes through the process, and everytime when a project comes, QA will only do black box test, function test. What QA's done is falling into make feature understanding. they don't like to think more about how to improve test effectiveness and efficency.
Second, the time is very tough, QA has no much more time to think more. In this kind of case, maybe the project is very urgent or the whole project just breaks the normal process.
Third, QA has no sense about this part. Maybe the QA is fresh man, he even can't understand what test it is, how can we ask them to think more about test strategy.
To resovle the problem, I think QA team should think more serious about test strategy; We may take some measures to check the test plan, especial for test strategy. If we have little time on this, we may write in simple way, at least it should explain why we don't think more about this. If the project is tested by a fresh man, Ok, I think the QA can ask a staff QA to give some advice.
As we know, test strategy is very important for QA, it presents our core ability. Before we test, we should indeed should think:
- What end user focus?
- What are the first priority?
- Whether need we invovle third party help?
- What mothodology should we take?
- Whether need we to come out some test assistant tool?
- What risk maybe introduce?
