SimplyClassics
QA Portfolio Case Study
What began as a boundary collision test developed into a multi-system exploit chain involving vehicle placement, player positioning, invalid physics states, and a critical session-level spawn failure.
Overview
This page is designed to show not only the bug itself, but the quality of investigation behind it: identifying downstream effects, understanding likely system interactions, and presenting the issue clearly for technical and non-technical readers.
Testing focus
The original goal was to test map boundary integrity and player containment. The investigation used exploratory testing, repeat reproduction, and system interaction analysis to understand how one exploit could trigger broader gameplay disruption.
Bug chain
The strongest part of this case study is the progression from an initial map boundary issue into a critical gameplay failure. Presenting it as a chain helps recruiters quickly understand the depth of testing and the impact of the discovery.
STEP 01
A large vehicle placed against a boundary wall could partially intersect the map edge, creating a reliable starting point for further exploit behaviour.
Expected result
Vehicle placement should respect collision boundaries and remain fully inside valid map space.
Actual result
The vehicle can partially clip through the wall, opening a path to unintended traversal.
STEP 02
After partial clipping, entering and exiting the vehicle can place the player beyond the intended playable boundary.
Expected result
Vehicle exit logic should validate a legal and safe player position before placing the character.
Actual result
The player is relocated outside the valid playspace without corrective handling.
STEP 03
In some reproduction paths, the vehicle destabilises and falls beneath the map into the void.
Expected result
Invalid physics states should be prevented or the vehicle should reset cleanly.
Actual result
The vehicle enters an unrecovered invalid state beneath the map.
STEP 04
Once the vehicle enters the void, the session can lose access to vehicle spawning entirely until the player rejoins the server.
Expected result
The spawn system should recover automatically and clear invalid references so normal play can continue.
Actual result
Vehicle spawning remains unavailable for the remainder of the session unless the user leaves and rejoins.
Impact
This was not just an out-of-bounds issue. It affected core gameplay reliability, created a repeatable exploit path, and introduced a session-breaking failure in a player-facing system.
It demonstrates the ability to move beyond surface-level defects and investigate system consequences.
It also shows the value of edge case thinking in live games, where one failure can cascade across collision, physics, and session state systems.
Root cause thinking
The exploit chain suggests several validation gaps working together: collision boundaries allow invalid placement, exit positioning lacks legal-space checks, invalid vehicle states are not recovered, and the spawn system may retain broken references.
Suggested fixes
These recommendations keep the page grounded in QA thinking rather than overclaiming engineering certainty.
Evidence
Recorded gameplay evidence showing the exploit path and the resulting vehicle system failure.
Recorded evidence
Vehicle spawn void-state reproduction
This recording shows the exploit path leading to an invalid vehicle state and the resulting session-level vehicle spawn lockout.
Footage captured from Brookhaven RP on Roblox for QA analysis and portfolio demonstration.
Takeaway
I focus on reproducibility, impact, and system behaviour. Rather than stopping at the first bug, I continue testing the surrounding mechanics to understand whether the issue is isolated or part of a larger failure chain.