Software Test Plan
Quality,  Software Testing

Software Test Plan

Software Test Plan

Software Test Plan is a strategic document in which it has explained that how the testing will be conduct on the particular software project. It is very necessary to know about this plan because it gives the clear idea of about every phase of testing.

Objectives and Scope:

This document provides a high level view of the type of test that is scheduled to be carried out and the features that will and will not be tested.

The objective of this document is to test the functionality of the XXXX Application.

Features to be tested:

The features which are to be tested are:

  1. Admin
  2. Merchant
  3. Delivery system
  4. Biker
  5. Customer

Features not to be tested:

  1. Third party Payment Functionality
  2. Third party API.


Agile model with scrum

Reference Documents:

SRS, Updated documents, Reviews from the client

Test Strategy:

  1. Read all the reference documents such as SRS, Reviews, Enhancements etc.
  2. Design Test Scenarios and Test Cases.
  3. Then we will conduct Manual Testing of AUT.
  4. Conduct undocumented Exploratory Testing on AUT.
  5. Recognize the Test Cases and Test Scenarios which need to be Automate.
  6. Design Test scripts for the Automation by using Selenium Tool.
  7. Create Test Data.
  8. Report the bugs to the Developer.
  9. Conduct BLC.
  10. Bug summary Report.

Expected Time Limit:

Expected Time Limit need to give according to the Features, Requirements, Enhancements, Reviews & BLC.


There is only one Senior Software Tester needed.

Risk and Contingencies:

Risk: 1. Requirements not clear.

Contingency: Need to clear all the confused requirements with the Project Manager or the client.

Risk: 2. Requirements keep changing.

Contingency: Need to discuss about the requirements with the Project Manager or the client.

Risk: 3. Functionalities intersects each other due to different requirements.

Contingency: Need to discuss about the requirements with the Project Manager or the client.

Risk: 4. Maintain the good relation with the developers & designers while achieving desired quality.

Contingency: Have patience to deal with the developers & designers and motivate them to do the better work.

Risk: 5. Shortage of software Tester.

Contingencies: Maintain buffer stock of Testers and share some part of the Project knowledge to them.

Peer Reviews:

Peer reviews are important to get the views of different persons. So make a group of Testers who are related with the same project.

Try to use the experience of Senior Testers if available.


  1. Manual
  2. Selenium IDE, Webdriver
  3. Sikuli
  4. Browser Stack for GUI and Responsive (if Applicable)
  5. Havij for Security Testing


IIS 7.0, Windows 7, 10, Mac latest version, Android 4 and above, iOS 8 and above. Latest browsers (IE, Chrome, Firefox, Safari, Opera) etc.

Test Design:

Write Test Cases for the different functionalities according to the requirement and AUT.

Test Execution:

Execute the Test Cases which are documented and also which are undocumented. Also UAT test cases as per the review of the client.


Report the Bugs to the developer who is related from the project. Tester should use Google Sheets or some tools like bugzilla. Then Enjoy the BLC phase.

Client Reviews:

Read all the client’s reviews carefully and separate true bugs and enhancements.

Bug Summary:

After completion of the project, Bug summary will be released.


Please click here to Learn Software Testing



Leave a Reply

Your email address will not be published. Required fields are marked *