Task 1B - Game Test Defects

Game Test Defects and Explanation,

Function Defect,

A function defect is apparent when something isn’t working like it should be. E.g. “You open a game and you change a setting. The setting you changed caused your game to crash.”

Assignment Defect,

An Assignment defect is a result of incorrectly setting or initialising a value used by the program or when a required value assignment is missing.

For example, “You start a new game, you should start with 0 gold. On the HUD display it says you have 10,000 gold.”

PlayerGold = 0
PlayerGold = 10000

Checking Defect,

A Checking defect occurs because of something being incorrectly checked within the programming.

For example,

IF SCORE >= 20
IF SCORE > 20

The code above will eventually have the same outcome and will not be as intended.

The correct code should be this;

IF SCORE <= 19
IF SCORE > 20

Timing Defect,

A Timing defect is apparent when something isn’t correctly timed with another thing. E.g. A sound effect is to early or too late, The movement of a character’s lips to the actual sound of their voice etc…

 Build/Package/Merge Defect,

A Build/Package/Merge defect is a result of something going wrong when the game is built.
Game developers are often producing newer versions of their game to update and to patch bugs from a previous update. The versions get better when the number increases.

Algorithm Defect,

Algorithm defects include problems that result from some calculation or decision process. For example, “The AI in the game is set to too high of a difficulty and it makes the game not fun to play.”

Documentation Defect,

Documentation defects occur in the fixed data assets that go into the game. This includes text, audio, and graphics file content. E.g. Spelling mistakes when text is onscreen etc…