Test Plan

climbmoujeanteaΛογισμικό & κατασκευή λογ/κού

13 Δεκ 2013 (πριν από 3 χρόνια και 10 μήνες)

94 εμφανίσεις




Team Oompa

Test Plan

Master Test Plan for The Gate Sporting Goods

ERM System

Jack Vanderhorst, Valerie Bombardier, Ryan Tucker, Edison Sinani

3/12/2010



Introduction

This is the test plan for design, development and implementation of The Gate Spor
ting Goods’
Enterprise Management System being developed by Oompa Inc. The purpose of this plan is to outline in
detail the scope of Quality Assurance measures to be taken by Oompa Inc in parallel with
its
analysis,
design, development, implementation and

maintenance of the proposed system

at The Gate Sporting
Goods.

All documented test items will be thoroughly scrutinized through a series of unit, integration,
and acceptance testing as documented in this test plan.

Target Test Components

A.

Database

a.

Implem
entation of Relational Integrity

b.

Field Constraints

B.

Data Access layer

a.

Generated Entity Framework Classes

b.

Reporting Components

C.

Business Intelligence

a.

Business Classes

b.

Coupling

c.

Implementation of Business Logic

D.

Presentation Layer

a.

In
-
house ERM application

i.

Custom
er module

ii.

Vendor module

iii.

Inventory module

iv.

Sales Order module

v.

POS module

vi.

General Ledger

vii.

Accounts Receivable

viii.

Accounts Payable

ix.

Reporting

b.

Reporting Component accuracy

c.

Customer web portal

i.

Company introduction

ii.

Product browsing

iii.

Login portal

iv.

Shopping cart

v.

Payment p
rocessing

vi.

Checking order status

E.

Security

Concerns

a.

Authentication

b.

Authorization

c.

Fault tolerance

Areas of Risk

Certain factors will contribute to the success of the overall system but are not directly under the control
of The Gate or Team Oompa but need to
be anticipated and planned for.



Web
host
availability

o

Alternative online hosting arrangements will be required to increase fault tolerance of
The Gate’s desired online presence, and recovery scenarios will be tested.



Power outages

o

Hardware requirements wil
l include UPS modules to be connected to any and all
information systems where the proposed system will reside or operate including
servers, workstations, terminals, and network appliances.



Distribution for Fault tolerance

o

Individual hardware appliances sh
ould all be expendable on their own
;
a single
hardware failure of any kind should not cripple the system.



Proactive System Monitoring

o

IP level software will monitor hardware health and be deliberately tested for accuracy
during the development phase and mo
nthly reports generated in the maintenance and
future phases.

Features to be tested

A.

Database

a.

Referential integrity and data constraints will be verified by intentional hand crafted
attacks on it.

B.

Business Intelligence Layer

a.

Generated Entity Framework class
es will be tested with automated Unit Tests

b.

Unit tests will be written to test primary business logic routines and class interaction of
our own classes.

c.

Development of Units Tests will take place either before or in parallel with the
development of compone
nts themselves.

d.

Property Change notification will receive specific attention

e.

Multi
-
threaded components will receive specific attention

f.

Data
-
binding
-
aware components able will receive specific attention

C.

Presentation Layer

a.

In
-
house

i.

The process of adding, del
eting and modifying an existing customer or vendor

ii.

The process of adding, deleting and modifying inventory items

iii.

The process of entering, invoicing, modifying and deleting an order

iv.

The process of printing reports

v.

The process of posting items to Accounts Re
ceivable

vi.

The process of posting items to Accounts Payable

vii.

Accuracy of the General Ledger

viii.

Accuracy of user documentation

b.

Website

i.

The process of browsing products

ii.

The general look and feel of the site

iii.

The process of adding and modifying an online profile

iv.

The

process of purchasing and processing payment for items online

v.

The process of customers logging in and out of the site

c.

Security

i.

Proper s
torage of sensitive
customer, vendor and employee data

ii.

Database protection through views and parameterized input

iii.

Isolati
on of employee access with role
-
based access

to entire system

iv.

Online customer protection

with careful consideration of all input

v.

HTTPS for payment processing only

Features Not to be Tested

A.

All Report design and appearance, this will be approved by manageme
nt.

B.

Financial auditing will be outsourced to a CA and is outside the scope of this project.

C.

Staff scheduling is outside the scope of this project but may be considered for a future project.

Testing Levels

A.

Unit testing will be conducted by the developer in
parallel with any development tasks that are
assigned. The tests themselves, any test data and the test results will be submitted for approval
and criticism by the rest of the team

B.

Integration testing will be conducted by the developer responsible for the

particular integration
of components i.e. Communication between application tiers. Each communication point will
be validated in either direction necessary with an automated Unit test whenever possible, and
alternatively using a test form as described be
low.

C.

Acceptance testing will be conducted by the entire team towards the end of the development
phase
but
before delivery and maintenance.

All members will submit details of their overall
experience conducting and documenting as many user
-
level test cases

as they can manage.
Undocumented test cases will be considered incomplete and not considered.

Tools

A.

Testing is
conducted through
Unit Testing
in
Visual Studio Team System test projects, manual
test forms as
outlined
below, cross
-
browser compatibility tes
ting

for web component
,
installation and configuration testing on Windows operating system
s

as pu
rchased for the In
-
House workstations and servers, and general user acceptance testing of presentation layer
functionality.

B.

Unit tests will be stored in the Su
bversion source code repository
along with the project source
code.

C.

Testing forms and documentation will be stored on SourceForge.NET under Project Files


Example
Testing Form


Date
Tested

Function
Tested

Steps
Performed

Data

Used

Expected
Results

Actual

Results

Pass / Fail























Meetings

A.

Meetings are conducted remotely based on the need. If someone has a concern a meeting can
be called at any time via E
-
mail otherwise progress is monitored on the “Recent Activity” section
on SourceFo
rge.


Test Deliverables


A.

Results of Unit testing
dated
throughout development
and implementation
phase
s

B.

Complete
,
proof read,
and
signed off
test
ing

forms

for individual system components