1) Requirement Analysis:- [Coming Soon…!]
2) Test Planning
The software test plan is a strategic document that describes how to perform one task effectively and efficiently.
The test plan document contains the below sections.
→ Scope of Testing
2) Reference Document
3) Test Items
⇒ Featured to be tested
⇒ Feature not to be tested
4) Test Strategy
⇒ Testing Types
⇒ Functional Testing
5) Test Environment
6) Defect Analysis & Closer
7) Items Pass / Fail Criteria / Test Summary
8) Automation Testing
9) Test Deliverables
10) Risk & Contingencies
11) Hardware & Software Requirement’s
12) Resource Plan
It describes the purpose of the test plan.
⇒ Scope of Testing:-
It describes what kind of testing like Manual testing, Automation testing, Performance testing, Etc… is responsible for the testing team.
2) Reference Document:-
The list of documents that are used to prepare the test plan will be described in this section.
3) Test Items:-
It contains two 2 sections like
⇒ Feature to be tested:
The list of testing & main activities for which the testing team is responsible will be described here.
Ex: Manual Testing, Automation testing’s are part of the test plan (Project/Product Plan)
⇒ Feature not to be tested:
The testing where the team is not responsible and not delivery to be here.
Ex: Security testing, Performance is not part of the project delivery.
4) Test Strategy:-
Strategy means how you are going to perform the task.
Test strategy means what kind of testing we are performing on the application will be described here.
⇒ Testing Types:
The testing team is responsible to perform the below functional testing like Regression, Ad-hoc testing, Usability testing, Regression testing, Retesting.
⇒ Functional Testing:
5) Testing Environment:-
The environment which we are going to use to deploy the build & to perform the testing will be described here.
Machin Type : Windows Server Enterprise
OS : Windows
Processor : Intel Xeon CPU
Ram/Memory : 8GB / 2.13 GHZ
Hard Disk : 1TB
Database : Microsoft SQL Server 2008 standard Edition
Client Browser: IE, GC, Firefox….
6) Defect Analysis & Closer:-
The list of defects that are available at the time of delivery of the project will be analyzed properly if these defects are not affecting the application then they will close it.
If it is really affecting the application, then the developer will fix it.
7) Test Summary:-
It describes the entire testing summary of the project as below
1) Total bills received by the tester
2) The list of bills accepted and rejected
3) The number of bugs identified by the testing team
4) No of bugs fixed by Dev Team, Etc…
8) Automation Testing:-
The tool & the Strategy which we are going to use for the automation testing will be described here.
9) Test Deliverables:-
The list of modules which we are going to deliver to the client will be described here.
10) Risk & Contingencies:-
The list of risks and the solutions will be described here.
Personal shortfall (ill, Marriage Leave)
Maintain buffer resources
Continues requirement changes
Lack of peer reviews
Monitor peer reviews
11) H/W & S/W Requirements:-
The list of machines like laptops, Mobiles, Machines with the related s/w which are required to deliver the project will be described here.
12) Resource plan:-
The list of resources that are required to deliver the project will be described here.
Manual Test Engineer: 8
Automation Engineer: 5
Performance Engineer: 2
[The Lead/Project manager will be going to prepare the test plan documents]