Game Development Reference
The following is brief scope-of-test memo written at a small publisher planning to develop an
expansion pack to an RTS released earlier that same year.
M E M O R A N D U M
Manager of Quality Assurance
RTS EXPANSION TEST PLAN SUMMARY
It will take 1,760 hours to test this expansion pack, based on the following assumptions:
50-day production schedule,
Four-person test team,
10% allowance for overtime, and
No post-release patch testing.
Single Player (900 hours)
A significant amount of QA time will be spent testing the new campaign. Because the story mode
of these missions will be highly script-dependent, testers will be tasked with breaking those scripts
to ensure the user will have a seamless, immersive gameplay experience.
Because the developer has not designed cheats in the game, and because our experience with the
original game was such that saved games could not reliably be brought forward from prior builds,
campaign mode will take up the majority of test time.
Multiplayer (650 hours)
The thrust of multiplayer testing will be to:
Ensure correct implementation of new units and the new tile set,
Debug new maps,
Debug “interface streamlining�? (new functionality described in design doc),
Stress test game size,
Stress test army size,
Stress test game length, and (as time permits)