Intw Questions: Test Strategy Vs Test Plan

Test Strategy

Set of guide lines which describes test design for the project
Can be either on organization level prepared by QA Manager/Director OR on project level prepared by QA Manger/Lead
Pre-requisite for this document is Business Requirement Document (BRD)
Often a static document i.e. not much changes happen in this document during the project life cycle
Contain generic information about what should be covered/used as testing. Few key points can be (Not limited to)-

Business scope & objective
QA Best Practices
Test Automation tools (Used at organization level OR Proposed for the project)
Defect Management tools (Used at organization level OR Proposed for the project)
Change & configuration management tool (Used at organization level OR Proposed for the project)
Test Deliverables
Test status communication
Test metrics reporting
Training requirements

Test Plan

Details out test methodology for a particular project release or phase
Prepared by QA Manager or QA Lead
Pre-requisite for a Test plan is Business Requirement Document (FRD) Or Software requirement specification (SRS)
Mostly a dynamic document where changes can happen during release cycle and all these changes are tracked in a different version e.g. There can be certain features which can be discovered as out of scope in the current release due to ANY reason. Such features should be scoped out from QA perspective as well in the Test plan
Can contain following information (Not limited to)

Feature/Release introduction
Features in scope
Features not is scope
Entry/Exit/Resumption Criteria
Testing in/out scope, can be a combination of functional / non- functional testing

Schedule & responsibilities
Test tools (Used in the particular release based on the consent with client or group)

Intw Questions