Software Test Documentation Templates

Software Test Documentation Templates, Software Test Plan Document, Software Test Case, Test Data Software Defect Report, and Software Test Summary Report.

Documentation is an important activity in Software Testing, before, during, and after Testing we create and use several documents.

Software Test Documentation Templates

We create & use test documents before, during, and after Software Testing.

I. Test Policy
II. Test Strategy (Company Level Document)
III. Business Requirements Specification
IV. Software Requirements Specification
V. System Test Plan
VI. Requirements Traceability Matrix
VII. Test Scenario
VIII. Test Case
IX. Test Data
X. Test Metrics
XI. Defect Report
XII. Test Summary Report

I. Test Policy (Company Level Document)

A high-level (company level) document describes the principles, approach, and major objectives of the organization regarding Testing.

Test Policy Template

1) Test Definition
(Verification & Validation)

2) Testing Process
(Proper planning before starts testing)

3) Testing Standards

4) Testing Measurements
(QAM, TTM, PCM)

5) Risks

6) Approvals

7) Comments

8) Revision History


II. Test Strategy (Company Level Document)

A high-level document of the Test Levels to be performed and the Testing within those levels for an Organization.

Test Strategy Template

Table of Contents
1.0    Introduction
2.0    Objective
3.0    Scope of the Document
4.0    Test Approach
4.1              Introduction
4.2              Functional and Usability Issues
5.0        Phases of Testing
5.1              Documentation Review
5.2              Unit /Module and Integration Testing
5.3              System Testing
5.4              Pre – Production Testing
5.5              Responsibilities
6.0      Test Management
6.1              Test Procedures
6.2              Test Report
6.3              Test Phase Acceptance
6.4              Timescales
7.0       Risks and Assumptions
7.1               Risks
7.2               Issues
7.3               Assumptions
7.4               Related Documents
8.0      Revision History

A Sample Test Strategy Document


III. Business Requirements Specification

Table of Contents
1.0    Introduction
1.1    Purpose
1.2    Scope
1.3    Background
1.4    Assumptions
1.5    Constraints
1.6    Dependencies
1.7    Users of the product
2.0    Functional Requirements
3.0    Usability Requirements
3.1    Help
3.2    Navigation
3.3    Feedback
3.4    Look and Feel
4.0    Performance Requirements
4.1    Capacity
4.2    Availability
4.3    Latency
5.0    Security Requirements
5.1    Protection
5.2    Authorization and Authentication

6.0    Revision History

A Sample BRS Document


IV. Software Requirements Specification

Table of Contents
1.0    Introduction
1.1    Purpose
1.2    Scope of the project
1.3    References
2.0    System Requirements Specification
3.0    Functional Requirements Specification
3.1    Use Cases
3.2    Functional Requirements – Online Catalog
3.3    Functional Requirements – Administration
4.0    Non Functional Requirements
4.1    Usability Requirements
4.2    Performance Requirements
4.3    Compatibility Requirements
4.3.1    Operating Systems
4.3.2    Browsers
4.4    Security Requirements

5.0    Revision History

A Sample SRS Document


V. System Test Plan

A document describing the scope, approach, resources, and schedule of intended activities.

Test Plan Template

1) Test Plan ID:
Some type of unique company-generated number to identify this test plan.

2) Introduction:
Describe the purpose of the Plan, possibly identifying the level of the plan (System Test Plan etc.). This is essentially the executive summary part of the plan.

3) Test Items:
These are things you intend to test within the scope of this test plan.

4) References:
List all documents that support this test plan. Refer to the actual version/release number of the document as stored in the configuration management system.

5) Features to be Tested:
This is a listing of what is to be tested from the Users viewpoint of what the system does. This is not a technical description of the software, but a Users view of the functions.

6) Features not to be tested:
This is a listing of what is NOT to be tested from both the Users viewpoint of what the system does and a configuration management/version control view. This is not a technical description of the software, but a Users view of the functions.

7) Test Approach:
This is your overall test strategy for this test plan; it should be appropriate to the level of the plan (master, acceptance, etc.) and should be in agreement with all higher and lower levels of plans. Overall rules and processes should be identified.

8) Entry Criteria:
It describes when to start Testing

9) Exit Criteria:
It describes when to stop testing

10) Suspension Criteria:
It describes when to stop testing temporarily.

11) Roles & Responsibilities
Team Lead or Test Lead and Team member’s Roles and Responsibilities.

12) Schedule:
Schedule for all Test activities in this Software Test Process.

13) Training:
Training on the application/system (Domain Training)

Training for any test tools to be used.

14) Test Environment / Lab:
It describes Require Hardware and software for setting up Test Environment or Test Lab.

15) Test Deliverables:
Lists out that what is to be delivered as part of this plan?

16) Approvals
Who can approve the process as complete and allow the project to proceed to the next level.

17) Glossary:
Define terms and acronyms used in the document, it can be used to understand the terms used in this plan.

A Sample Test Plan Document

Software Test Documentation Templates

VI. Requirements Traceability Matrix

This is the document that connects the requirements to the test cases. The connection or mapping of the requirements to test cases is many to many. This means that one requirement is tested by one or more test cases. Conversely, it is possible to have one test case addressing one or more requirements.

Requirements Traceability Matrix Template

1) Serial No
2) Type of Requirement
3) Requirement Source
4) Requirement ID
5) Requirement Description
6) Test Case ID
7) Test Case Description
8) Test Log
9) Defect ID
10) Defect Description
11) Requirement Status
12) Software Version
13) Comments


VII. Test Scenario

An item or event of a component or system that could be verified by one or more Test cases.

Test Scenario Template

1) Scenario ID

2) Scenario Description

3) Module Name/ID

4) Version Control

5) Requirement/s Reference

6) Comments


VIII. Test Case

A set of input values, execution preconditions, expected result, and execution postconditions developed for a particular objective or Test condition.

Test Case Template

1) Test Case Id: a Unique name/number (Alphanumeric)

2) Test Case Name: Name of Test Case

3) Test Suite ID: Unique name/number (Alfa-numeric)

4) Pre-Condition: Status before Test Case Execution

5) Steps: Steps for Executing the Test Case

6) Post-Condition: Status After Test Case Execution

7) Expected Result: Expected Result as per Requirements

8) Actual Results: <After Test Case Execution>

9) Test Results: <After Test Case Execution and After Comparison of Expected with Actual Results> Pass / Fail

10) Remarks: Comments (Optional)

——————————————————–
Note 1: You prepare this Test Case Template in Excel Sheet

Note 2: Test Case Template may vary from one company to another and one project to another.

Note 3: In the above template Actual Results and Test Results fields can be filled in the Test Execution phase, Remaining fields in Test Design phase.

A Sample Test Case Document


IX. Test Data

Data that exits before a test is executed and that effects or is effected by the component or System under test.


X. Test Metrics

A Sample Test MetricsDocument


XI. Defect Report

A document reporting of any flaw in a component or system that can cause the component or system to fail to perform its required function.

Defect Report Template

1) Defect Id: any unique name for Identifying the Defect (Alphanumeric)

2) Defect Description: Details about the Defect

3) Test Case Id: Corresponding Test Case Id for tracking

4) Tester: Tester’s name (who found the Defect)

5) Product Version: Version of the Product on which defect was found

6) Build Version: Version of the Build on which defect was found

7) Priority: Importance of the Defect based on Business /Customer

8) Severity: Importance of the Defect based on Functionality

9) Status: Status of Defect

10) Reproducible or not: Yes / No

If Reproducible:

Steps:

If not Reproducible:

Attachments

11) Reporting to: Corresponding Developer

12) Remarks : Comments (Optional)

A Sample Defect Report Document


XII. Test Summary Report

A document summarizing testing activities and Results. It also contains an evaluation of the corresponding test items against exit criteria.

Test Summary Report Template

1) Introduction:

2) Test Items:

3) Reference documents

4) Target Audience

5) Test Summary

5.1) Test Suite Information:

•    Number of test suites planned.

•    Number and percentage of test suites implemented.

•    Number and percentage of test suites executed.

5.2) Test Case Information:

•    Number of test cases planned.

•    Number and percentage of test cases implemented.

•    Number and percentage of test cases executed.

•    Number and percentage of test cases passed.

•    Number and percentage of test cases failed (total and by severity).

5.3) Defect Report Information

Number of defects found in comprehensive Testing

Number of Test Cases selected for Regression Testing Cycle1

Number of defects found in Regression Testing Cycle1

Number of Test Cases selected for Regression Testing Cycle 2

Number of defects found in Regression Testing Cycle 2

Number of Test Cases selected for Regression Testing Cycle 3

Number of defects found in Regression Testing Cycle 3

.

.

.

A number of Test Cases were selected for Final Regression.

A number of opened defects in this release.

6) Approvals

A Sample Test Summary Document

Software Test Documentation Templates


Software Testing Documentation 

Related Documents:

1) Software Test Plan
2) Software Test Case
3) Defect Report
4) Test Summary Report
5. Software Test Metrics
6. Software Quality Standards
Sample Business Requirements Specification
A Sample SRS Document
Follow me on social media: