Game Test Processes

Smoke testing

This is a test that attempts to see if the new build of a gaming software is smooth enough to run at a stable FPS for future tests or if it doesn't. If the software tests are not efficient and effective, then the program will be updated by the developers and then the test will be repeated again.

White box testing

This is a testing technique used for checking whether the program gathers test data from the coding that has been programmed into the game, this is because games need the correct coding to make sure that the mechanics work fluently within the game.

Black box testing

This is a similar testing method to white box testing, as it examines the functionality of the software but not the internal structure. This is because we need to see if the application functions properly of the game mechanics and the black box testing only tells us this in an clear format without any specific details of why and how.

Clean room testing

This is used to scan the software to find if it is clean and reliable using mathematical equations and algorithms. The strategy is to detect and remove all of the defects that are very obvious and easy to find manually but this is quicker option to get rid of them all in one big go.

Play testing

This is the stage that takes place when the game is being tested by QA testers that are hired to find any bugs or faults within the game that effect the gameplay in a negative fashion. They will play through the game story or multiplayer and try to complete and noting down any bugs that they find to report back to the studio so that they can be fixed for a more enjoyable experience.

Ad Hoc testing

This is completed with no information and it is completed one time and if a defect is found, then the process is repeated. The process is completed at random and if a fault is found within the software, then the test would commence in other parts of the program to see if the same glitch is present.