Test Plan Documentation, Test Plan vs. Test Strategy Prerequisites for Test Planning, Test Plan Template, and Test Team Job Responsibilities.
System Test Plan Documentation
I) Test Planning Phase
Input or References:
Requirement Specifications
Project Plan Document
Test Strategy Document
Global design document
Low-Level Design document
Development and Test process standards
Corporate standards and guidelines
Tasks:
Understanding & Analyzing the Requirements
Risk Analysis
Test Strategy Implementation
Test Estimations (in terms of time, budget, resources, and scope of the project)
Team formation
Test Plan documentation
Configuration management planning
Creating Traceability matrix
Defining test environment setup
Output:
Test Plan document
System Test Plan
a. 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 members 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.
b. A Sample Test Plan Document for Internet Banking Application
1) Test Plan ID: IBS_ST_TP_001
2) Introduction:
It is System Test Plan for Interment Banking System, internet web application, provides access to Account holders and guest users from any ware in the world. It has two interfaces one is Admin interface another is User interface. Admin can be accesses by Bank authorized users, user interface can be accessed by Bank account holders and guest users.
The propose of the system (Application) is to provide bank information and services online (through Internet), Bank account holders can get Banking services from any ware, without visiting the Bank branches.
3) Test Items:
Admin Interface:
Master Data
User Management
Reports
etc…
User Interface
Information
Personal Banking
Corporate Banking
Business
Etc…
4) References:
Requirements
Project Plan
Test Strategy
—
Use cases (If available)
High Level Design doc
Low Level design docs
Process guide line doc
Prototypes
5) Features to be Tested:
- a) Admin Interface:
i) Master Data
1) Add new branch, Edit Branch /Delete Branch
2) Add new ATM
3) Add new loan type
4) Add new account type
5) Add new deposit type
….
ii) User Management
1) Create new user
2) Edit user
3) Delete user
etc…..
iii) Reports
1) Branch wise report
2) User wise report
3) Day, month, yearly reports
4) Service wise report (only loans, only new account. fixed deposits)b) User Interface:
i) Information
1) Branch locators
2) ATM locators
3) Loans information
4) Bank history
5) Bank financial details
6) Fixed deposits information
7) Calculators
etc…
ii) Personal Banking
1) Login
2) Balance enquiry
3) Bill payment (utilities, subscriptions)
4) Fund transfer (transfer to same bank, others banks)
5) Statement generation (mini stmt, detailed report)
etc…
iii) Corporate Banking
1) Add user, Edit user, Delete user
2) Balance enquiry
3) Money transfer
4) Payroll
5) Reports
etc..
6) Features not to be tested:
NA
7) Entry Criteria:
- a) Test Design
Team formation, Responsibilities, Schedule,
Requirements, Test Case Template etc…
Training on Domain, on Automation tools
- b) Test Execution:
Readiness of Test Lab
Readiness of AUT
Requirements
Test Case docs
Test Data
Defect Report Template
Etc…
8) Exit Criteria:
All possible test cases executed
Maximum defects fixed, Final Regression performed successfully
Confidence on Test process
Time Limitations
Budget Limitations
9) Suspension Criteria:
Show-Stopper bug found
Supplier issues
Vast changes in requirements
If resolving defects are more
10) Roles & Responsibilities
| Sno | Name | Role | Responsibilities | Remarks |
| 1 | Kareemulla SK | Test Lead | Test Planning, guidance, Monitoring and Test control | |
| 2 | Venkat Rao P | Sr. Tester | Test Data Collection, Generating Test Scenarios. | |
| 3 | Swapna DK | Tester | Test Case Documentation, Test execution, defect reporting and tracking for Admin module. | |
| 4 | Srinivas V | Tester | Test Case Documentation, Test execution, defect reporting and tracking for Personal Banking module. | |
| 5 | Suneetha B | Tester | Test Case Documentation, Test execution, defect reporting and tracking for Corporate Banking module. | |
| 6 |
11) Schedule:
| Sno | Task | Days | Duration | Remarks |
| 1) | Understanding & Analyzing Requirements. | 5 | 2nd July to 6th July | |
| 2) | Review Meeting | 01 | 9th July | |
| 3) | Generating Test Scenarios. | 10 | 11th July to 22nd July | |
| 4) | Reviews | 02 | 25th July to 26th July | |
| 5) | Test Case Documentation | 40 | 29th July to 12thAugust | |
| 6) | Reviews | 04 | 14th August to 18thAugust | |
| 7) | Test Data collection | 06 | 20th August to 26th August | |
| 8) | Reviews | 01 | 28th August | |
| 9) | Verifying Test Environment setup | 01 | 29th August | |
| 10) | Create Test batches | 02 | 30th, 31st August | |
| 11) | Sanity Testing | 01 | 3rd September | |
| 12) | Comprehensive Testing | 25 | 4th September to 2ndOctober | |
| 13) | Sanity Testing | 01 | 3rd October | |
| 14) | Selecting Test cases | 02 | 4th and 5th October | |
| 15) | Regression Testing | 05 | 8th October to12th October | |
| 16) | Sanity Testing | 01 | 15th October | |
| 17) | Selecting Test cases | 01 | 16th October | |
| 18) | Regression Testing Cycle 2 | 04 | 17th October to 22ndOctober | |
| . | . | . | . | |
| . | . | . | . | |
| . | . | . | . | |
| 28) | Final Regression | 08 | 19th November to 28th November | |
| 29) | Evaluating exit criteria | 01 or 02 | 29th, 30th of November | |
| 30) | Collecting all artifacts | 02 | 3rd, 4th December | |
| 31) | Test Summary Report | 01 | 5th December | |
Note: Regression Testing depends on Application and strength of Development team.
12) Training
Training Program on Banking Domain
Test Automation Training using QTP Tool
13) Risks & Mitigations
Team members issues
Vendor issues
Time
Budget
14) Test Environment / Lab
Application Type: Web Application, Internet and Public
Server side:
Windows 2003 Server
UNIX server
Ms Exchange server
a) Web server, b) EDP, 3) Data storage
Bugzilla Tool
VSS
MS Office
QTP Tool etc….
Browser IE 7.0
————————————
Client side:
Windows XP + SP2
VSS
MS Office
QTP
Etc…
———————————————
AUT Environment
.NET (C#, VC++, ADO)
IIS -web server
COM+ -App server
SQL Server 2005 for Database server
—————————————————
15) Test Deliverables
Test Plan,
Review Reports,
RTM
Test Scenario docs
Test Case docs
Test data
Opened, Closed Defect Reports
Test Summary Report
16) Approvals
| SNO | Task/s | Author /Role | Date & Signature |
| 1) | Test Plan Documentation | Kareemulla SK (Test Lead) | |
| 2) | Review | Hari Prasad (QA Analist) | |
| 3) | Approval | Vinod Rao (Project Manager) |
17) Glossary
AUT -Application Under Test
.
.
.
PIN -Project Initiation Note
.
.
.
SRS- Software Requirements Specification
.
.
.
