Oracle Migration Test Plan

Table of Contents:

PURPOSE OF ORACLE MIGRATION TEST PLAN .............................................................................................................2

I. OBJECTIVE..............................................................................................................................................................2
II. SCOPE ...................................................................................................................................................................2
III. TEST RESOURCES ................................................................................................................................................2
IV. TEST SCHEDULE ...................................................................................................................................................3
V. TEST RISKS ...........................................................................................................................................................3
VI. TEST TYPES .........................................................................................................................................................4
VII. TEST TOOL .........................................................................................................................................................4
VIII. TEST PREPARATION .........................................................................................................................................5
IX. TEST DELIVERABLES: ...........................................................................................................................................5
X. ENTRANCE (A) AND EXIT (B) CRITERIA FOR TESTING ..........................................................................................5
 Oracle Migration Test Plan – Draft 2/1/2002

Purpose of Oracle Migration Test Plan

To establish a test plan outlining the

1. Test objective
2. Test plan scope
3. Test resources
4. Test schedule
5. Test risks
6. Test types
7. Test tools
8. Test preparation
9. Test deliverables

I. Objective

To develop a test plan ensuring HRSA functionality, customizations, and interfaces working prior
to the Oracle migration are working after the migration from Sybase to Oracle.

II. Scope

The scope of this test plan is to identify the test resources from each functional area and the type
of test cases required for test preparation and test execution in HRSA (including other impacted
programs) at scheduled testing cycles. This test plan will cover only functionality testing of HRSA
and associated programs.

III. Test Resources

Functional Department FBA/Tester

Admissions - Undergraduate Demetrius Cunia

Admissions – Graduate Kathleen Kelly
Budget Sara Harrington
Campus Community Eileen Quilty, Harry Fleming
Financial Aid Cheri McEntee
Human Resources – HR Colleen Strempel
Human Resources – Benefit Sue Bird
Law College Ron Nabewaniec
Payroll John Maiura
Brian Pendergast
Student Financials Steven Kelly
John Murlin
Student Records – Advising Nancy Prince
Student Records – Course/class Wendy Love
Student Records – Records Steve Clark
Student Records – Registration Sue Peck
University College - Undergrad Anne Barker

Information Systems Developers

2
 Oracle Migration Test Plan – Draft 2/1/2002
Developers:
Admissions Larry Roux
Campus Community Harry Fleming
Financial Aid Pat Stanley
Human Resources Patty Bergin
Ray Brunner
Pat Cabrey
Payroll Patty Bergin
Ray Brunner
Pat Cabrey
Student Financials Marilyn Butler, Darlene Kennedy
Student Records Bill Keesler
Steve Wowelko

Oracle Migration Project Team

Database Conversion Eric Patten
Data Warehouse Tom Bloss
Development Ray Brunner
Express Lenny Heisler
Interfaces Eileen Quilty
Project Lead Larry Roux
QA Manager Open
Security Peter Giovinazzo
Test Coordination Mimi Mark

IV. Test Schedule

There will be three test cycles. The tester will have two weeks at the start of each cycle to test and
report defects. Prior to the test cycles, the testers will be requested to view and navigate a preliminary
version of HRSA in Oracle. The preliminary HRSA navigation test is expected to take place in March
2002. A final customer acceptance test will take place in September before HRSA (Oracle) goes live.

1. Prelim HRSA Navigation Test March 2002

2. 1st Test Cycle 2nd and 3rd weeks May 2002
3. 2nd Test Cycle 2nd and 3rd weeks June 2002
4. 3rd Test Cycle 2nd and 3rd weeks July 2002
5. Customer Acceptance Testing Morning of Sept. 15, 2002

V. Test Risks

Risks Contingency

· Lifecycle testing most likely will · FBAs to identify and develop critical
not be performed due to time and cross functional tests
technology constraints

· Not all tests are documented in · FBAs to provide weekly test

Test Director readiness reports to management.
Management will allocate staff’s time
3
 Oracle Migration Test Plan – Draft 2/1/2002
Risks Contingency
to get the job done.

· Tester’s time constraint · FBA manager commitment to

allocate a portion of the FBA’s time
to get the job done

· Financial Aid (FA) – not live until · FA will be documenting their tests in
Summer 2002 Test Director, so the tests will be
available to them to use for
migration testing.

· Student Financial (SF) – not live · SF should have tests documented in

until May 2002 Test Director prior to production.
This will reduce the amount of re-
working of tests for Oracle
Migration.
· Discuss with Project Manager –

· Test Data – need for current and · Have one database containing
stable test data current data and another one that is
stable
· Discuss with Oracle Migration
Project Lead

VI. Test Types

Test Director will be the tool used to document and manage tests and defects. Only functionality testing
will be performed by the testers. The tests that will need to be developed and prioritized are:
Responsibility
1. Automated Test Cases Test Coder

2. Manual Test Cases FBAs

a. Regression
b. Cross Functional Area
c. Security
d. Reporting
e. Interfaces
f. Customizations
g. Calendar year processes

Note: FBA Manager will be provided with test lists to review for any gaps in testing.

It is expected that there will be some overlap in tests between the different types of tests.

VII. Test Tool

Test Director (TD) will be the central repository for tests, test results, and defects. TD will be essential
toward monitoring the migration testing status and defects reported.

4
 Oracle Migration Test Plan – Draft 2/1/2002
* Almost all FBAs and developers have been trained to use TD.

VIII. Test Preparation

Completion
1. Test Coordinator (TC) updates FBAs on testing expectations mid-Feb 2002
for Oracle migration
2. FBAs documenting tests in Test Director. Feb– Apr 2002
3. FBAs updating weekly status on test documentation Feb– Apr 2002
4. Test Coordinator updates Project Manager on test prep. status Feb– Apr 2002

IX. Test Deliverables:

Responsibility Completion
1. Test Plan Approval IS and FBA Managers Feb 2002
2. Test Schedule Project Lead Feb 2002
3. Testing Entrance Criteria (A) See (A) and (B) criteria Apr 2002
4. Testing Exit Criteria (B) See (A) and (B) criteria 9/15/02
5. Testing Progress Report Test Coordinator May,Jun,Jul,Sep2002
6. Defect Status Report Test Coordinator May,Jun,Jul,Aug,Sep
2002
7. Customer Acceptance Approved FBAs/FBA Managers 9/15/02

X. Entrance (A) and Exit (B) Criteria for Testing

(A) Entrance criteria required before tests execution for test cycles

Responsibility
1. Test plan approval IS/FBA Managers
2. FBAs trained on TD Test Coordinator
3. Tests documented in TD FBAs
4. Tests coverage signoff FBA Managers
5. Test environment ready DBA/PS Tech Team
6. Test progress report developed Test Coordinator
7. Defect status report developed Test Coordinator

(B) Exit criteria required before customer acceptance testing is declared completed.

Responsibility
1. All defects resolved FBAs/Developers
2. Testing Completed FBAs
3. Customer Acceptance Test Signoff FBAs/FBA Managers