Replace the company’s logo or name with the relevant details of the company. Input the project-specific information into the corresponding cells in the tables on the right.
Maintain the Version History section to document any modifications to the template; each change must be reviewed, sanctioned, and recorded in the table.
The Test Plan comprises various segments:
a. Test Plan:
i. Test Plan ID.
ii. Task ID.
iii. While adhering to ISO/IEC 29110, which suggests regression, integration, and unit tests, it can be customized to incorporate other test types.
iv. Test Status (Not started, In progress, partially passed, failed, passed).
v. Version.
vi. Estimated start date.
vii. Estimated end time.
viii. Estimated cost.
b. Required resources:
i. Necessary software resources.
ii. Essential hardware resources.
iii. Test Plan Status (not started, verified, in progress, baselined, and validated).
iv. Test Case Status Result (not started, in progress, baselined, validated, and verified).
v. Test Case Execution Result (to do, in progress, accepted with restrictions, blocked, failed, and accepted).
c. List of test cases:
i. Test Case ID.
ii. Requirement ID.
iii. Created by.
iv. Software component for testing.
v. Description.
vi. Hardware prerequisites.
vii. Software prerequisites.
viii. Expected Result.
ix. Tool.
x. Start date.
xi. End date.
xii. Status (not started, in progress, validated, not validated, verified, not verified).
d. Individual Description for each Test Case (Unitary and Regression Tests):
i. Test Case ID.
ii. Test ID.
iii. Description.
iv. Methodology.
v. Input Data.
vi. Expected Output.
vii. Test Result (Not Started, in progress, accepted with restrictions, blocked, failed, accepted).
viii. Observations.
e. Individual Description for each Test Case (Integration Tests):
i. Test Case ID.
ii. Test ID.
iii. Step ID.
iv. Procedure.
v. Input Data.
vi. Expected Output.
vii. Test Result (Not started, in progress, accepted with restrictions, blocked, failed, accepted).
viii. Observations.
f. Test Report:
i. Test Case ID.
ii. Test ID.
iii. Description of the defect.
iv. Affected functions.
v. Defect severity (1. high severity, high priority, 2. low severity, high priority, 3. high severity, low priority, 4. low severity, low priority).
vi. Date of identification.
vii. Team member who identified the defect.
viii. Date of resolution.
ix. Team member who resolved the defect.
Include a Procedures file where users can document all the procedures for each test case.