8/9/2014

Home

A Sample Test Plan ~ Software Testing

UFT Guide

QTP Online Training

Projects

Selenium Tool

VBScript for UFT

Software Testing
Manual Testing, HP UFT, VBScript for UFT, Quality Center,
LoadRunner, C and SQL by G C Reddy (91-9247837478)

Manual Testing

QTP

Testing Question Bank

Manual Testing Videos
UFT Videos

QTP Online Training

SQL

C Language

Java

Oracle FAQ

Resum es

UFT Guide

A Sample Test Plan

11:23 PM

G.C. REDDY

UFT Videos

Softw are Testing FAQ

Search

NO COMMENTS

Software Test Plan Documentation

SQL For Testers

Banking Domain

G. C. REDDY
2 circles

Insurance Domain

967

V IE W M Y COM P LE TE
P ROF ILE

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

Sample Test
Configuration management planning
Sample Executive Summary
Creating Traceability matrix
Defining test environment setup
Test Internet
[Link]

1/10

8/9/2014

A Sample Test Plan ~ Software Testing

Join to G C Reddy Group

Email:

Output:
Test Plan document

Subscribe
Visit this group

POPULAR POSTS
VB Script for QTP

Test Plan Documentation

-----------------------

a) Test Plan Template

1) Test Plan ID:

QTP Guide

Some type of unique company generated number to identify this test plan.

SQL and Pl/SQL Interview

Questions

2) Introduction:

QTP Scripting
manual testing interview
questions

Software Test Cases

Project Proposal Sample
Software Testing
BLOG ARCHIVE
2014 (165)
2013 (730)
2012 (143)

Describe the purpose of the Plan, possibly identifying the level of the plan

December (39)
November (19)

(System Test Plan etc.). This is essentially the executive summary part of the
plan.

October (3)

3) Test Items:

September (2)

SQL Interview Questions

QTP Basic Features
Manual Testing Interview
Questions 2

These are things you intend to test within the scope of this test plan.

An overview on Test
Automation

4) References:

QTP Online Training

version/release number of the document as stored in the configuration

July (18)
List all documents that support this test plan. Refer to the actual

SQL Interview
Questions

management system.

Database Testing

5) Features to be Tested:

LoadRunner Interview
Questions

..
ANALYTICS

August (2)

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

Ecommerce domain
top 10

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

Web Testing Interview

questions
testing fresher cv
test documents
LoadRunner
Certification
Performance Testing
testing interview
questions

with all higher and lower levels of plans. Overall rules and processes should be
identified.

Automation Scenario
Defect Reporting

8) Entry Criteria:
It describes when to start Testing

ISTQB Paper 14
ISTQB Question
Paper

9) Exit Criteria:
ISTQB dumps 12
It describes when to stop testing

10) Suspension Criteria:

It describes when to stop testing temporarily.

[Link]

ISTQB questions 11
A Sample Test Plan
June (21)

2/10

8/9/2014

A Sample Test Plan ~ Software Testing

May (21)
11) Roles & Responsibilities
March (3)
Team Lead or Test Lead and Team members Roles and Responsibilities.
12) Schedule:

February (2)
January (13)

Schedule for all Test activities in this Software Test Process.

2011 (54)
13) Training:

2010 (138)

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
understood 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

[Link]

3/10

8/9/2014

A Sample Test Plan ~ Software Testing

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
etc.....
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

[Link]

4/10

8/9/2014

A Sample Test Plan ~ Software Testing

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:

[Link]

5/10

8/9/2014

A Sample Test Plan ~ Software Testing

Show-Stopper bug found
Supplier issues
Vast changes in requirements
If resolving defects are more

10) Roles & Responsibilities

Sno

Name

Role

Responsibilities

Kareemulla SK

Test Lead

Test Planning,

Remarks

guidance, Monitoring
and Test control
2

Venkat Rao P

Sr. Tester

Test Data Collection,

Generating Test
Scenarios.

Swapna DK

Tester

Test Case
Documentation, Test
execution, defect
reporting and tracking
for Admin module.

Srinivas V

Tester

Test Case
Documentation, Test
execution, defect
reporting and tracking
for Personal Banking
module.

Suneetha B

Tester

Test Case
Documentation, Test
execution, defect
reporting and tracking
for Corporate Banking
module.

11) Schedule:
Sno

Task

Days

Duration

1)

Understanding &

2nd July to 6th July

Remarks

Analyzing
Requirements.
2)

Review Meeting

01

9th July

3)

Generating Test

10

11th July to 22nd

Scenarios.

July

4)

Reviews

02

25th July to 26th July

5)

Test Case

40

29th July to 12th

Documentation
6)

Reviews

August
04

14th August to 18th

August

7)

Test Data

06

collection

20th August to 26th

August

8)

Reviews

01

28th August

9)

Verifying Test

01

29th August

Environment setup

[Link]

6/10

8/9/2014

A Sample Test Plan ~ Software Testing

10)

Create Test

02

30th, 31st August

batches
11)

Sanity Testing

01

3rd September

12)

Comprehensive

25

4th September to

Testing

2nd October

13)

Sanity Testing

01

3rd October

14)

Selecting Test

02

4th and 5th October

8th October to12th

cases
15)

Regression Testing

05

16)

Sanity Testing

01

15th October

17)

Selecting Test

01

16th October

04

17th October to

October

cases
18)

Regression Testing
Cycle 2

22nd October

28)

Final Regression

08

19th November to
28th November

29)

Evaluating exit

01 or 02

criteria
30)

Collecting all

29th, 30th of
November

02

3rd, 4th December

01

5th December

artifacts
31)

Test Summary
Report

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

[Link]

7/10

8/9/2014

A Sample Test Plan ~ Software Testing

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

[Link]

8/10

8/9/2014

A Sample Test Plan ~ Software Testing

SNO

Task/s

Author /Role

1)

Test Plan

Kareemulla SK (Test

Documentation

Lead)

2)

Review

Hari Prasad (QA Analist)

3)

Approval

Vinod Rao (Project

Date & Signature

Manager)
17) Glossary
AUT -Application Under Test
.
.
.
PIN -Project Initiation Note
.
.
.
SRS- Software Requirements Specification
.
.
.
------------------------------------------------------------------------------

Also Visit:

Test Case Documentation

Test Summary Report
Defect Report
Posted in: Softw are Test Plan,Test Plan Documentation,Test Plan Template,Test Planning Phase

+3 Recommend this on Google

New er Post

Home

Older Post

0 comments:
Post a Comment

Preview
anshuman biswas said...
bxsjsx
August 9, 2014 at 1:04 AM

Add profile picture

Please prove you're not a robot

Links to this post

Create a Link

[Link]

9/10

8/9/2014

A Sample Test Plan ~ Software Testing

Copyright 2011 Software Testing | Powered by Blogger

[Link]

10/10