Thursday, January 5, 2017

Game Testing Techniques

Matrix Testing

- i.e. for fighting games

play every character vs. every character

Functionality Testing

- making sure game features work according to design documentation

Regression Testing

- Testing all bugs claimed to be fixed by programmers

Anything fixed is closed
Anything not fixed is reopened, noted, and sent back to the person who claimed
to fix it.

Open Testing

- When no features are a priority to check, or if all priorities are finished, open testing is
usually done

- Open testing can focus on anything and usually varies per person
organic playthroughs (checking the user experience)
checking all text
checking specific systems

Test Case

- Helps define what and how to test a game

- Usually in three parts:
1

Thursday, January 5, 2017

Description: what you are trying to verify

Steps: each step in chronological order - required to reach the state in which you
can perform the verification

Expected Result: The result you should expect to observe, provided the game
works properly

Checklist

- A collection of Test Cases put together with a specific goal in mind

i.e. validating the physics engine, localization (text and voice translation), or game
mechanics.

Bug Tracker Database

- A log that records all bugs that have been found, whether they have been reported,
claimed as fixed, and listed as open or closed (fixed).

- Each bug is called an item, or ticket

- Bug tracking databases can be anything from an excel spreadsheet to specific
software

Bug Report

- should be precise and give the reader all and no more than necessary to understand,
reproduce, and fix the bug

Bug Name
Bug ID (created after saving in system)
Area Path (how you got there, like level you are on)
Build Number
Severity (High/Medium/Low)
Priority (High/Medium/Low)
2

Thursday, January 5, 2017

Assigned to: (person you send it to)

Reported by: (your name)
Reported On: Date
Reason: Defect
Status:
Environment: (system like wii u, pc, etc.)
Description:
Steps to Reproduce:
Expected Result: (what it should do)