GAME FUNCTIONAL TESTING

GAME TESTING PROCESS

Today, games range from enormous, multiple player games to miniature diversions that you fit in the palm of your hand. Regardless of the size of the game and the intricacies of its operations, every testing project will follow a similar testing model:
  • Test Strategy & Planning
    • The project scope is determined - timelines, costs and resources are all assessed.
    • A team leader is assigned to the project and depending on the size of the test project numerous assistant leads may also be named.
    • The test leader defines entry acceptance criteria and target dates for the Alpha, Beta, and Gold phases of the test process.
    • The defect tracking database, DevTrack, is setup - this database will assign testers to track different bugs and subsequently track maintenance progress on individual bugs. Alternatively, the client's database can be used in which case the team leaders will familiarize themselves with the already existing system and the client's requirements at this stage.
    • The overall test plan is drafted.
  • Test Environment is Setup
    • Testers are prepped and required training is done.
    • A kick-off meeting is held and test plan is reviewed.
    • The release life cycle of every game is different and defined individually, but in general the following stages are present:
  • Testing Execution: Alpha
    • Alpha is the stage at which a game is generally playable from start to finish; major sub-systems and the user-interface are complete even if minor asset changes are still flexible. The main game features including placeholders for artwork and audio are implemented and the game is mostly navigational. This stage often involves the game leaving the development team and going for outside testing.

  • Testing Execution: Beta
    • Beta is the stage where developers get the most valuable feedback on the game and the game is now functioning at a level where massive multiplayer test scenarios can be deployed. In this stage the user interface as well as artwork and audio tend to be in their final stage. The game is mostly compatible with all specified hardware and software and all game features and options have been implemented.

  • Testing Execution: Gold
    • Once a game enters the Gold testing phase, the game looks and feels like a common retail game. All major functional errors are fixed, and unresolved issues have a documented plan that has been communicated to the developers. The version of the game that is sent to manufacturers is called the gold master, therefore, the final few versions of the game are know as gold master candidates (GMC).

  • Release Certification
    • In the release certification phase a clean GMC is issued and sent to the platform manufacturer for a set of tests. The platform manufacturer will test the game in two phases: the first phase is to ensure compatibility with the technical requirements checklist and the second phase tests the game code for stability and function. The platform manufacturer will always issue a report of the bugs they found and a plan for re-submission.

  • Post-Release Testing
    • Software updates and patches are an appropriate remedy if a game is shipped with defects. Although generally considered unfavorable for users and developers, it is important to note that developing and testing a patch is an opportunity to fix bugs that were originally waived and incorporate some additional style to a game.

MO Group International game testing services are designed to deliver clarity and cultural sensitivity to your target market. Contact us today to get started!