ERP-StockEase

Software Test Plan

V1.0
Name Role Date
Prepared By K.Samuel Arun Kumar QM 06-Mar-06

Reviewed By K.Samuel Arun Kumar QM 06-Mar-06

Approved By K.Samuel Arun Kumar QM 06-Mar-06

A-Added, M-Modified, D-Deleted

Change Brief
Version
Sno Date Page No Mode Description of
No
(A/M/D) Change

1 Yaami Integrated Solutions Confidential STP 1.0

Contents

1. Introduction

The Software Test Plan (STP) is designed to prescribe the

scope, approach, resources, and schedule of all testing
activities. The plan must identify the items to be tested,
the features not to be tested, the types to be performed,
the personnel responsible for testing, the resources and
schedule required to complete testing, and the risks
associated with the plan.

1.1. Objectives

The objective of the Test Plan is:

a) To identify the components or modules to be tested.

b) To identify and determine the resources required to
perform the testing process.
c) To identify and estimate the task schedules for each
level of testing process.
d) To define the test deliverables.

1.2. Test Strategy

Test Strategy is a management plan that involves ingenious

methods to achieve ends. In the context of testing a
strategy can be defined as a high-level management method
that confirms adequate confidence in the software product
being tested, while ensuring that the cost, effort, and
timelines are all within acceptable limits.

The Test Strategy for ERP-STOCKEASE is classified into

following sections of the Test Plan document.

1.3. Scope

Testing will be performed in several points in the life

cycle as the product is constructed. Testing is a very
“dependent” activity. As a result, test planning is a
continuing activity performed throughout the system
development life cycle. Test plans must be developed for
each level of testing.

The scope of this Test Plan document is the testing process

for entire ERP-STOCKEASE.

2 Yaami Integrated Solutions Confidential STP 1.0

 1.4. Referential Material

a) User Manuals and FRS Documents.

b) Wire-frame Documents.
c) Use-Case Documents.

2. Test Items

2.1. Program Modules

This section outlines testing to be performed by the

developer for each module being built.

2.2. User Procedures

This section describes the testing to be performed on all

user documentation to ensure that it is correct, complete,
and comprehensive.

3. Features To Be Tested

The features to be tested within ERP-STOCKEASE are classified

under the following modules as:

a) Admin

Unit of Measurement, Item Group, Departments, Q.C

authorized employees, Rejection Type, Transaction Code and
User-Levels.

b) Masters

Item and Supplier.

c) Transactions

Purchase Requisition, Receipts, QC Acceptance, Receipt

Returns, Issues, Issue Returns, Transfer, Adjustments,
Miscellaneous Receipts, and Work Requisition.

d) Reports

Various reports generated that are classified under Daily,

Periodical and MIS reports.

3 Yaami Integrated Solutions Confidential STP 1.0

4. Features Not To Be Tested

Not Applicable

5. Approach

5.1. Smoke Testing

Initial testing done to check and ensure the availability of

the major functionalities in the AUT.

5.2. Sanity Testing

Initial testing done to check and ensure the stability of

the application to perform thorough testing.

Note: Smoke and Sanity Testing are considered as Build

Acceptance Testing.

5.3. Interface Testing

Testing done on the AUT to check and ensure the Look-N-Feel

of the user interfaces.

5.4. Functional Testing

Actual Verification and Validation testing done on the AUT.

5.5. Re-Testing

The testing done on the application after the bug is

resolved to ensure that the bug is really fixed.

5.6. Regression Testing

The testing done on the dependent functionalities in the AUT

that were working fine to ensure it doesn’t have an adverse
effect of any refinement of failed functionalities or
addition of new functionalities.

5.7. Integration Testing

The testing on the AUT when the modules within the AUT are
being integrated together to ensure the functionalities are
still working fine even after Integration.

5.8. System Testing

Testing done on the AUT when all the proposed modules are
integrated as a single unit and deployed in the Client
specified environment. The focus areas of System testing are
Non-Functional areas like Compatibility, Configuration,
Database, Load/Stress/Performance, Browser Compatibility/
Capability and Network testing.

4 Yaami Integrated Solutions Confidential STP 1.0

 5.9. Automation Testing

Testing done on the AUT with the use of software tools.

Automation testing is performed for Re-testing, Regression
Testing, Repetitive Testing and Load/Stress/Performance
testing.

6. Pass/Fail Criteria

6.1. Suspension Criteria

a) When the AUT is failed in the Build Acceptance Testing.

b) Whenever there is a Change Request.
c) Delay in publishing the input documents.

6.2. Resumption Criteria

a) Testing can be resumed after the patch is released for

the rejected build.
b) When specification documents are refined and base-lined
based on CR acceptance or rejection.
c) After the input documents are published.

6.3. Approval Criteria

When the status of the bugs in the Defect profile is

“Closed” and result column in the TCD is “Pass”. This
ensures the proposed functionalities are justified in the
System.

7. Testing Process

7.1. Test Deliverables

a) Defect Profile Documents.

b) Test Summary Reports.
c) Test Execution Reports.

7.2. Testing Tasks

a) Review of Functional specification document and

preparation of Review Report.
b) Preparation of Test Case documents.
c) Execution of the TCD’s.
d) Result Analysis based on Actual Behavior and Expected
Behavior.
e) Defect Tracking.
f) Bug Reporting.
g) Ensuring bug-fixing process.

5 Yaami Integrated Solutions Confidential STP 1.0

 7.3. Responsibilities

a) B.Suresh Babu – Project Manager/ Business Analyst

b) L.Bhanu Prakash – QC - Manager
c) K.Samuel Arun Kumar – Quality Manager
d) J.V.Amar – Sr. Quality Lead
e) J.Madhukar – Quality Lead
f) K. Dharmaveer –Quality Lead
g) S. Karthik – Quality Lead (Automation)

7.4. Resources

a) Members of QA8 Team-A

b) Members of QA8 Team-B

7.5. Schedule

Schedule
Sno Task (in From Date To Date
Days)
Admin
a) WF – UCD (User
1 1.5 days 22-jun-06 23-jun-06
Levels) Review and
RR preparation
a) RR with
clarificati
2. .5 days 23-jun-06 23-jun-06
on release
b) Review Meeting
a) TCD Preparation
3. (User 3 days 24-jun-06 27-jun-06
Levels)
a) Refinement and
4. Baseline of 1 Day 28-jun-06 28-jun-06
TCD
Masters
a) WF – UCD (Item)
5. 1.5 days 29-jun-06 30-jun-06
Review and RR
preparation
a) RR with
clarificati
6. .5 days 30-jun-06 30-jun-06
on release
b) Review Meeting
TCD Preparation
7. (Item 2.5 days 31-jun-06 3-Jul-06
Master)
Refinement and
8.
Baseline of .5 Day 3-Jul-06 3-Jul-06
TCD
Transactions
a) WF – UCD
9. 1.5 Days 4-Jul-06 5-Jul-06
(Receipts) Review
and RR preparation

6 Yaami Integrated Solutions Confidential STP 1.0

 a) RR with
clarificati
10. .5 days 5-Jul-06 5-Jul-06
on release
b) Review Meeting
11. a) TCD Preparation 1 day 6-Jul-06 6-Jul-06
a) Refinement and
12. Baseline of .5 days 7-Jul-06 7-Jul-06
TCD
Reports
13. a) User Manual 1 days 7-Jul-06 8-Jul-06
Walk-Through
a) RR with
clarificati
14. .5 days 8-Jul-06 8-Jul-06
on release
b) Review Meeting
Overview Session &
15. Execution .5 days 10-Jul-06 10-Jul-06
Plan
Build#1 Execution
Admin
16. Module 2 days 11-Jul-06 12-Jul-06
Preparation of
Defect Profile
Masters Module
17. Preparation of 2 days 13-Jul-06 14-Jul-06
Defect Profile
18. Transactions Module 4.5 days 15-Jul-06 20-Jul-06

19. Reports Module 2 days 20-Jul-06 22-Jul-06

Build#2 Execution
20. 2 days 22-Jul-06 25-Jul-06
(All Modules)
System Testing
21. Scenario Analysis 2 days 25-Jul-06 27-Jul-06
Execution
Automation Testing
22. Preparation & 8 days 28-Jul-06 5-Aug-06
Execution
Web Testing &
23. Database 2 Days 6-Aug-06 8-Aug-06
Testing

8. Environmental Requirements

8.1. Hardware

Description Server Client

Processor Intel Pentium III Intel Pentium II or III
Main Memory 64 MB RAM or more 16 MB RAM or more
Hard Disk 18 GB hard disk drive 1 GB and above
Printer 136 Column Dot Matrix 136 Column Dot Matrix Printer
Printer

7 Yaami Integrated Solutions Confidential STP 1.0

 CD ROM 52 X CDROM Drive 52 X CDROM Drive
Ethernet Card 32 Bit PCI Fast 32 Bit PCI Fast
EthernetCard EthernetCard
Monitor 15” SVGA Color 15” SVGA Color
Key Board 104 Key Board and Mouse 104 Key Board and Mouse
Floppy Disk 1.44 MB Floppy Disk Drive 1.44 MB Floppy Disk Drive

8.2. Software

Description Software Requirements

Operating System Windows 95 / Windows NT workstation
Network Novell Netware 3.1 and above / Windows NT
RDBMS Microsoft SQL Server Version 7.0 Enterprise
Edition(Back End)
Front End Tool Microsoft Visual Basic 6.0 Enterprise Edition(Front End)

8.3. Tools

a) Version Control System – VSS.

b) Functional Testing – WinRunner/ QTP.
c) Bug Tracking – yTracker (Yaami Issue Tracker).
d) Test Management – Test Director.

8.4. Publications

a) Essentials of Software Testing – William.O.Perry

b) Software Testing (Methods, Techniques) – Renu Rajani
c) Software Testing (Principles and Practices) – Srinivasan
Desikan & Gopalaswamy Ramesh.

8.5. Risks and Contingencies

a) Schedule

The schedule for each phase is very aggressive and could

affect testing. A slip in the schedule in one of the other
phases could result in a subsequent slip in the test phase.
Close project management is crucial to meeting the
forecasted completion date.

b) Personnel

Due to the aggressive schedule, it is very important to have

experienced testers on this project. Unexpected turnovers
can impact the schedule. If attrition does happen, all
efforts must be made to replace the experienced individual.

d) Requirements

8 Yaami Integrated Solutions Confidential STP 1.0

 The test plan and test schedule are based on the current
Requirements Document. Any changes to the requirements could
affect the test schedule and will need to be approved by the
CCB.

9. Change Management Procedures

Impact Analysis and Risk Analysis are done to evaluate the

effort of re-engineering and impact on existing
functionalities if the CR is incorporated.

10.Plan Approvals

K.Samuel Arun Kumar – Quality Manager.

9 Yaami Integrated Solutions Confidential STP 1.0