QUALITY ASSURANCE

Bug reports, a test plan and playtests from my work on Royal Vermin.

BUG REPORTS

Bugs I found and documented while working on Royal Vermin. Each report covers the build, priority, frequency, steps to reproduce, severity and expected result. Use the arrows to go through the slides.

Gameplay · Priority: Medium

Crush Death Animation

When a crushed player and a player thrown off screen are eliminated within 2.5 seconds of each other, the game ranks them in the wrong order and the wrong player wins.

Crush Death Animation – Slide 1
1 / 7
Visual · Priority: Medium

Underground Podium

With the Quick game duration, the podium is pushed so low that it sticks out into the mini-game cave.

Underground Podium – Slide 1
1 / 8
Input/Gameplay · Priority: Low

Wave Dash

Holding jump at the exact end of a dash makes the character jump twice as high as usual.

Wave Dash – Slide 1
1 / 6

TEST PLAN

Feature tested: Auto-Grab

Auto-Grab is an accessibility option I designed for Royal Vermin. When it's on, the player automatically grabs nearby objects, so they only need to aim and throw. It helps players who struggle to hold a trigger while moving and jumping.

My goal

Make sure Auto-Grab stays reliable in every situation a player can create: menus, controller disconnections, eliminations, button spamming, special objects and other players. I focused on edge cases, because an accessibility feature that breaks silently hurts the players who need it most.

The plan contains 12 tests split into Menu and Gameplay. Each test lists its steps and an expected behaviour, and a results table tracks which tests pass.

AUTO-GRAB PLAYTESTS

Before Auto-Grab became a feature, I ran two rounds of playtests to find out what really made Royal Vermin's controls hard for our target players. The full document explains the design process. Here is what makes it relevant for QA.

A clear problem and hypothesis

Each iteration starts with a written problem and a hypothesis, so every playtest answers one precise question.

Measurable success criteria

Before testing, I set targets: at least 70% of players discover the feature on their own, the score gap shrinks in 70% of matches, and players rate their enjoyment from 1 to 10.

A repeatable protocol

Players first play a match with no explanation, then a second match with the feature introduced but optional. Both iterations use the same protocol, so the results can be compared.

Honest results

The first iteration missed its targets (20% discovery, a smaller gap in only 35% of matches). I reported it, noted the bias of a small Comiccon sample, and asked players why. That revealed the real cause: the grab-and-throw controls.

Verifying the fix

The second iteration was tested again with families matching our persona: 100% of testers said Auto-Grab helped them play, and 90% enjoyed it. The feature then shipped in the final game.