Test Deliverables in Software Testing – Detailed Explanation

Test Deliverables are the test artifacts which are given to the stakeholders of a software project during the SDLC (Software Development Life Cycle). A software project which follows SDLC undergoes the different phases before delivering to the customer. In this process, there will be some deliverables in every phase. Some of the deliverables are provided before the testing phase commences and some are provided during the testing phase and rest after the testing phase is completed.

Don’t miss: Manual Testing Complete Tutorial

Test Deliverables, Test Artifacts

Every software application goes through different phases of SDLC and STLC. In the process of software application development, test teams prepare different documents to improve communication among the team members and other stakeholders. These documents are also known as Test Deliverables, as they are delivered to the client along with the final product of software application.

Test Deliverables Infographics:

Test Deliverables

Interview Question: What is test deliverables and list out the test deliverables you have come across in the process of STLC?
This is one of the most important QA interview questions for freshers.

Check below video to see “Test Deliverables”

In the next section, we will discuss the above mentioned important test deliverables in detail.

The following are a list of test deliverables:

The test deliverables prepared during the process of software testing are as follows

1. Test Strategy: Test Strategy is a high-level document (static document) and usually developed by a project manager. It is a document which captures the approach on how we go about testing the product and achieve the goals. It is normally derived from the Business Requirement Specification (BRS). Documents like Test Plan are prepared by keeping this document as a base. Click here for more details.

2. Test Plan: Test plan document is a document which contains the plan for all the testing activities to be done to deliver a quality product. The test Plan document is derived from the Product Description, SRS, or Use Case documents for all future activities of the project. It is usually prepared by the Test Lead or Test Manager. Click here for more details.

Difference between Test Strategy and Test Plan

3. Effort Estimation Report: In this report, usually test teams mention the efforts put in to complete the testing process by the test team.

4. Test Scenarios: Test Scenario gives the idea of what we have to test. Test Scenario is like a high-level test case.

Difference between Test Scenario and Test Case

5. Test Cases/Scripts: Test cases are the set of positive and negative executable steps of a test scenario which has a set of pre-conditions, test data, expected result, post-conditions and actual results. Click here for more details.

6. Test Data: Test data is the data that is used by the testers to run the test cases. Whilst running the test cases, testers need to enter some input data. To do so, testers prepare test data. It can be prepared manually and also by using tools.

For example, To test a basic login functionality having a user id, password fields. We need to enter some data in the user id and password fields. So we need to collect some test data.

7. Requirement Traceability Matrix (RTM): Requirements Traceability Matrix (RTM) is used to trace the requirements to the tests that are needed to verify whether the requirements are fulfilled. Requirement Traceability Matrix AKA Traceability Matrix or Cross Reference Matrix. Click here for more details.

8. Defect Report/Bug Report: The purpose of using Defect report template or Bug report template is to convey the detailed information (like environment details, steps to reproduce etc.,) about the bug to the developers. It allows developers to replicate the bug easily. Click here for more details.

9. Test Execution Report: It contains the test results and the summary of test execution activities.

10. Graphs and Metrics: Software test metrics is to monitor and control process and product. It helps to drive the project towards our planned goals without deviation. Metrics answer different questions. It’s important to decide what questions you want answers to. Click here for more details.

11. Test summary report: It contains the summary of test activities and final test results.

12. Test incident report: It contains all the incidents such as resolved or unresolved incidents which are found while testing the software.

13. Test closure report: It gives a detailed analysis of the bugs found, bugs removed and discrepancies found in the software.

14. Release Note: Release notes will be sent to the client, customer or stakeholders along with the build. It contains a list of new releases, bug fixes.

15. Installation/configuration guide: This guide helps to install or configure the components that make up the system and its hardware and software requirements.

16. User guide: This guide gives assistance to the end user on accessing the software application.

17. Test status report: It is to track the testing status. It is prepared on a periodic or weekly basis. It contains work done till date and work remains pending.

18. Weekly status report (Project manager to a client): It is similar to the Test status report but generates weekly.

Download the above mentioned Test Deliverables here.

 
Test Deliverables

Rajkumar SM is a founder of SoftwareTestingMaterial. He is a certified Software Test Engineer by profession and blogger & youtuber by choice. He has an extensive experience in the field of Software Testing. He writes here about Software Testing which includes both Manual and Automation Testing. He loves to be with his wife and cute little kid 'Freedom'.

1 thought on “Test Deliverables in Software Testing – Detailed Explanation”

  1. i would lik to get latest updates ..:) gud job

Leave a Comment

Share via
Copy link
Powered by Social Snap