Master Test Plan Data Warehouse

15
Test Plan – Campus Community HRSA 7.6 Upgrade to 8.0 1. Introduction Campus Community encompasses person-level data that can be shared by all modules of HRSA. This includes biographic and demographic data, addresses and phones, relationships and emergency contacts for recruits, applicants, students, employees, and others. Additionally, it includes functionality for specific populations such as international students and visitors, and student athletes. Some elements defined by PeopleSoft as part of Campus Community will be covered by other functional areas for this upgrade. These elements include the 3Cs (communications, checklists, comments), service indicators, FERPA, and external organizations. They are outside the scope of this Campus Community test plan. 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 functional area test plan consists of the following: A. Test Roles and Responsibilities B. Items to be Tested C. Test Strategy D. Test Approach E. Deliverables F. Approval 1

Transcript of Master Test Plan Data Warehouse

Page 1: Master Test Plan Data Warehouse

Test Plan – Campus CommunityHRSA 7.6 Upgrade to 8.0

1. Introduction

Campus Community encompasses person-level data that can be shared by all modules of HRSA. This includes biographic and demographic data, addresses and phones, relationships and emergency contacts for recruits, applicants, students, employees, and others. Additionally, it includes functionality for specific populations such as international students and visitors, and student athletes.

Some elements defined by PeopleSoft as part of Campus Community will be covered by other functional areas for this upgrade. These elements include the 3Cs (communications, checklists, comments), service indicators, FERPA, and external organizations. They are outside the scope of this Campus Community test plan.

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 functional area test plan consists of the following:

A. Test Roles and ResponsibilitiesB. Items to be TestedC. Test StrategyD. Test ApproachE. DeliverablesF. Approval

1

Page 2: Master Test Plan Data Warehouse

Test Plan – Campus CommunityHRSA 7.6 Upgrade to 8.0

4. Test Roles and Resources

Role Responsibilities – related to testing

Test Designers: For many of the functional areas, this role will be held by the functional business analyst.Update names as needed

1. Admissions: Demetrius Cunia2. Benefits: Sue Bird3. Budget: Sara Harrington4. Campus Community: Eileen Quilty5. Financial Aid: Zack Kelley, Cheri McEntee,

Mel Uhlig6. GEMC Admissions & Graduate Awards:

Roland Shelton7. Human Resources: Colleen Strempel,

Deborah Gardner8. Law: Ron Nabewaniec9. Payroll: John Maiura10. Student Financials: Darnay Campbell, Mark

Clary, Steve Kelly, John Murlin11. Student Records: Steve Clark, Theresa

Fuller, Wendy Love, Nancy Prince12. University College: Peg Stearns13. Data Warehouse: Natalie Vincent 14. Load Testing: Ed Lester15. Security Testing: Key Security Contact for

the functional areas

Develop and document test design for data conversion, functional, lifecyle, 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.

Testers:Update names as needed

1. Admissions: Ken Schoening2. Benefits: Sue Bird3. Budget: Sara Harrington4. Campus Community: Eileen Quilty, Harry

Fleming, SCIS Representative5. Financial Aid: Cheri McEntee, Zack Kelley,

Connie Larocca, Mel Uhlig6. GEMC Admissions & Graduate Awards:

Shad Pulverenti7. Human Resources: Colleen Strempel,

Deborah Gardner8. Law: Ron Nabewaniec, Anikka

Laubenstein, Cheryl Ficcara, Gina Soliz9. Payroll: John Maiura, Jeremy McIntosh10. Student Financials: Anne Barker, Darnay

Campbell, Mark Clary, Steve Kelly, John Murlin, bursar personnel

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 Leads

2

Page 3: Master Test Plan Data Warehouse

Test Plan – Campus CommunityHRSA 7.6 Upgrade to 8.0

RoleResponsibilities – related to testing

11. Student Records: Steve Clark, Theresa Fuller, Wendy Love, Nancy Prince, registrar personnel

12. University College: Anne Barker13. Data Warehouse: Natalie Vincent,

Richard Bundy, Tom Bloss, Tom Sproull, Harry Fleming, and Key Brio Users

14. Load Testing: Ed Lester15. 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 Community3. Vivian Silliman for Student Financials,

Student Records4. Debbie Gardner, Linda Saul - Benefits,

Budget, Human Resources5. Linda Saul, Brian Pendergast - Payroll

Monitor and update project plan testing

activities by functional area.

Facilitate in the development of test plan,

test design and test cases for functional

and lifecycle testing.

Upgrade and Patch/Fix Technicians:

1. Mark Bostick2. John Bowden3. Dan Edwards

Prepare test databases used in the PS 8

upgrade

Communicate test environment readiness

to HRSAcore

Developers:

1. Admissions: Larry Roux2. 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 Stanley5. GEMC Graduate Awards: Mary Serrano6. GEMC Admissions: Bill Keesler, Larry Roux7. Student Financials: Marilyn Butler, Darlene

Kennedy8. Student Records: Bill Keesler, Steve

Wowelko

Perform unit test

Troubleshoot problems

Document problem updates in Test

Director

Communicate unit testing progress to test

lead

Work with Test Designers/testers on data

validation planning and testing efforts

3

Page 4: Master Test Plan Data Warehouse

Test Plan – Campus CommunityHRSA 7.6 Upgrade to 8.0

RoleResponsibilities – related to testing

Test Coordinator

Mimi Mark Develop master test plan

Prepare test materials (test guidelines,

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 cross functional area

testing

Redevelop automated tests for post

implementation

Work with Functional Project Managers on

test plan tasks.

Keep functional areas and PS 8 team leads

apprised of PS 8 testing activities.

4

Page 5: Master Test Plan Data Warehouse

Test Plan – Campus CommunityHRSA 7.6 Upgrade to 8.0

5. Items to be Tested

There should be tests developed for the list of items below. Details of the items to be tested should be provided in the test design document – a future deliverable.

A. Tests from the Functional Area

1. Data Validation Translate values Set-up tables Row counts for some tables Detailed review of specific cases (EMPLIDs to be determined) Detailed reviewed of components that are different in PS8, including:

Relationship between citizenship status and country of citizenship Separation of phone types from address types Addition of phone type ‘MAIN’ (validation will vary depending on whether

we decide to use MAIN)

2. Business Processes (Including Business Requirements and Business Rules) Search for a person online (by ID, name, national ID) Add person online Attempt to create emplid = ‘NEW’ online Update person online – name, addresses, phones, email, biographic data Change national ID online Try to add duplicate national ID online Maintain citizenship, visa and I20 data online Maintain athletic participation data online Validate a person’s data affiliations online Personal Portfolio tests (if this component is implemented) Manage national IDs for multiple countries (if this is implemented)

Many of the tests above can be defined in greater detail using our 7.6 regression tests as a starting point.

(3. Reporting

National ID (NID) audit - Brio against operational data Personal data audit - Brio against operational data

4. Batch Jobs SEVIS alerts Linked addresses update Campus housing purge Post OIS holds for new admits (if process is still needed)

5

Page 6: Master Test Plan Data Warehouse

Test Plan – Campus CommunityHRSA 7.6 Upgrade to 8.0

Purge OIS batch holds (if process is still needed)

5. Interfaces Post campus housing addresses and phones to HRSA from Housing, Meal Plans and

Special Purchases System (HMS) Post current (CURR) addresses to HRSA from ESF. Export file of I20 candidates from HRSA to SEVIS Download transaction file and I20 forms from SEVIS Load HMS with required HRSA data (scope is wider than just Campus Community

data) Load ID card system with required HRSA data (scope is wider than just Campus

Community data) Load library patron data from HRSA to library system (scope is wider than just

Campus Community data) Load Business Layers (BL) with required HRSA data (scope is wider than just

Campus Community data)

6. Boltons None

7. Cross Functional Areas Processes (Lifecycle Testing) Almost everything in CC is cross-functional. Need to determine if

anything deserves special emphasis here. I20 data entry and SEVIS alerts error resolution process (possible candidate)

8. Functional Area Key Process Performance (Timing Measurements) Online person search Online person add

B. Data Warehouse Testing SEVIS monitoring reports (yet to be defined).

C. Load Testing No Campus Community load testing is planned.

D. Security Testing

Change NID (function is tied to a specific security class) Demographic Data Access (DDA) testing (Still need to determine how we will

implement DDA here) Personal Portfolio security (if this component is implemented)

6

Page 7: Master Test Plan Data Warehouse

Test Plan – Campus CommunityHRSA 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 Phase

Role Description Examples

Data Validation

1,2,3 DeveloperTester

Validating the data converted to PS 8 database. This is done early on in the project.

7.6 Student data=8.0 Student data7.6 Employee data=8.0 Employee data

Unit 1 Developer Developer testing to validate that new code can be executed to completion with no errors.

Open panel, Add new record, Run sqr, etc.

Functional 1 Tester To validate the application meets business requirements under various scenarios for a functional area.

Add recruit, Update recruit, Add applicant existing already in HRSA, Run score load process, Generate report, etc.

Performance

1,2,3 Tester 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.

Enrollment, Admissions Application Entry, Batch Processing, Student Registering, etc.

Cross-Functional Process

2 Tester 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.

Cashnet (AD,SR, SF)ADSR

Load 2,3 IS - Ed Running key processes or activities under heavy usage simulation to determine if the application can perform adequately with high levels of activity/transactions.

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

Regression 3 Tester 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.

Acceptance

4 Tester Customer testing of the application for approval for production. This testing typically is not in-depth testing.

Login, Search, Navigating to panels, Running reports, etc.

Security 2 Key Security Contact

Testing security implemented in PS 8. Validate role access to PS 8, Permission lists

Data Warehouse (DW)

2,3 IS DW Tester

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

Running data stage and validating data move to data warehouse

7

Page 8: Master Test Plan Data Warehouse

Test Plan – Campus CommunityHRSA 7.6 Upgrade to 8.0

queries.

Automated 3 Test Coordinator

Run redeveloped automated tests

8

Page 9: Master Test Plan Data Warehouse

Test Plan – Campus CommunityHRSA 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: Jun’03 – Jan’04 (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: Feb’04 – mid-Apr’04

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

9

Page 10: Master Test Plan Data Warehouse

Test Plan – Campus CommunityHRSA 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 Reportingo Business processeso Batcho 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 Apr’04 – Aug’04)

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.

10

Page 11: Master Test Plan Data Warehouse

Test Plan – Campus CommunityHRSA 7.6 Upgrade to 8.0

8. Schedule

Test Activities Role Start Date

End Date

Create Master Test Plan Test Coordinator 4/2003 5/2003Create Functinal Test Plans Functional Business

Analyst5/2003 6/2003

Create Test Design Test Designer 5/2003 10/2003Create Test Cases Test Designer 6/2003 12/2003Phase 1 Testing Testers 6/2003 1/2004Phase 2 Testing Testers 2/2004 4/2004Phase 3 Testing Testers 4/2004 8/2004Redevelop Automated Test Cases Test Coordinator 1/2004 4/2004Create Customer Acceptance Criteria Test Coordinator 8/2004 8/2004Phase 4 - Customer Acceptance Testing

Testers 9/2004 9/2004

9. Deliverables

A. Functional Test Plan B. Functional Test Design C. Functional Test Cases

10. Test Plan Approval

By signing here, you are approving test plan for your functional area for the upgrade to HRSA 8.0.

Functional Area Manager Date Reviewed

______________________________________________[Type Functional Area Manager here. Mgr signs above the line]

11

Page 12: Master Test Plan Data Warehouse

Test Plan – Campus CommunityHRSA 7.6 Upgrade to 8.0

12