Game Test Defects

Defect	Explanation with Example
FUNCTION DEFECT	This is a defect that stems from the game code, this effects how the player plays the game. If may also affect Game Capability. A Function defect is where a function does not work as intended. The Game may crash when collecting an item, this would be a function defect.
ASSIGNMENT DEFECT	This is where numbers don’t work correctly, it may either not counting properly or is may break completely. CIV 2, Mahatma Ghandi’s Kindness underflowed from 0 to 255 which made him nuke you.
CHECKING DEFECT	This is where triggers in games don’t work, where certain thing are supposed to happen but they break half way through which results in broken games. Oblivion does not check the game progress so if the player triggers the ending cutscene the game ends
TIMING DEFECT	This is where the timing is off which results in odd game movement or even a softlock. Examples of this is in Pokemon Yellow, if the play is in a certain position the cutscene where Professor Oak leads you to his lab you will not hit the door due to the being offset
BUILD/PACKAGE/MERGE DEFECT	This is where the build/version you play is old or a test version which could make somethings breaks. Files may be incompatible for eachother which would break some parts of the game.
ALGORITHM DEFECT	This is where calculation go wrong such as Pathfinding for enemies. An example of this is the pathfinding of party members in Fallout 3 as they will get into a position where they get stuck and you have to leave them behind.
DOCUMENTATION DEFECT	This is where things are not appropriately ladled which leads to mistakes that van cause problems. An example of this is in Street Fighter 2, if you won as Ryu you would mention “Shen Long” which is just a mistranslation of Dragon Punch which is a move in the game.