Contact us

To find out more about testing, email greatservice@imperial.ac.uk.

The implementation of a new system is a complex and high-risk process. Therefore, it is important to rigorously test each element of the new system throughout the project lifecycle to ensure that it meets business requirements, is fit for purpose and to avoid potential failure. Testing validates that all components of the new system, including integrations with other systems, work together as an end-to-end solution before go live. Testing is not just a technical step, it is a critical safeguard for success.

Why is testing important?

Assures quality

Validates that the new system meets design and business requirements.

Builds confidence

Gives users trust in the system before go live.

Ensures compliance

Verifies that the system meets data protection and security standards.

Prepares for transition to business as usual

Confirms performance and operational readiness.

Reduces risk

Catches defects early before they impact operations.

Types of testing

The Great Service Programme has an extensive testing plan which will include the following types of testing:

Types of testing

Unit/Component Testing

This involves performing tests on individual components or modules within the system to confirm if they function correctly in isolation from the rest of the system. This will verify that each piece of code or configuration behaves as expected based on the predefined requirements and design specifications.

System Testing

This involves validating the working stability of the configured and developed components within the larger end-to-end system and assesses how these elements operate together in a more integrated environment.

System Regression Testing

This is conducted on critical functional elements of the solution that have previously passed System Testing. This testing focuses on confirming the stability of the system by ensuring that recent changes, such as defect fixes, project changes, or base product upgrades, do not adversely impact the broader functionality.

System Integration Testing

This is conducted on business approved system designs and focuses on functionality and end-to-end integration and processes within a realistic testing environment that simulates real-world scenarios. This will help to identify and address any issues that may arise from the interaction of different components.

User Acceptance Testing

This marks the final stage of business assurance testing and is carried out by Imperial’s wider business teams. While System Integration Testing (SIT) focuses on validating end-to-end business processes across the numerous integrations delivered by the Great Service Programme, UAT provides business teams with hands-on access to the system for a comprehensive review of all key business functions delivered by the programme.

Faculties and central departments will be required to take part in User Acceptance Testing and try out real Imperial scenarios to make sure the system works in preparation for go live.

Our UAT resource plan has been approved by the Great Service Board and we can confirm:

  • We need a minimum equivalent of 29 full time equivalents (FTE) for 12 weeks – this does not mean we need all testers full-time for this period, times and commitment will vary depending on the test scenarios.
    - 14 Human Capital Management - such as recruitment, absences, payroll
    - 12 Enterprise Resource Planning - such as accounts, procurement, expenses
    - 3 Enterprise Performance Management - Non-Research Projects and Research Projects & Worktribe
    - The estimates for Projects and Portfolio Management still to be confirmed
  • We recommend this as a guideline and additional capacity is provided from a process perspective for each department
  • UAT training will take place in February
  • UAT will run from March to May 

We will work closely with our senior leaders to source testers and consider nominations carefully as they will be there to act as assurance the system works as it should, for your area.

All nominations for UAT should come through leadership teams only, so speak to your manager in the first instance.

Parallel Payroll Run(s)

Parallel testing is a critical process designed to ensure that payroll calculations are accurately performed by the new system. This method involves running the new system alongside the existing system to compare results and verify accuracy.

Security Testing

Security Testing is the practice of rigorously testing a computer system, network, or web application to identify vulnerabilities that could be exploited by attackers. This process primarily involves scanning the system and its associated infrastructure to ensure that appropriate security patches and controls are in place. 

Performance Testing

This type of testing focuses on evaluating the speed and performance of the system, ensuring that processes operate efficiently and meet pre-defined time criteria. Additionally, it simulates peak and prolonged user loads to determine whether the infrastructure and solution can maintain performance without negatively affecting the end-user experience.

Operational Acceptance Testing

This is a crucial process designed to ensure that the system and infrastructure are operationally ready for deployment and is conducted after UAT as an entry criteria into cutover preparation. It also confirms that the necessary support services and security approvals are in place.