Unit 4.1: Test Planning & Strategy

1. Test Planning: The Blueprint

Definition: A Test Plan is a rigorous, detailed document that describes the scope, approach, resources, and schedule of intended test activities. It identifies what is being tested, how it will be tested, who will test it, and the risks involved.

Why is it Critical?

• Direction: Without a plan, testing is aimless and chaotic (Ad-hoc).
• Communication: It serves as a contract between the QA team and stakeholders (Project Manager, Client).
• Control: It allows managers to track progress against a baseline.

---

2. Components of a Test Plan (IEEE 829 Standard)

The IEEE 829 standard defines 16 sections for a Test Plan. Here are the most critical ones:

A. Test Pattern Scope (In-Scope vs Out-Of-Scope)

Defining boundaries is crucial to prevent "Scope Creep".

• In-Scope: Features we will test.
• Example: "We will test the Login, Signup, and Forgot Password modules on Chrome and Firefox."
• Out-Of-Scope: Features we will not test.
• Example: "We will not test the Payment Gateway integration (as it's a 3rd party sandbox) and we will not test on Internet Explorer."

B. Test Strategy / Approach

The "How-To" section.

• Levels: Will we do Unit Testing? Or start directly at System Testing?
• Types: Functional, Performance, Security, Usability.
• Tools:
• Automation: Selenium, Cypress.
• Bug Tracking: JIRA, Bugzilla.
• API Testing: Postman.

C. Entry & Exit Criteria (The Gates)

You need rules for starting and stopping.

1. Entry Criteria: (When can we start?)

• Code is frozen and deployed to QA env.
• Smoke Test passed (Build is stable).
• Test Data is ready.

1. Suspension Criteria: (When do we pause?)

• A "Showstopper" bug prevents logging in. Testing stops until a hotfix is deployed.

1. Exit Criteria: (When are we done?)

• 100% of Critical/High severity bugs are fixed.
• 95% of Test Cases passed.
• Client sign-off received.

D. Risk Analysis

What could go wrong?

• Project Risks: "We might lose a key tester to illness." -> Mitigation: Train a backup.
• Product Risks: "The database might crash under load." -> Mitigation: Perform Stress Testing early.

E. Schedule & Deliverables

• Schedule: "Unit Testing ends by Feb 10. System Testing begins Feb 12."
• Deliverables: Test Plan, Test Cases, Bug Reports, Test Closure Report.

---

3. Staffing & Training

• Roles: Test Manager (Strategy), Test Lead (Technical guidance), Tester (Execution).
• Training Needs: If the plan requires using "Appium" for mobile testing, but the team only knows Selenium, you must schedule a training week. This impacts the schedule.