Savior Version 1.

1
Test Plan

Savior 1.1

Test Plan

Table of Contents
1.
2.
3.
4.
5.
6.

Document Revision History.......................................................................................................3

Document Identification............................................................................................................3
Summary....................................................................................................................................3
[Project Name] [N.N.N] Test Plan Objectives...........................................................................3
Reference Material.....................................................................................................................3
Scope of Work............................................................................................................................4
6.1...Items To Test...............................................................................................................................................4
6.2...Items To Not Test........................................................................................................................................4

7. Test Strategy and Approach.......................................................................................................4

8. Estimate and Schedule...............................................................................................................4
8.1...Resources....................................................................................................................................................4
8.1.1. Staff.................................................................................................................................................4
8.1.2. Hardware........................................................................................................................................4
8.1.3. Software..........................................................................................................................................4
8.1.4. Other...............................................................................................................................................4
8.2...Schedule......................................................................................................................................................5

9. Issues/Risks/Assumptions..........................................................................................................5

Page 2

Savior 1.1

1.

Test Plan

Document Revision History

Author

Date

Version

Description

Tanay, Keyur,
Rayan,
Amarmath
Tanay, Keyur,
Rayan,
Amarmath
Tanay, Keyur,
Rayan,
Amarmath

04/15/14

1.0

Added: Introduction, Test Objectives, and Items to Test

04/22/14

1.1

Edited: Test Objectives and Items to Test.

Added: Items that will not be Tested, Resources

04/29/14

1.2

2.

Document Identification

Project Name

Savior

Document Name

Integration Test Plan

Status

Reviewed

3.

Introduction

Based on the Functional Requirements Document and the Design Document for Savior 1.1, we created
this Software Test Plan so that we can effectively manage the Quality Assurance process. We designed
the Software Test Plan (STP) to prescribe the scope, approach, resources, and schedule of all testing
activities. This plan identifies the items and features we test, the types of testing we perform, the
personnel responsible for testing, the resources and schedule necessary to complete testing, and risks.

4.

Savior 1.1 Test Plan Objectives

These are the objectives for the Savior 1.1 Test Plan:
Remote Access Successful login from any number of workstations, not including the server. If this test
is successful, it will proceed to perform sub-tests of the categories below.
Local Access Successful login from the local host of the server. If this test is successful, it will proceed
to perform sub-tests of the categories below.
Transmission/History Successful transmission of SMS to a mass group of contacts and individual
users, as well as a record of the transmission in history (From Localhost and Workstation).
Importing/Associating Groups Successful import of groups into the composition interface, meaning
that as one group is checked, each contact that is a member of that group will become a message recipient
(From Localhost and Workstation).
Savior Contact AdministrationSuccessful implementation of a contact management interface. This
ideally will give the administrator/authorized users the privileges of adding contacts to the text message
management system (From Localhost and Workstation).
Savior Group AdministrationSuccessful implementation of a contact management interface. This
ideally will give the administrator/authorized users the privileges of adding contacts to the text message
Page 3

Savior 1.1

Test Plan

management system (From Localhost and Workstation).

Savior User Administration Successful implementation of a user management interface. This ideally
will give the administrator privileges to add users and specific roles to Savior (From Localhost and
Workstation).

5.

Reference Material

List all documents this Test Plan references:

Document

Release Date

Description

Design
Document
Project
Requirement
Specification
Project plan

[MM/DD/YY]

Design for [Project Name] [N.N.N].

6.

Scope of Work
6.1.

Items To Test

These are the items we will test.

User AuthenticationThis test will ensure that the system and all pages therein are secure from
unwanted access.
Adding ContactsThis test will ensure that every process and component in adding users and
their information is working properly.
Adding Members to Groups This test will ensure that every process and component in
member addition is working properly.
Sending Messages to Groups This test will ensure that every process and component of
sending group messages is working properly, including but not limited to: Adding groups to
message composition interface, group member management, group/member association, and
successful transmission of these messages to each member of each group.
Sending Messages to IndividualsThis test will ensure that every process and component of
sending individual contacts messages is working properly, including but not limited to: Selecting
multiple individual users to add to the message composition interface, and successful
transmission of messages to these users.
Message History This test will ensure that every process and component of the message history
interface is working properly. It will mainly test the message storage methods, as well as the
message filtering methods.
Post-Dated Messages This test will ensure that every process and component of the post-dated
messaging function is working properly. This can be found within the Settings interface.

Page 4

Savior 1.1

Test Plan

6.2.

Items Not To Test

These items will not be tested.

Message History
Post-dated Messages
Default System Interface

7.

Test Strategy and Approach

<The Test Strategy presents the recommended approach to the testing of the target-of-test. The previous
section, scope of work, described what would be tested - this describes how the target-of-test will be
tested. For each particular test, use the test case template (the attached Excel file).>

8.

Estimate and Schedule

Estimate the resources you need to complete all activities and create the schedule.

8.1.

Resources

List all resources you need to complete all of your activities:

8.1.1. Staff
Role

Quantity

Skills/Domain Expertise

General Tester
General Tester

2
2

Web Applications and Database Management

Hardware, Networking, and Server Configuration

8.1.2. Hardware
Item

Quantity

Detail

Workstation

Workstation
Server/Workstation

2
1

2 Workstations within the UCO domain, preferably in MCS

building.
2 Workstations outside of the UCO domain.
1 Server workstation hosting the web application.

8.1.3. Software
Item

Quantity

Detail

Glassfish Server
Apache Derby
DB
Browser/JRE

1
1

Glassfish server management mechanism.

Apache Derby DB managing the database aspect of the application.

Any browser on workstation with the Java Runtime Environment,

preferably the latest version.

8.1.4. Other
Item

Quantity

Detail

Page 5

Savior 1.1

Test Plan

8.2.

Schedule

Account for all test activities:

Activity

9.

Deliverables

Start Date

Delivery
Date

Owner(s)

Issues/Risks/Assumptions
[List all issues/risks.]
Schedule
Technical
Management
Personnel
Requirements

Page 6