TL;DR

Test plan — Guiding the testing team on what to test, how to test, and when to test. All implemented and planned testing. Plan how to execute testing (how functional testing will occur, manual or auto). Answers “how” questions. How we will do perf testing?

Scope of testing in project (what we want to test)
Test execution guides (test env, test reports)
Test scenarios, test cases, test techniques, test schedule
Exit criteria

The main objective of creating Test plan is focusing on resources and schedules:

Project scope
Roles and Responsibilities
Deadlines and deliverables

Test strategy — Answers “what” questions. What are the objectives of testing? Types of testing (functional, regression, perf). Risks. Finish line.

Testing objectives, testing levels and types, automation (kind what should be covered, defect management, documentation rules)

Test plan

Test plan — describes a list of tested components, quality criteria and risks of testing, resources to be used for testing, metrics by which results will be measured, testing strategy and testing types.

A document describing the scope, approach, resources, and schedule of intended testing activities. It identifies test items, the features to be tested, the testing tasks, who will do each task, and any risks requiring contingency planning.
The test plan is a more detailed document that provides guidance to the testing team on how to perform testing.
Test methodologies and techniques: Describes the testing approaches and methods that will be used, such as black-box testing, white-box testing, regression testing, etc.

How to write a test plan?

Analyze the product

Test methodology (agile or waterfall), depending on product select it
Who will use the website?
What is it used for?
How will it work?

Design the Test Strategy
Define the Test Objectives

Scope (which is tested and which part will not be tested)

Based on customer requirements
Project budget
Project specification
Skills and talent

Which part of software will be automated
Features to be tested, test techniques, testing tasks, features pass or fail criteria, test deliverables, responsibilities, and schedule. Planning of resources. Test environment planning
When will the test occur?
How functional, regression, perf testing will occur?

Define Test Criteria Acceptance, Metrics

Number of test cases executed, passed, failed, critical, non-critical, severity, priority, blockers
Even if the test failed, we can proceed with release if it is not a blocker, or it is not depend on the team’s work

Resource Planning
Plan Test Environment
Schedule & Estimation
Determine Test Deliverables

Test plan: ISTQB

A test plan shall have the following structure:

Test plan identifier;

To which product it belongs, number, level (master, or component), date

Introduction;

Level of the plan (master), summarize software items and its feature to be tested
Project Authorization
Project Plan
Quality Assurance Plan
Configuration Management Plan
Relevant Policies and Standards
For lower level plans, reference higher level plan(s)

Test items = the things you will test;

Requirements specification;
Design specification;
Users guide;
Operations guide;
Installation guide.

Features to be tested; (from the USERS view point)

set the risks for each feature (H, M, L)

Features not to be tested;

why this feature will not be tested

maybe will not be included to the release
low risk, has been used before
in-build solution

Approach = test strategy for the test plan; Rules and procedures

Are any special tools to be used and what are they? Will the tool require special training?
What metrics will be collected? Which level is each metric to be collected at?
How is Configuration Management to be handled?
How many different configurations will be tested

Hardware
Software
Combinations of HW, SW and other vendor packages

What are the regression test rules? How much will be done and how much at each test level.

Will regression testing be based on severity of defects detected?

How will elements in the requirements and design that do not make sense or are

untestable be processed?

If this is a master test plan the overall project testing approach and coverage

requirements must also be identified.

Specify if there are special requirements for the testing.
Only the full component will be tested.
A specified segment of grouping of features/components must be tested together.
Other information that may be useful in setting the approach are:

MTBF, Mean Time Between Failures - if this is a valid measurement for the test involved and if the data is available.
SRE, Software Reliability Engineering - if this methodology is in use and if the information is available.
How will meetings and other organizational processes be handled.
Are there any significant constraints to testing.

Resource availability
Deadlines
Are there any recommended testing techniques that should be used, if so why?

Item pass/fail criteria;
Suspension criteria and resumption requirements;
Test deliverables;
Testing tasks;
Environmental needs;
Responsibilities;
Staffing and training needs;
Schedule;
Risks and contingencies;
Approvals.

Test strategy

Test Strategy provides a higher-level overview of the testing approach and objectives, helping stakeholders understand the overall direction and goals of the testing effort.

Testing objectives: Defines the overall goals of the testing effort, such as ensuring the quality of the product, meeting customer expectations, etc.
Test levels and types: Specifies the different levels of testing (e.g., unit testing, integration testing, system testing, etc.) and the testing types (e.g., functional testing, performance testing, security testing, etc.) that will be performed.
Test automation: Outlines the strategy for test automation, identifying which tests will be automated and the tools and frameworks that will be used.
Test data management: Describes how test data will be obtained, created, and managed throughout the testing process.
Documentation formats, test processes, team reporting structure, client communication strategy.
Defect management: Describes how defects will be reported, tracked, and resolved.
Test team organization: Describes the roles and responsibilities of the testing team members.
Entry and exit criteria: Specifies the conditions under which testing activities will begin and end for each testing phase.

References

‣

Test plan by Artyom: Testing from Zero

Testing.pdf606.5KB

TestPlanTemplate.pdf126.1KB

Test plan & test strategy