In this article, we learn what is test plan in software testing.
Test plan In Software Testing Life Cycle (STLC)
A test plan in software testing is a detailed document that describes software testing areas and activities.
The test plan is the base of every software test. Test plan in software testing is the most crucial activity which ensures the availability of all the lists of planned activities in an appropriate sequence.
A test Plan is a dynamic document. The success of a testing project depends upon a well-written Test Plan document that is current at all times. A test Plan is more or less like a blueprint of how the testing activity is going to take place in a project.
It is a project-level document and it’s created by a lead or senior test engineer.
The Test Plan in Software Testing Includes:
- Work allocation (What type of work)
- The scope of the project gets selected
- Based on the scope of the project, work is get allocated.
- Resources Allocation (Who will test)
- Resources mean people
- In work, allocation tests are get selected
- In resources allocation who will do the test, that’s decided.
- Estimation (Start date and End date)
- Estimation means, the start and end date of the project or module.
Given below are a few pointers on a Test Plan in Software Testing:
1) Test Plan is a document that acts as a point of reference and only based on that testing is carried out within the QA team.
2) It is also a document that we share with the Business Analysts, Project Managers, the Dev team, and the other teams. This helps to enhance the level of transparency of the QA team’s work with the external teams.
3) It is documented by the QA manager/QA lead based on the inputs from the QA team members.
4) Test Planning is typically allocated with 1/3rd of the time that takes for the entire QA engagement. The other 1/3rd is for Test Designing and the rest is for Test Execution.
5) This plan is not static and is updated on an on-demand basis.
6) The more detailed and comprehensive the plan is, the more successful will be the testing activity.
Preparation of Test Plan in Software Testing:
It consists of information about modules, features, test data, etc., which indicate the aim of the application means the application behavior, goal, etc.
2. Test Plan ID
Test plan id is created in an excel sheet. This would be a unique ID to categorize the items in the test plan.
Release Month Project Name Department Name Module To Be Developed
After the release month, project name, department name, and departmental project name the team lead selects modules like a movie: Hollywood, Bollywood, etc.
4. Feature to test/scope/out of scope
Test Scenarios and Test objectives will be validated.
Enhanced clarity on what we are not going to cover.
The feature means requirement or specification as per the customer.
Also if any feature does not needs to test then that is also mentioned in it.
Example: Feature testing on the web, not on mobile.
1. Seat Selection à Reflect seat numbers when the user makes a selection.
2. Show Time Selection à Show availability of seats at that show.
3. Payment Method Selection à Show payment option.
4. Payment Info Tab à Accept inputs from a user and confirm the validity of the card.
5. Finalized roles and responsibilities
Team members are listed.
Who is to do what?
Module owners are listed and their contact info.
Each member of the team gets his work allotment then to complete his task is his/her responsibility.
6. Test Pass/Fail Criteria
The test is consider as pass when all test scenarios get pass.
Test is consider as fail when any one of all scenario/test case is fail.
Test scenario consist of multiple test case.
We check test case one by one.
If test case if fail we mark scenario is failed.
We make status of test case in the excel sheet or in JIRA.
7. Test Environments
Test Environments means required Hardware and software to conduct a test.
What kind of environment requirements exist.
Hardware are desktop, mobile, tablet etc.
Software are Browser, OS, JIRA etc.
8. Test Deliverable
It means without completing one phase we cannot proceed to next phase.
- Without test case design-we cannot proceed for test case review.
- Without test case review-we cannot proceed for test case execution
- Without test case execution-We cannot proceed for test case summary.
- Without test case summary-we cannot proceed to test closure report.
The schedule is the start and end date of each task.
It is a kind of estimation.
Test Case Design
Test Case Execution
User Acceptance Testing (UAT)
10. Risk and mitigation
If any critical defect get then we do retesting to avoid bad defect situations then we log defect and send mail to all authorities.
11. Approval and review of test plan
Once Teat plan created by TL or Senior then that is verified or reviewed by PM.
They check as test plan meeting requirements or not from BRS or SRS or User story.
12. Defect Tracking tool
JIRA used for bug tracking.
13. Test Environment
In test plan also mentioned as like when we have to perform regression testing or sanity testing and in which server or environment testing would be carried.