GTD: Lesson - Game Test Document

Two programmers work together on a game.Game Test Document

When testing a game, it helps to identify potential problems and areas of improvement before the game is released. In this process, identifying and preparing your users is the first step. Once you've found a tester, provide them with a concise summary of the game's purpose and features, and let them know the game is still a work in progress. The second step is introducing the Think Aloud Protocol, where the tester vocalizes their feedback while playing the game. The third step involves seeking specific feedback by asking questions. Finally, the fourth step is to repeat the process with more users and make key changes based on the feedback received.

In this way, testing and debugging will help you develop a better game for your audience. In this lesson, we will be utilizing the Engineer For The Week game test document titled, ‘Testing with Users’ to evidence our understanding of this important step.

Let’s examine each element of this process one at a time.

STEP 1: IDENTIFY AND PREP YOUR USERS

Provide the tester(s) with a concise summary of the game’s purpose and features. You can write down a summary of your game. Let the tester know your game is still in progress, as people often give more honest feedback about products in the early stages than when the product is nearly done.

STEP 2: INTRODUCE THINK ALOUD PROTOCOL

Instruct your tester to play your game and talk out loud about their experience while using it. The process of having a tester vocalize their feedback in real time is called the Think Aloud Protocol. Encourage the tester to record their verbal feedback as they play the game or take notes on what they say, what they like and don’t like, and where they get stuck.

STEP 3: SEEK SPECIFIC FEEDBACK

Ask questions! The following questions are great questions for feedback:

  1. What was your favorite part of the game?
  2. What was most confusing about playing the game?
  3. What was something you wanted to be able to do with the game that is currently not available?

STEP 4: REPEAT WITH MORE USERS

Repeat Steps 1-3 with another tester. Once your Engineering Team has conducted several tests, go back and identify key changes you can make to your game based on the feedback you received.

Self-evaluation using the game test document is an essential part of the game development process too, as it allows developers to identify and address any potential issues with their game before it's released to the public. Before publishing your game test document for others to utilize when providing feedback, complete a self-evaluation first and complete step 1 of the document before making it available to others.

In conclusion, testing and debugging a game is a critical step in the development process to ensure that it meets the expectations of its users. To do so, it is important to identify and prep users, introduce the think aloud protocol, seek specific feedback, and repeat the process with more users. By following these steps, developers can gather valuable insights into how their game is being received and make the necessary changes to improve the user experience. Ultimately, the success of a game depends on how well it meets the needs and expectations of its users, so thorough testing and debugging is essential to ensuring its success.

[CC BY 4.0] UNLESS OTHERWISE NOTED | IMAGES: LICENSED AND USED ACCORDING TO TERMS OF SUBSCRIPTION