Test Plan
APPO Sybase - Oracle Conversion
November 2002 – March 2003
Introduction
APPO (Accounts Payable and Purchase Orders) is an acronym for the PeopleSoft system that
includes the Accounts Payable and Purchasing software modules. The main functional areas
that use the software are Disbursements, Purchasing and Materials Distribution. APPO handles
all payments for products and services provided to the University, including payments due to
vendors used by central Purchasing, the Bookstore, Library, Student Financials, Financial Aid,
Dining and Publications.
The test plan not only encompasses stand alone payments (non match vouchers) to vendors,
but also includes an interactive plan between the three functional areas to track and process the
life cycle of a requisition; from order origination, initiation and processing of the purchase order,
receipt of the material, processing the invoice, and initiation of a check to a vendor for payment.
Purpose
The purpose of the test plan is to ensure that the current Accounts Payable Purchase Order
(APPO) system on PeopleSoft 7.5 SP2 using a Sybase database will continue to work and give
consistent results after converting to an Oracle database.
Components
The test plan consists of the following:
I.
II.
III.
IV.
V.
VI.
VII.
VIII.
IX.
X.
XI.
Resources
Business Activities
Strategy
Approach
Environment
Test Management Tool
Schedule
Risks/Contingencies
Assumptions
Deliverables
Approval
Dated: 12-20-2002
1
Test Plan
APPO Sybase - Oracle Conversion
November 2002 – March 2003
I.
Test Resources
Functional
Area
APPO
Role
Manager
Manager
Testers
P – Primary
B – Backup
ECM
IS
Project Analyst
Developer
Manager
Test Coordinator
Automated Tester
Dated: 12-20-2002
Person
Contact
Purchasing: Allan Breese
Disbursements: Kathy Hartelius
Christina Julian, Purchasing, P
Cindy Caramella, Purchasing, B
Gail Jackson, Purchasing, B
Mike Cusano, Disbursements, P
Diane Deneve, Receiving, B
Melissa Yandon, Receiving, B
Diane Oad
Phil Driscoll
Pat Cabrey
Alex Corsello
Mimi Mark
Myra Daly
[email protected], x2793
[email protected], ,3148
[email protected], x2283
[email protected] x2286
[email protected] x2281
[email protected] x4994
[email protected], x2446
[email protected], x1940
[email protected], x1000
[email protected] , x9272
[email protected], x3710
[email protected], x4876
[email protected], x3449
[email protected], x9257
2
Test Plan
APPO Sybase - Oracle Conversion
November 2002 – March 2003
II.
Business Activities To Be Tested
Activities
Purchasing
Purch./Disb.
Purch./Disb.
Disbursement
Purch./Disb.
Express Jobs
A.
B.
C.
D.
E.
F.
G.
H.
I.
J.
K.
L.
M.
N.
O.
System
Balancing
Online Panel
Access
Functional
Security
Brio Reporting
P.
Performance
Tests
T.
Dated: 12-20-2002
Q.
R.
S.
Functionality
Testers
PO Reservation
On-line Purchase Orders
Web Requisitions
Web Inquiries
PO Workbench
Workflow Activities
Commitment Accounting
Receiving
PO Reconciliation
Match Rules- PO Voucher
PO Voucher
Non-Match Voucher (Non PO payments)
Check Issuance
Vendors
To APPO:
1. Bookstore
2. Library
3. Student Financials
4. Financial Aid
From APPO
5. G/L
1. Online Entry Batch
2. Balance Voucher Commitments
1. Vendor Setup
2. Panel Updates
1. Application Security
Julian/Caramella
Julian/Caramella
Julian/Caramella
Julian/Caramella
Julian/Caramella
Julian/Caramella
Julian/Caramella
Julian/Caramella
Julian/Caramella
Julian/Cusano
Cusano/Julian
Cusano
Cusano/Driscoll
Cusano/Julian
- Driscoll/Cabrey runs.
- Cusano balances.
1. Queries against production
2. Queries against DW
- Note, DW testing will be handled
through DW Oracle conversion test plan.
1. PO Edit
2. PO Reconciliation
3. Payment Posting
Cusano/Julian
Cusano
Julian
Cusano/Julian
Cusano
Julian/Caramella
Julian/Caramella
Cusano
3
Test Plan
APPO Sybase - Oracle Conversion
November 2002 – March 2003
III. Test Strategy
There will be two test cycles, one in January 2003 and the other in February 2003. Each test
cycle lasts three weeks. The three weeks of testing will allow APPO to go through a
complete business cycle of purchasing and disbursement activities. The testing format will
be similar to what is done in APPO regression testing today.
During Oracle testing, there will be some corresponding Sybase testing to capture results for
comparisons against Oracle test results.
IV. Test Approach
Each test cycle lasts three weeks. On the first day, IS test coordinator runs five automated
tests, generating approximately 100 different types of purchase orders that become the basis
(test data) for additional testing that takes place during the duration of the test cycle.
The following is a broad view of how Purchasing, Materials Distribution and Disbursements
interact through the test cycle. Purchasing uses the test data to manipulate different
purchasing test scenarios. Materials Distribution (Julian) than performs receiving tests.
Disbursements perform testing of different voucher and payment scenarios, based on the test
purchase orders.
Disbursements also perform testing of non-match vouchers and processing of checks for
payment to vendors. These are non-purchase order payments.
Most of the testing is complete during the first two weeks of testing. The third week is
typically used for troubleshooting any potential problems.
Dated: 12-20-2002
4
Test Plan
APPO Sybase - Oracle Conversion
November 2002 – March 2003
V. Test Environment
·
The Oracle test environment should be set up to allow testing of the business
activities listed above. This would include any redevelopment that needs to be
completed.
·
The Oracle test environment should contain the latest patch updates from PeoplesoftFix 19.
·
The Oracle test data should be a copy of the current production data.
·
The tester’s security for Oracle testing should be the same as his/her test security for
regression testing today. Note, there are a couple testers that require special security
to allow for workflow testing, as indicated in the Workflow Setup column below. Listed
are the buttons needed for each tester.
Testers
Christina Julian
Cindy Caramella
Gail Jackson
Mike Cusano
Diane Deneve
Melissa Yandon
Diane Oad
Mimi Mark
Phil Driscoll
Pat Cabrey
Myra Daly
DEV
Button
1
1
TEST
Button
1
1
1
1
1
1
1
1
1
1
1
TEST
Workflow
Button
6
6
1
The Sybase test environment, as of 12/16/02, should remain available after the latest round of
regression testing to allow testers to compare functionality between systems in Sybase and
Oracle, as needed.
Dated: 12-20-2002
5
Test Plan
APPO Sybase - Oracle Conversion
November 2002 – March 2003
APPO Test Environment Diagram
Test Environment
Test Cycle
QA (Sybase)
DB00040
Sybase PROD
Copy
at
the D
sta ata
rt o Re
f e fres
ac h
ht
es
tc
yc
le
Sybase 40MGRP
Data Mover
APPO
Oracle TEST
server 10
DB00048
(AP7TEST)
Changes in Oracle DEV are
migrated to Oracle TEST
APPO
Oracle DEV
DB00047
(AP7DEV)
Development
Environment
Data Mover
Copy
Sybase PROD
Sybase DEV
VI. Test Management Tool
Test Director will be used to store and maintain APPO tests and defects. The test coordinator will work
with the APPO test team to get their tests loaded to Test Director prior to the testing cycles. Specific
testers will be trained to use the tool for documenting tests statuses and defects during the testing cycle.
Test Director will also be used as a reporting tool on the testing progress and defect statuses.
Dated: 12-20-2002
6
Test Plan
APPO Sybase - Oracle Conversion
November 2002 – March 2003
VII.
Test Schedule
Test Activities
Test Director Training
Date
Dec. 16 – 31, 2002
(Training is up to 2 hours long.)
Test Cycle 1
Test Cycle 2
Customer Acceptance Testing
Jan. 6 - 24, 2003
Feb. 3 - 21, 2003
Mar. 2, 2003
VIII.
Risks/Contingencies
1. Risk: The Oracle test environment is not available at the start test cycle 1 could delay
testing and impact start date of conversion.
Contingencies:
a. Change date of conversion to a later date.
· This contingency may not be feasible if resources are not available to
test at the later date.
b. Have only one testing cycle instead of two.
· This contingency does not allow for enough time to fix and re-test
defects, in addition to completing the tests planned for in the test cycle.
c. Test only what is ready for testing in cycle 1. Make sure the complete set of
tests in cycle 2 is run.
2. Risk: The 1099 tax process in January 2003 could take more time than expected.
This issue would prevent or delay a tester from testing.
Contingency: A backup for the tester has been identified.
VII. Assumptions
1. By test cycle 2, the testers will be able to run through all their tests if all redevelopment was
not completed by test cycle 1.
2. APPO data warehouse will not be replicated after Feb. 28, 2003. Whether APPO gets
converted to Oracle or stays in Sybase, the data warehouse will be populated via nightly
process.
Dated: 12-20-2002
7
Test Plan
APPO Sybase - Oracle Conversion
November 2002 – March 2003
VIII.
Deliverables
Deliverable
1. Test Plan
2. Test Design
3. Defect Report
4. Test Cases
5. Customer Acceptance Criteria
6. Customer Acceptance Tests
7. Test Procedure
Due Date
12/31/02
12/31/02
12/31/02
12/31/02
12/31/02
2/1/03
Prior to each testing
Responsibility
APPO Test Team
APPO Test Team
IS
APPO Test Team
APPO Test Team
APPO Test Team
APPO Test Team
IX. Test Plan Approval
By signing here, you are approving the test plan for APPO Sybase-Oracle conversion.
Functional
Area
APPO
Manager
Date
Reviewed
_________________________________________________________
Purchasing Allan C. Breese, Director, Business and Facilities Maintenance Services
_________________________________________________________
Disbursements Kathy Hartelius, Manager, Disbursements Processing
IS
_________________________________________________________
Information Alex Corsello, Applications Manager
Systems
Dated: 12-20-2002
8