QA Process Setup and Ongoing Testing for Mobile Game Development Studio
Challenge
The client is a UK-based company developing interactive VR training simulations for higher education and healthcare students. The platform uses immersive experiences to teach soft skills such as communication, employability, and leadership across desktop and VR environments.
The company was preparing a new version of its training simulation and needed manual QA support during the Beta and Gold stages. The testing scope focused on script-to-screen accuracy, avatar and animation behavior, voice prompts, gaze direction tracking, and closed captions.
The project had a tight timeline, with less than three weeks between the Beta and Gold stages. Testing also required coordination across Jira, TestRail, and Slack, while VR testing had to be planned separately because of device availability and its lower priority. The client therefore needed a QA engineer who could quickly integrate into the workflow and provide focused testing within the agreed release schedule.
The client is a UK-based company developing interactive VR training simulations for higher education and healthcare students. The platform uses immersive experiences to teach soft skills such as communication, employability, and leadership across desktop and VR environments.
The company was preparing a new version of its training simulation and needed manual QA support during the Beta and Gold stages. The testing scope focused on script-to-screen accuracy, avatar and animation behavior, voice prompts, gaze direction tracking, and closed captions.
The project had a tight timeline, with less than three weeks between the Beta and Gold stages. Testing also required coordination across Jira, TestRail, and Slack, while VR testing had to be planned separately because of device availability and its lower priority. The client therefore needed a QA engineer who could quickly integrate into the workflow and provide focused testing within the agreed release schedule.
Solution
QA Madness provided a manual QA engineer who joined the project during the Beta stage and worked within the client’s existing development workflow. The initial scope was focused on the desktop version of the simulation, while VR testing on Meta Quest 2 was treated as a secondary priority. Areas such as accessibility, login, profile management, menus, settings, and debug features were excluded according to the client’s requirements.
The QA engineer established a shared communication channel in Slack and integrated with the client’s Jira and TestRail workflow. The team received access to the relevant testing documentation, builds, and training scripts and followed the agreed testing schedule for both Beta and Gold builds.
Testing focused on functional behavior, UI elements, compatibility, and the accuracy of the simulation against the provided training scripts. QA engineers checked visual alignment, functional issues, avatar and voice behavior, and other discrepancies, reporting defects in real time with the necessary details and supporting materials. The primary testing environment was a Windows PC, with VR testing planned as needed.
QA Madness provided a manual QA engineer who joined the project during the Beta stage and worked within the client’s existing development workflow. The initial scope was focused on the desktop version of the simulation, while VR testing on Meta Quest 2 was treated as a secondary priority. Areas such as accessibility, login, profile management, menus, settings, and debug features were excluded according to the client’s requirements.
The QA engineer established a shared communication channel in Slack and integrated with the client’s Jira and TestRail workflow. The team received access to the relevant testing documentation, builds, and training scripts and followed the agreed testing schedule for both Beta and Gold builds.
Testing focused on functional behavior, UI elements, compatibility, and the accuracy of the simulation against the provided training scripts. QA engineers checked visual alignment, functional issues, avatar and voice behavior, and other discrepancies, reporting defects in real time with the necessary details and supporting materials. The primary testing environment was a Windows PC, with VR testing planned as needed.
Results
QA Madness successfully completed the full manual testing cycle within the agreed timeline, allowing the client to proceed with its planned release schedule without delays. Testing covered both the Beta and Gold stages and focused on the areas most important to the simulation’s functionality and training experience.
More than 25 issues were identified and logged across the two testing stages. Each defect was documented with reproduction steps, severity classification, and multimedia files, providing the client’s team with actionable information for addressing the identified problems.
The QA process was smoothly integrated into the client’s existing workflow through coordinated use of Slack, Jira, and TestRail. The client provided positive feedback on the testing coverage, defect reporting, communication, and proactive status updates, confirming the effectiveness of the QA support during the release cycle.
QA Madness successfully completed the full manual testing cycle within the agreed timeline, allowing the client to proceed with its planned release schedule without delays. Testing covered both the Beta and Gold stages and focused on the areas most important to the simulation’s functionality and training experience.
More than 25 issues were identified and logged across the two testing stages. Each defect was documented with reproduction steps, severity classification, and multimedia files, providing the client’s team with actionable information for addressing the identified problems.
The QA process was smoothly integrated into the client’s existing workflow through coordinated use of Slack, Jira, and TestRail. The client provided positive feedback on the testing coverage, defect reporting, communication, and proactive status updates, confirming the effectiveness of the QA support during the release cycle.