skip to main content

Summary

In this lesson, students will formally test their own games using criteria developed from the scoring rubric.

Curriculum codes

Digital Technologies: AC9TDI8P10 AC9TDI10P10

Design and Tecnologies: AC9TDE8P04 AC9TDE10P04

General capabilities

Critical and Creative Thinking: Analysing

a young man sitting on ground using laptop

Learning intention

In this lesson, you will test your team’s video game to identify any bugs or other issues with the game.

Prerequisites

Lessons 1 to 7

What you need

Before the lesson

  • Make at least one copy of the Alpha testing checklist per team. If each student has access to a device, make one copy per student.
  • Teams will require device access. At least one device per team is required. Headphones are also recommended for each device.

Activities

Introduction (10 mins)

  1. Explain to the class that while they will have been testing aspects of their game throughout the game development process, this lesson is about the first full test of their game.
  2. Introduce alpha testing to the class.
    • Alpha testing is the first stage of game testing.
    • In alpha testing the game is test played by the game developers. The aim is to identify any bugs or other issues with the game.
  3. Show the class the Scoring Rubric – putting this up on a screen would be appropriate.
    • This rubric is what the judges will use to score their games.
  4. Have the students read – or read through as a class – the elaborations for a one-star score and for a five-star score, for each of the criteria.
  5. Hand out copies of the Alpha testing checklist document. Discuss how this document will be used as a part of their game testing during this lesson.
  6. Explain to teams that they will play their game and score themselves using this checklist, which is a simplified version of the Scoring Rubric.
  7. Tell teams they can refer back to the Scoring Rubric during the alpha testing if they need more information to help them complete the checklist.
    • The important thing with a self-test like alpha testing is to be honest – if the game has issues, or doesn’t work as expected, you should note this. You will use this alpha test to help improve your game before it is submitted.
    • 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 is the main problem you identified?
      • What can you do to fix the problem?
      • What changes can you make to improve the game performance?
  8. Tell students to also check their written or in-game instructions as a part of their test.
    • Do the instructions make sense?

Main Activity (40 mins)

  1. Tell teams to test their games using the checklist.
  2. Explain that once the alpha test is complete, teams may work to fix problems and improve their game based on their reflections.

Reflection/Sharing Tasks (10 mins)

  1. Discuss problems that teams need support to solve.
  2. Tell students to take a photo of each feedback sheet and include these in their GDD.

    Teacher tip: You could have teams consult with other teams to help them fix identified problems.

Additional resources

  • Valgrind – Video game testing tool focusing on programs built using C or C++
  • BugSplat – App to track game performance, analyse and detect crashes