The planning phase, is where they plan on revisiting with every build. they would consider things such as "what has changed in the design spec since
the last build? What additional test cases have been added? What new
configurations will the game support? What features have been cut?" The testing should ensure that no new issues would be introduced in the process of
fixing bugs.
Prepare
Code,
tests, documents, and the test environment are updated by their respective
owners and aligned with one another. By this time the development team should
have marked the bugs fixed for this build in the defect database so the QA or
test team can subsequently verify those fixes and close the bugs.
Perform
Test the new build check if there is any defect, they also test “around” the bug
making certain they have done everything they can to recreate the bug. More research that's done, the
easier it becomes to report the bug.
Report
This is where they log in their reports of any defects and bugs they've found.
Repair
The test
team participates in this step by being available to discuss the bug with the
development team and to provide any directed testing they may require to track
it down.
Repeat
Repeat the process with a new bug to test.
 |
| Game Testing Cycle |
No comments:
Post a Comment