Purpose of This Article

Once your Environment has been configured in line with the agreed configuration requirements decided in the Refine stage. It is essential that the environment is tested thoroughly to ensure that it is functioning as expected. Doing this ensures that there are no surprises when your deployment goes live. This article outlines how your team should approach testing and what checks to perform. Treating this as a high-priority task will help keep your project on track.

Overview of the Testing Process

The testing process will be led by our team, who will guide you through each stage. You will need to nominate a group of testers—ideally users who are familiar with your existing system and who are familiar with your current business process.

Who Should Be Involved in Testing

We recommend involving individuals from your organization who will actively use Mercury. Ideal participants include:

• Recruitment Managers
• Recruiters
• Administrators

Their insights and feedback are crucial in ensuring Mercury’s configuration aligns with your operational needs and delivers the expected value.

What to Test

Although our team will guide you through the process of Testing, it is important to keep in mind the following three key areas when testing, they are as follows:
Functional Validation: Confirm that all features and workflows operate correctly and efficiently according to your recruitment needs.
Usability Assessment: Evaluate the software's user interface, navigation, and overall user experience.
Integration Testing: Ensure seamless integration with any existing systems or platforms used within your recruitment processes, within agreed scope.
 

How to Test

Mercury best practices mean that when testing, this will be done so in a Test environment so not to interfere with any production settings and configurations. You will be granted access to the relevant testing environment where you can interact with the software using test accounts and data.
You will then be guided through executing predefined test scenarios covering essential workflows such as job posting, candidate management, reporting, and integration points (e.g., with timesheet systems) as well as encouraged to freely explore the software to simulate real-world usage scenarios based on your recruitment processes.

How to Provide Feedback

What Happens Next

Once testing is complete, we will provide a summary of all proposed changes. We’ll confirm which can be included within the project scope and identify any that may be chargeable or deferred until after Go-Live due to time constraints.
If you have any questions during the testing process, please reach out to your Mercury Project Manager.