Checklists - slander36/IssueTrackerTraining GitHub Wiki

Description

Checklists can be used for everything from build verification to sanity checks to deep systems testing. Their purpose is to systematize testing as much as possible in order to reduce testing times and lower false positives/negatives.

Types of Checklists

Build Verification/Sanity Checks

Build verification tests and sanity checks should both be fast, and high level. Their job is to verify that no functionality that is core to the game has been broken. Examples of such features include, but are not limited to:

  • User input
    • Mouse clicks are registered
    • Movement commands work
    • Hotkeys are operational
  • Graphics
    • Everything is drawing appropriately
    • Character textures are working
    • Animations are working
  • Quest system
    • You can start a quest
    • You can complete quest objectives
    • You can finish a quest

These sorts of checks are usually done by using a “test map” where a majority of the core systems have been implemented so that a tester can verify the core systems in a matter of 10-15 minutes. The main point of this being catching a broken build before it is distributed to the rest of the team or is used in playtests.

Area Checklists

The other types of checklist are specialized area checklists, meaning art, systems, design, narrative, UI, etc. The job of these is to do a deep dive of a certain area/aspect of the game before it is put in the hands of a user (e.g. trade show, conference, usability testing). Examples include, but are not limited to:

  • Systems
    • Movement
      • Can move forward
      • Can move backward
      • Can move left
      • Can move right
    • Camera
      • Turn with keyboard
      • Turn with mouse
      • Zoom in/out
      • Collide camera with rigid body
    • Quest Systems
      • Can start quest from NPC
      • Can start quest from UI
      • Can complete quest objective type Pickup
      • Can complete quest objective type Enter Trigger Volume
  • Gameplay
    • Level 3
      • Quest 2
        • Can start quest
        • Can complete each objective
        • Can turn in quest
        • Turning in quest triggers Quest 3
  • Narrative/Text/VO
    • Level 5
      • Quest 3
        • Check each line to verify new text is in/not in
  • Art
    • Player
      • Player textures are rendering
      • Player textures are up to date
      • Player animation rigging is working
      • Player collision is working correctly

These tests are almost always done in game. In some cases, such as Systems, the test map can suffice, but full tests such as Gameplay, Narrative, Art, UI, etc., must be completed in the live environment with a clean playthrough. Play as if you are the end user.