Product Testing Test Strategy

This depends on the industry, company, and project.  Generally my test strategy includes:

1 INTRODUCTION
1.1 Purpose
1.2 Context
1.3 Target readership
1.4 Source material and references

2 OBJECTIVE AND SCOPE
2.1 System description
2.2 Test objectives
2.3 Scope of testing
    2.3.1 Areas to be tested
    2.3.2 Areas not to be tested
2.4 Stakeholders
2.5 Stakeholder preconditions

3 TEST STRATEGY DESCRIPTION
3.1 Overall approach
3.2 Risk Analysis
    3.2.1 Test factors
    3.2.2 Other factors
    3.2.3 Contingencies
    3.2.4 Recovery
3.3 Test phases
3.4 Stakeholder/Test phase matrix
3.5 Entrance criteria
3.6 Acceptance criteria
3.7 Exit criteria

4 TEST PLANNING
4.1 Major deliverables per test phase
4.2 Roles and responsiblities
4.3 Deliverables
    4.3.1 Deliverables to test
    4.3.2 Deliverables from test
4.3 Progress monitoring and reporting
4.4 Communication
4.5 Product delivery risk analysis
4.6 Assumptions and dependencies

5 TEST ORGANIZATION

6 TEST ENVIRONMENT AND TOOLS

7 TESTING STANDARDS AND CONVENTIONS
7.1 Configuration management and change control
7.2 Metrics
7.3 Test data

It mainly depends on the industry the application is targeted at. The industry will tell you the application type. You will never find a tailor-made test strategy for each type of application. If this were an interview question, I would ask the interview if he can tell me what type of application it is and which industry it applies to.

For example, the interviewer told you it an online banking application, your test strategy will include all these testing levels:
1. Component
2. Integration
3. System
4. Acceptance

Your testing approach will include but not limited to:
- Functional
- UI
- Database testing
- Interface testing
- Security testing
- Cookie testing
- Performance
- Load
etc.

You will include testing approach in your test strategy.