Test Plan Vs Test Strategy

Sl.No

Test Plan

Test Strategy

1

The set of ideas that guide or represent the intended test process

The way tests will be designed and executed to support an effective quality assessment

2

Test Plan are of different types:

  1. Unit
  2. Integration
  3. System
  4. UAT

 

Test strategy should

 

A. focuses most effort on areas of potential technical risk, while still putting some effort into low risk areas just in case the risk analysis is wrong.

 

B. address test platform configuration, how the product will be operated, how the product will be observed, and how observations will be used to evaluate the product

 

C. is diversified in terms of test techniques and perspectives. Methods of evaluating test coverage should take into account multiple dimensions of coverage, including structural, functional, data, platform, operations, and requirements.

 

D. Specify how test data will be designed and generated.

3

Test plan is the sub set of Test Strategy.

Different test techniques ( Ad hoc, Exploratory, Specification based, code based, Fault Injection and etc) and test methods (Black, White and Incremental) is used while designing test cases and execution

9 thoughts on “Test Plan Vs Test Strategy”

  1. ———————–
    3 Principal Test Documents
    ———————–
    1. Test Policy (Organisation Level)

    – Very High Level Document
    – What “Testing” means for organisation
    – How organisation measures test success
    – Relatively static document (Changes when organisation’s focus changes)
    – Developed by IT department

    2. Test Strategy (Programme Level)

    – Applicable for a Programme/System which covers multiple projects
    – Objective/Scope of Testing
    – Inscope/Out of scope Items for testing
    – Test Levels (Unit/Module/System/Integration)
    – Test Types ( Functional/Non-Functional)
    – Entry/Exit/Stop/Resumption Criteria for testing (for different Levels/Phases)
    – Risks to be addressed
    – Test Environment
    – Test case design methodology (Specification driven/BVA/EQ Parttition)
    – Test methodology ( Top-down/bottom-up/risk based)
    – Test Automation Approach
    – Test Tools to be used
    – Defect Management approach
    – Defect classification
    – Retesting & regression approach

    3. Test Plan (Project Level)

    – All above points specific for this project
    – Test Estimation & Test schedule
    – Test Organisation/roles/responsibilities
    – Test deliverables
    – Test reporting

  2. Who will write the test strategy? I read that the project manager writes the test strategy and team lead writes test plan. Then how test strategy comes under test plan. Please clear this doubt.

  3. I desire to bookmark this specific posting, “Test Plan Vs Test Strategy | Qastation” http:
    //edmonton-industrial.com on my blog. Will you mind in case Ido it?
    Regards -Perry

  4. Thank you, I have recently been searching for information approximately this topic for ages and yours is the best I’ve found out so far. But, what concerning the conclusion? Are you sure about the source?

  5. Hello just wanted to give you a quick heads up.
    The words in your post seem to be running off the screen in Ie.
    I’m not sure if this is a format issue or something to do with browser compatibility but I thought I’d post to let you know.
    The design look great though! Hope you get
    the issue resolved soon. Many thanks

  6. Hello there! Do you use Twitter? I’d like to follow you if that would be ok. I’m undoubtedly enjoying your blog and look forward to
    new posts.

  7. I love your blog.. very nice colors & theme. Did
    you make this website yourself or did you hire someone to do it for you?
    Plz reply as I’m looking to create my own blog and would like to know where u got this from. appreciate it

Leave a reply to tinyurl.com Cancel reply