Unit Testing / Confirmation Sessions
Unit Testing is the first round of testing and is meant to review and test each individual configuration component to ensure that each unit performs its assigned function independently of the other units. It serves as a basic check that the configuration conforms to design requirements.
End-to-end Testing (E2E)
The purpose of end-to-end testing is to ensure the proper flow of processes between multiple functions, integrations, and downstream systems. It is designed to verify the system functions as designed, to continue verification of the converted data, and to verify the results of processes run in Workday to downstream systems and vendors.
- Cycle 1: Run through all End-to-end test scenarios to ensure system is working to business requirements.
- Cycle 2: Re-run through any changes made during Cycle 1 to ensure they do not adversely impact the parts of the system that are not changing. This phase is to verify the deployed configurations, security, business processes, and integrations continue to behave as expected.
User Acceptance Testing (UAT)
User Acceptance Testing is designed to confirm that Workday is not only working properly, but that Brandeis’s subject matter experts are confident in their ability to perform their daily tasks using Workday and can explain the system to general end users. By this stage of testing activities, all processes should be stable and the Brandeis team should be fully leading first-level issue triage. Payroll and integrations are not included as part of User Acceptance Testing.
Parallel Testing helps ensure that the payroll processes and integrations are correctly in Workday match the same results found in PeopleSoft. Any differences in results between the two systems must be identified and explained. The Brandeis Parallel Testing team will include HCM, integrations, and payroll staff. All the Brandeis resources who will have an active role in entering, processing, sending, and validating payroll-related data and inputs once the Brandeis is in production should participate in Parallel testing by leading and performing those same functions with Collaborative Solutions as support during test. Supporting resources from the Brandeis HRIS group should also be available to assist in entering catch-up transactions and any other HCM data entry as required.
Rolling Data Validation
As each load is performed Brandeis functional teams will review their specific segment of data for each load. This will be done by reviewing the data visually in the tenant and can be further evaluated by creating audit reports for the specific data elements.