Create a Test Plan (Part 1)

Sort elements

• Plummet5 core game mechanics — gameplay includes both single and multiplayer, with randomized falling block shapes, clearing instances of 5-in-a-row.
• All core gameplay functionality (block shapes falling, clearing on patterns, level progression, etc.) using default controls. All gameplay content including visuals and sound. Does not include scoring, control customization, save system, or compliance testing. Those features are covered in other Test Plans.
• Diagonal clearing mechanic is new and unproven and no dedicated UX designer
• Player expectations Plummet5 block shapes can be rotated and moved from side-to-side within the play area. Row clears when five matching colored octagons are in a single or multiple straight-line row(s) on any orientation.
• Previous versions of the game did not include diagonal row matches.
• Question for the design team: How do we accommodate players that are color-blind?
• Gameplay is consistent with prior releases, visuals match concept art targets.
• Use manual testing to cover core gameplay and ensure mechanics meet player expectations. Leverage data to help ensure balanced coverage. Automation for repetitive tasks, and debug to increase manual tester efficiency. Open beta for direct player feedback, especially around balance and pacing.
• Scripted and exploratory manual testing as part of component testing and system testing.
• Use coverage reporting to ensure balanced testing of game levels and testing across supported platforms.
• Automated smoke and performance testing. Debug command to advance to any level. Performance will include memory profiling of CPU and GPU usage, framerate, memory leak testing.
• Estimate of 4 tester weeks per test pass, with an expected 5 full passes throughout development. This includes testing for feature delivery, as well as reviewing bug fixes, and preparing for release review.