Test Plan for the real boxing Project

 

The test plan for the real-person boxing project is as follows:

 

First, it is Dev's unit test (12.28-1.7 ). When developers write small modulesCodePerform unit tests to ensure that the writing module correctly implements the predefined functions.

 

Second, integration and validation testing (12.28-1.7 ). After the developer compiles some modules, the modules that can be assembled are assembled into subsystems for integration testing. Specifically, our projects are divided into the character model generation module and the game main module. Each of them has its own sub-module. We can perform the following tests on these sub-modules:

 

1) character model generation module

Input: Player photo, body model, special effect, and initial values of two player statuses

Test: after the body parts extraction module extracts the header from the input player's photo, the body parts parser can assemble the body data generated by the header and body model and input it to gesture & special
The effect images model is correctly displayed. During this period, you can test various user input photos that meet the design document specifications.

 

2) Main game Module

Input: keyboard and other input, initial value of Model Image and special effect data

 

Test: under each tick Driver, can the controller make a correct State Conversion Based on the user input, send the corresponding character action instructions, and then the player module generates the player state,
Displayed by the display module. Different test cases can be designed during this period to check whether they meet expectations.

 

3) Overall Test

Input: Player photo and keyboard input

 

Test: whether the game can run correctly as expected with a given input.

 

Then there is the system and Acceptance Test (1.8-1.9 ). It fully tests the entire game software, including functional testing, robustness testing, performance testing, installation testing, and so on, to ensure that the final software can run as required by the design documentation.

 

Finally, it is a user feedback test. After the alpha version is released, test the corresponding scenario based on user feedback and report it to Dev for correction.