The goal is simple: test everything!
The testing phase involves three types of tests. At this point, everything needs to be tested: Workday configurations, business processes, workflows, data, integrations, reports, security and all functionalities (Finance, HR, and common). No aspect can be taken for granted.
- End-to-end testing. Based on predefined scenarios, the business processes will be tested from start to finish. We test everything: the common functionalities, along with those specific to finance and HR, integrations with third parties, and interconnected systems. These tests will be broken down into three cycles and run from June to September 2022.
- Parallel testing for payroll processing. Over the same time period, we will run payroll processing simulations in both Workday and Banner, and compare the results to confirm compliance. These tests, which will be spread out over two cycles, will take place in October and November 2022.
- University user acceptance testing. University users who are not members of the project team will check that the solution meets their business needs. These tests will examine security measures and business processes. This is also when we will evaluate training materials and documentation. This third, and final, testing phase will take place in November and December 2022.
Already in the testing phase?
Yup! Remember that the previous phase, involving configuration and prototyping, took place from December 2021 to May 2022. During this time, the project team produced and tested two Workday prototypes. This important step allowed us to evaluate and confirm or revisit the decisions taken during the design phase.
After creating the first prototype, the project team conducted various tests from user and administrator accounts. In light of the results, and in consultation with the faculties and services, the team refined the second prototype. Creating these prototypes allowed the team to understand how the new system would affect processes, what changes to make and what new processes to adopt, and how to adjust the final prototype, which will be used for end-to-end testing.