skip to main content

Summary

This module will help you formally test your game using criteria developed from the scoring rubric.

a young man sitting on chair wearing headphones and using a laptop

Documents used in this module

Before you start

Before starting these activities, it is recommended that you have:

  • Completed enough of your game for it to be play-tested for the first time (Modules 5, 6 and 7)
  • Accessed the Alpha testing checklist.

Tasks

What is alpha testing?

Alpha testing is the first stage of game testing where the game's functionality is evaluated. It is typical for game developers to conduct alpha testing before the game is shared with other users.

The purpose of alpha testing is to identify bugs, glitches, and other issues related to the game's core mechanics, design, and overall performance. At this stage, your game may not have all the elements finished, and some parts might still be in development.

The focus of alpha testing is on stability, ensuring the game doesn't crash or face major bugs. The process often leads to revisions or updates. Alpha testing is iterative: multiple alpha versions may be tested before the game moves to the beta testing phase, which involves a broader audience.

When conducting alpha testing, it is important to be honest. If the game has bugs, or it doesn’t work as expected, you should recognise and fix these issues before sharing your game with others.

What can I use to check my game?

    The judges for the STEM VGC will evaluate your game using the Scoring Rubric. Each criterion in this rubric is broken down into five levels of performance (from one star to five stars), and explicit written descriptions are provided for each level. This approach ensures that your game is judged on various important aspects such as gameplay, creativity, user experience, and technical performance.

    For alpha testing, you should use the Alpha testing checklist, which is a simplified version of the Scoring Rubric. This checklist is designed to guide you through testing the core elements of your game, ensuring that any bugs or issues are identified early.

    During this phase, don’t forget to check your written or in-game instructions as a part of the testing. Clear, well-structured instructions are crucial for enhancing user experience, as they help players navigate and enjoy your game with ease.

    By closely following this checklist, you can systematically refine your game, ensuring it achieves the highest score possible.

    Recording your work and your decisions within the GDD

      After playing and rating your game against the criteria in the checklist you should note some key points in the reflection section of your GDD:

      • What are the main problems you identified?
      • What can you do to fix the problems?
      • What changes can you make to improve the game performance?

      Level-up activities

      You might find it helpful to use an online bug detection tool.

      There are a lot of these, including some that are especially useful for game development. Here are a couple:

      • BugSplat – a tool that works in a wide range of environments and languages to help developers find and fix software crashes. It collects detailed information when an app or game crashes.
      • Valgrind – a programming tool that helps developers find memory-related errors, like leaks and bugs, in their code to make their software more stable and efficient. Focuses on programs built using C# or C++.