jhonatan-oliveiradev Testing Playable Games
Test in layers
- Boot and recoverability: load, restart, pause, resume, route/scene transition.
- Controls: keyboard/gamepad/touch as supported; repeated and conflicting inputs.
- Movement and camera: boundaries, collision, slopes, follow lag, zoom, occlusion.
- Combat: hit registration, invulnerability, cooldowns, enemy state transitions, death, reset.
- Animation: transitions, looping, foot sliding, weapon continuity, effect timing.
- Progression: inventory, pickups, checkpoints, save/load, rewards.
- Performance: frame pacing, long-session stability, asset spikes, offscreen work.
Evidence
Reproduce failures with exact steps. For visual defects capture the state or frame where the problem is visible. Separate design feedback from implementation bugs.
Acceptance
A feature is not complete because its isolated code path works. It must survive normal gameplay sequences and transitions into and out of the state.