Test Plan - Final

HRSA 7.6 Upgrade to 8.0

1. Introduction............................................................................................................................................2 2. Purpose.................................................................................................................................................2 3. Components..........................................................................................................................................2 4. Test Roles and Responsibilities.............................................................................................................3 5. Items to be Tested.................................................................................................................................5 6. Test Strategy.........................................................................................................................................8 7. Test Approach.....................................................................................................................................10 8. Test Environment - Database Update Process from HRSA 7.6 to 8.0.................................................12 9. Tools....................................................................................................................................................12 10. Schedule ..........................................................................................................................................13 11. Deliverables.......................................................................................................................................13 12. Risks/Contingencies.........................................................................................................................13 13. Assumptions......................................................................................................................................14 14. Test Plan Approval.............................................................................................................................14

Revised: 5/21/03

Test Plan - Final

HRSA 7.6 Upgrade to 8.0

1. Introduction Human Resources and Student Administration (HRSA) system is a PeopleSoft system which has modules for administering employee/faculty/student data and activities. The functional areas that use HRSA and will be testing the upgrade to 8.0 are Admissions, Benefits, Campus Community, Financial Aid, Budget, Graduate Enrollment Management Center(GEMC), Human Resources, Law, Payroll, Student Financials, Student Records, and University College. 2. Purpose The purpose of the test plan is to ensure the upgrade from HRSA 7.6 to 8.0, which includes a data conversion, is thoroughly tested, resulting in a successful implementation of new and existing functionality, business processes, reports, interfaces, and batch processes. 3. Components The test plan consists of the following: A. B. C. D. E. F. G. H. I. J. K. Test Roles and Responsibilities Items to be Tested Test Strategy Test Approach Test Environment Test Tool Test Schedule Deliverables Risks/Contingencies Assumptions Approval

Revised: 5/21/03

Test Plan - Final

HRSA 7.6 Upgrade to 8.0

4. Test Roles and Responsibilities

Role Test Designers: For many of the functional areas, this role will be held by the functional business analyst. 1. 2. 3. 4. 5. Admissions: Demetrius Cunia Benefits: Sue Bird Budget: Sara Harrington Campus Community: Eileen Quilty Financial Aid: Cheri McEntee, Zack Kelley, Mel Uhlig 6. GEMC Admissions & Graduate Awards: Roland Shelton 7. Human Resources: Colleen Strempel, Deborah Gardner 8. Law: Ron Nabewaniec 9. Payroll: John Maiura 10. Student Financials: Darnay Campbell, Mark Clary, Steve Kelly, John Murlin 11. Student Records: Steve Clark, Theresa Fuller, Wendy Love, Nancy Prince 12. University College: Peg Stearns 13. Data Warehouse: Natalie Vincent 14. Load Testing: Ed Lester 15. Security Testing: Key Security Contact for the functional areas Testers: 1. 2. 3. 4. 5. Admissions: Ken Schoening Benefits: Sue Bird Budget: Sara Harrington Campus Community: Eileen Quilty Financial Aid: Cheri McEntee, Zack Kelley, Mel Uhlig, Connie Larocca 6. GEMC Admissions & Graduate Awards: Shad Pulverenti 7. Human Resources: Colleen Strempel, Deborah Gardner 8. Law: Ron Nabewaniec 9. Payroll: John Maiura, Jeremy McIntosh 10. Student Financials: Anne Barker, Darnay Campbell, Mark Clary, Steve Kelly, John Murlin, bursar personnel 11. Student Records: Steve Clark, Theresa Fuller, Wendy Love, Nancy Prince, registrar personnel 12. University College: Anne Barker Run test cases during designated test periods Document test results and problems in Test Director Work with developers in troubleshooting problems. Re-test problem fixes Communicate test updates to Test Designers Responsibilities related to testing

Develop and document test design for data validation, functional, crossfunctional process, security, and performance testing Create and document test cases based on test design Coordinate testing activities within own functional area Communicate test updates to Test Coordinator and Functional Project Managers

Revised: 5/21/03

Test Plan - Final

HRSA 7.6 Upgrade to 8.0
Role 13. Data Warehouse: Natalie Vincent, Richard Bundy, Tom Bloss, Tom Sproull, Harry Fleming, and Key Brio Users 14. Load Testing: Ed Lester 15. Security Testing: Key Security Contacts Functional Project Managers: Cindy Hoalcraft is the functional project lead who will be managing the functional project managers. 1. David Harris - Admissions, Financial Aid, GEMC 2. Cindy Hoalcraft - Campus Community 3. Vivian Silliman - Student Financials, Student Records 4. Debbie Gardner, Linda Saul - Benefits, Budget, Human Resources 5. Linda Saul, Brian Pendergast - Payroll Upgrade and Patch/Fix Technicians: 1. Mark Bostick 2. John Bowden 3. Dan Edwards Developers: 1. Admissions: Larry Roux 2. Benefits, Budget, Human Resources, Payroll: , Ray Brunner, Patty Bergin, Pat Cabrey, Scott LaPar, Stephanie Chiaravalloti, Jeff Bedell - consulting only. 3. Campus Community: Harry Fleming, Larry Roux 4. Financial Aid: Tom Bloss, Pat Stanley 5. GEMC Graduate Awards: Mary Serrano 6. GEMC Admissions: Bill Keesler, Larry Roux 7. Student Financials: Marilyn Butler, Darlene Kennedy 8. Student Records: Bill Keesler, Steve Wowelko Test Coordinator Mimi Mark Develop master test plan Prepare test materials (test guidelines, Perform unit test Troubleshoot problems Document problem updates in Test Director Communicate unit testing progress to Test Designer Work with Test Designers/testers on data validation planning and testing efforts Prepare test databases used in the PS 8 upgrade Communicate test environment readiness to HRSAcore Monitor and update project plan test activities by functional area. Facilitate in the development of the functional areas test plan, test design and test cases. Responsibilities related to testing

Revised: 5/21/03

Test Plan - Final

HRSA 7.6 Upgrade to 8.0
Role Responsibilities related to testing procedures, templates) for functional areas use Setup test and defect reporting Setup Test Director for PS 8 testing effort Monitor test planning progress and execution efforts Facilitate and coordinate the development and execution of crossfunctional area testing Redevelop automated tests for regression testing Work with Functional Project Managers on test plan tasks. Keep functional areas and PS 8 team leads apprised of PS 8 testing activities.

5. Items to be Tested The functional project managers, who are also process and business analysts, will be essential in assisting the functional areas (Test Designers) to identify business processes, activities, and scenarios components of the test design. The details of the items to be tested will be provided in the test design document a future deliverable. A. Each functional areas Test Designer should identify, document, and test the following: 1. Data Validation The data validation is to make sure that no data was lost or corrupted in the data conversion to PS 8. This testing should be completed early in the upgrade project. Subsequent testing in later test phases would need to occur but to a lesser degree. List differences (i.e. table, field) between HRSA 7.6 and 8.0 database components to validate. The IS developers and the Test Designer will need to work together to plan a list of data items to validate. Generate reports used to check the converted data. The reports need to be generated prior to the conversion.

2. Business Processes (Including Business Requirements and Business Rules) Revised: 5/21/03 5

Test Plan - Final

HRSA 7.6 Upgrade to 8.0

List business processes Identify activities performed for each business process Develop scenarios that can take place in the activity Create a test for each scenario

3. Reporting Queries against production database (BRIO, PS Query, reports run through PS Navigator, Crystal) Queries against data warehouse (BRIO) 4. Batch Jobs

Incoming to HRSA Outgoing from HRSA

5. Interfaces Incoming to HRSA (i.e. Data Feeds, Housing) Outgoing from HRSA (i.e. Data Feeds, Housing, Library, Health Services) 6. Bolt-Ons 7. Cross-Functional Area Processes Functional areas using common data will need to work together to determine what tests will be needed. Test dependencies, coordination, and timing of specific tests will be important details to be aware. Both the test coordinator and project manager will facilitate the discussion. 8. Functional Area Key Process Performance (Timing Measurements)

List key processes where the applications performance is important. Develop baseline times for key processes. Use timings from key processes in HRSA 7.6 production to compare with times taken in 8.0.

B. Data Warehouse Testing Data warehouse testing effort will be led by IS Data Warehouse group. The testing will be performed by IS Data warehouse staff and users of the data warehouse. There will be internal IS data warehouse testing. Testers will be expected to validate their Brio queries. Data warehouse testing communications will come from the IS Data Warehouse group. C. Load Testing Listed below are some business activities load tested in the past. The activities are run through a variety of scenarios to determine how well the application performs under heavy usage.

Revised: 5/21/03

Test Plan - Final

HRSA 7.6 Upgrade to 8.0

1. Payroll Process 2. Weekly Timekeeping 3. On-line Student Registration

If a functional area has a process or activity that should be load tested, the Test Designer should document the load test in the test design document. Both IS and the functional area will need to work together on the load test preparation. The actual execution of the load test will be handled by IS.

D. Security Testing The security testing is led by the functional area key security contacts (KSC). The KSCs should ensure that users are assigned the access needed to perform their job. This testing may include validating 1. 2. 3. 4. Functional areas roles Permission lists Query capabilities Table/View access

in addition to any other items that the KSC identifies for testing. IS Security will be available to help facilitate in the test design, as needed.

Revised: 5/21/03

Test Plan - Final

HRSA 7.6 Upgrade to 8.0

6. Test Strategy Listed below are the various types of testing that will take place in four test phases.
Testing Data Validation Unit Functional Phas 1,2,3 Role Developer Tester Developer Tester Description Validating the data converted to PS 8 database. This is done early on in the project. Developer testing to validate that new code can be executed to completion with no errors. To validate the application meets business requirements under various scenarios for a functional area. Measuring the time an activity or key process takes to complete. This testing should be done throughout the test phases. Timings from HRSA 7.6 production should be used as the benchmark for PS 8 timings. Cross-functional process testing to validate the application works across functional areas or other applications (into or out of HRSA). Included in this testing are any interfaces from or into HRSA. Running key processes or activities under heavy usage simulation to determine if the application can perform adequately with high levels of activity/transactions. Regression testing to validate PS 8 patch and reg updates. By this time, there should be minimal application changes except for PS 8 patch and reg updates. Customer testing of the application for approval for production. This testing typically is not in-depth testing. Testing security implemented in PS 8. Testing to validate changes to DW. This would involve IS DW testing the DW data stage jobs in the conversion and the testers validating the repository queries. Run redeveloped automated tests Login, Search, Navigating to panels, Running reports, etc. Validate role access to PS 8, Permission lists Running data stage and validating data move to data warehouse Examples 7.6 Student data=8.0 Student data 7.6 Employee data=8.0 Employee data Open panel, Add new record, Run sqr, etc. Add recruit, Update recruit, Add applicant existing already in HRSA, Run score load process, Generate report, etc. Enrollment, Admissions Application Entry, Batch Processing, Student Registering, etc.

1 1

Performan ce

1,2,3

Tester

CrossFunctional Process

Tester

Cashnet (AD,SR, SF) ADSR

Load

2,3

IS - Ed

Running simultaneously the payroll process, weekly timesheets, and 700 users for on-line registration

Regression

Tester

Acceptanc e Security Data Warehous e (DW) Automated

Tester

2 2,3

Key Security Contact IS DW Tester

Test

Revised: 5/21/03

Test Plan - Final

HRSA 7.6 Upgrade to 8.0
Coordinat or

Revised: 5/21/03

Test Plan - Final

HRSA 7.6 Upgrade to 8.0

7. Test Approach The four test phases are based on the development schedule for PS 8 upgrade project along with the requirement to comply with financial aid regulation updates that need to be in place when the upgrade goes live. Phase 1: Jun03 Jan04 (Note Test cases should be completed by end of 2003)

Data Validation Performance Unit Functional Data Warehouse (internal testing within IS validating data stage jobs)

Data validation should start early in the test process and be completed before phase 2 testing begins. Some data validation testing should occur in the remaining test phases, but to a much lesser extent. Important business processes where performance is important should be identified and tested (when available) in the phase 1. Performance times in HRSA 7.6 should be used as benchmarks to determine if the performance in the PS 8.0 is within benchmarked range. Performance testing should be continued in the later test phases as the application will be continuously enhanced throughout the project. In addition to phase 1 testing, there will also be unit and functional testing. As unit testing is completed for a program, the tester will perform functional tests on the program. While functional testing takes place with one program, the developer continues with redeveloping and unit testing the next program. Toward the end of phase 1, the data warehouse group will be testing the data stage jobs. Redevelopment and unit testing should be completed by end of 2003 with functional testing finishing a couple weeks afterwards. A final formal test will cap the end of phase 1 testing. Phase 2: Feb04 mid-Apr04

Cross-functional process Load Security Data Warehouse (Repository testing and validation)

Revised: 5/21/03

10

Test Plan - Final

HRSA 7.6 Upgrade to 8.0
In addition to the above tests, phase 2 should also cover remaining test items that may not been tested in phase 1 such as:

o o o o

Reporting Business processes Batch Bolt-Ons

Phase 2 testing will be important because it is the final testing opportunity that IS and the functional area testers will have to make sure PS 8 works as expected before moving to regression testing in phase 3. Some performance tests and data validation should be be included in this phase. A final formal test will cap the end of phase 2 testing. Phase 3: (end of Apr04 Aug04)

Regression

Phase 3 testing is comprised of three regression test periods to test PS 8 update patches and regs that are required as part of the Go-Live system in September 2004. The functional area testers will have two weeks to test in each regression test period. Phase 4: (Sept. 28, 2004)

Customer Acceptance

Phase 4 testing is limited to one day. In addition to the functional area testers, end users will probably be involved in this final test before the system goes live. In customer acceptance testing, no new tests should be introduced at this time. Customer acceptance tests should have already been tested in prior test phases.

Revised: 5/21/03

11

Test Plan - Final

HRSA 7.6 Upgrade to 8.0

8. Test Environment - Database Update Process from HRSA 7.6 to 8.0

Diagram was provided by Erik Anderson. Note, over time, the diagram will be modified.

DB50027 7.6 Prod

Mast is frozen from the time the tools are exported and to the time it is refreshed.

DB000xx Mast

DB000xx SA8PROTO

ple eo tP or xp E

ol To

Migrate Patches (.5)

( s. le ab sT

Make Security Changes

Copy to DB00027 (1)

1)

Approved Customizations (.5)

7 Upgrade Database Tools Upgrade (2) 13

.3 )

Re f

DB00027 9 Upgrade Database Data Conversion (12) Copy to DB00032 (1)

re

sh

DB00033 RT Testing (2)

Secu rity sa ved o ut

Securit y

13
before refres h. (.5) 15
refres h. (.5 )

as

t(

Customizations For Testing (.5)

copied back in afte r the

13
sh RT (.3 )

Migrate Patches (.5)

DB000xx Safe

10

fre Re

Export tools tables from DB00032 when this is not a patch move

13 Refresh DEV (.4) DB00032 11 Finish Upgrade / Cleanup (3) 3

12 be ) ut (. 5 do h. ve es sa efr re er a th ns er 14 ti o a ft za in mi ck sto ba d Cu p ie co re t. a us C

) (.5 h. es efr er for

DB00031 Dev Migrate Patches to Dev (1) Develop patch fixes (2) 2

DB00013 VAN

Apply Patches (1) 1

9. Tools A. Test Director will be used by 1. Test coordinator to monitor test development, testing progress, and defect reporting. 2. Test Designers to document tests. 3. Testers to run tests and report defects. 4. Developers to review and update defects. B. Load Runner will be used by IS to run the load tests

Revised: 5/21/03

12

Test Plan - Final

HRSA 7.6 Upgrade to 8.0

10. Schedule Test Activities Create Master Test Plan Create Test Design Create Test Cases Phase 1 Testing Phase 2 Testing Phase 3 Testing Redevelop Automated Test Cases Create Customer Acceptance Criteria Phase 4 - Customer Acceptance Testing Start Date 4/2003 5/2003 6/2003 6/2003 2/2004 4/2004 1/2004 8/2004 9/2004 End Date 5/2003 10/2003 12/2003 1/2004 4/2004 8/2004 4/2004 8/2004 9/2004

11. Deliverables Deliverable A. B. C. D. E. F. G. H. I. J. Master Test Plan Functional Area Test Plan Functional Area Test Design Functional Area Test Cases Phase 1 Testing Completed Phase 2 Testing Completed Redeveloped Automated Tests Phase 3 Testing Completed Customer Acceptance Criteria Phase 4 Testing Completed Completion Date 5/15/03 6/30/03 10/31/03 12/31/03 1/30/04 4/16/04 4/30/04 8/20/04 8/31/04 9/28/04 Responsibility Test Coordinator Functional Area Project Manager Test Designer Test Designer Testers Testers, IS Test Coordinator Testers, Test Coordinator Test Coordinator Testers

12. Risks/Contingencies 1. Risk: Redevelopment is not completed on schedule. Impact: Testing is delayed and not completed on time. Contingency 1: The projects progress will be continually monitored. If the project schedule becomes a concern, appropiate action will be taken at the time to keep the project on schedule. Contingency 2: Shorten test phases. 2. Risk: Testing personnel shortage Impact: Testing the upgrade to PS 8 may suffer.

Revised: 5/21/03

13

Test Plan - Final

HRSA 7.6 Upgrade to 8.0
Contingency: Train a backup tester. 3. Risk: Not enough time to test Impact: Testing the upgrade to PS 8 may suffer. Contingency: Prioritize testing to ensure application functionality works for critical and major business processes. 13. Assumptions 1. Redevelopment will be completed on schedule allowing functional testing to be completed in 1/2004 2. Testing effort will have adequate resources. 3. Production equipment/software will be delivered and set up on time. 14. Test Plan Approval By signing here, you are approving the test plan for the upgrade to HRSA 8.0. Functional Project Managers ______________________________________________ David Harris for Admissions, Financial Aid, GEMC ______________________________________________ Cindy Hoalcraft for Campus Community ______________________________________________ Vivian Silliman for Student Financials, Student Records ______________________________________________ Deborah Gardner for Benefits, Budget, Human Resources ______________________________________________ Brian Pendergast for Payroll Functional Project Lead ______________________________________________ Cindy Hoalcraft Technical Project Lead ______________________________________________ Erik Anderson Date Reviewed Date Reviewed Date Reviewed

Revised: 5/21/03

14