Test Cycle Overview. ucpathproject.ucop.edu/

Transcription

1 Test Cycle Overview

2 Functional Unit Test (FUT) System Test (ST) 2 Iterations Integration Test (IT) 1 Iteration: File and Web Service Integration (Tier 1) Full Integration (Tier 2) User Acceptance Test (UAT) 1 Iteration OAT (Operational Acceptance Test) Location UCPath Delta Development Location UCPath New TAM and eperformance ST1 Changes to Existing CEMLIs (15 CRs) and Location Tier 1 and 2, DDODS, Vendor, Corporate Systems Location <-> UCPath Interface Test: Interfaces & Monitoring Tools Payroll Parallel Test Performance Test Remediation Location <-> New CEMLIs (4) Location <-> UCPath UCPath End-to-End Integration Test: Kick the tires ST2 Business Processes, Review HCM Batch Processing (PCSSC), Operational Individual Location Security Roles/Row Processes CEMLI s System & Tests Web Services 2

3 System Test (ST) Integration Test (IT) File and Web Service Integration (Tier 1) Full Integration (Tier 2) System Test includes the following for new D1 CEMLIs and change requests: Product confirmation of module functions Identification of requirement gaps Validation of standalone inbound and outbound interfaces (including vendor interfaces) Confirmation of system modifications, extensions and workflow Verification of the flow of information within applications Authentication of technical usability Validation of security roles Open defects/change requests Integration Testing includes the following: Interface configuration Inbound and outbound interfaces and web services New reports or existing reports used in IF Security role and row level validation Negative and boundary testing Integration Testing has the following attributes: Executes using production converted data Passes data to vendors for validation Includes D1 data in the conversion Includes business processes, systems, and communications across the UCPath Center, CoE support, hosting service provider, UC Berkeley PCSSC and deploying locations. 3

4 Payroll Parallel Test (PPT) Compare a payroll run in UCPath to a PPS payroll (legacy system) from a specific point in time and pay period. Comparison includes: Checks, Earnings, Taxes, General Deductions, Benefit Deductions, Garnishments Results are compared and variances identified, fixed, accepted and/or communicated. Validate the impacted payroll converted data, configuration, and UCPath payroll solution. Increase confidence in accuracy at the point of go-live. Locations supply time files in I-181 format and should be produced from their timekeeping system for prior pay periods (based on PPT snapshot dates). This requires format mapping from existing time system to I-181 format. In general, PPT covers a prior Bi-Weekly & Monthly pay period and time files are required from locations. User Acceptance Test (UAT) OAT (Operational Acceptance Test) Kick the tires concept Focuses on Employee Self Service and Manager Self Service Locations include additional users (not the same testers from IT) Refinement of Business Practices to incorporate Path Center hand-offs and operational test cases Path Center will define test scenarios with locations during Operational Alignment sessions Reuse of test cases from IT is dependent on the locations 4

5 PPT v. IT Payroll Parallel Testing is: Comparison of UCPath converted data payroll to PPS payroll for full monthly and bi-weekly population Instrument to identify UCPath system defects resulting in a variance in pay (logged in TnT Jira) Mechanism to identify acceptable variances between UCPath and PPS resulting in a variance in pay (logged Known Variances, identified for potential communication or training) Payroll Parallel Testing is not: User training on payroll User acceptance testing Transaction testing for Benefits/HR Functional or end-to-end testing of business processes Conversion data accuracy or reconciliation to PPS is not critical for Integration Test. ucpath.universityofcalifornia.edu/ 5