Game Testing Methodology
2.TESTING STRATEGY2.1SCOPE AND DEFINITION
In a simplistic view, testing is to identify
found in the software
so the problem can beremoved. There are different forms of tests and testing that can be categorized as
testing (“Clear Box” testing is also known as “White-Box” testing inthe software industry). Their testing objective and overall processes are indifference (e.g., test planning, test design, testing execution, regression testing and bug reporting), but their focus of attention puts emphasis on different aspects of the game:
” focuses on the functional or the playability aspects of the game. For examples, testing the user interface (e.g., the selection menus and the use of buttons),the “look and feel” (e.g., the graphics and animation), and the actual gameplay.
” is focus on the architecture and integration aspects of the gamesoftware. For examples, the use of a database, pipelines, the interaction/integration of game components like the rendering engine, the AI engine, sound, and so on.For Black Box testing, the tester must know how to play the game (e.g., use of the game pad,know the rules and the game flow). For Clear Box testing, the tester must understand whatcoding is. The Software Tester uses a run-time debugging environment, feeds the code or chunksof code with input (i.e., data, setting variables, etc.) and analyzes the test result.
a single person’s job, nor solely the responsibility of the Game Tester and theSoftware Tester for a game project. Every team member working in a game project must have“quality” in mind, and each person is responsible for the accuracy and completeness of the work that he/she produces.This testing methodology is
the only process and it should
be used in isolation. Thereader must be aware that this testing methodology is considered as an integral part to the GamePre-production and Production processes.In reality, no one can test a program
, i.e., testing every single part of the gameusing different and all available characters, so triggering different path of the logic and all the possible variations of input, interfaces, AI, and then output. Our testing strategy is to developexcellent, full-coverage, and effective testing (i.e., 80/20 rule).