Sergio Mejia

Scenario: a new Vehicle Trading feature ships soon and there are 45 minutes to test. I ordered the work by risk:

1. Core flow: send, accept, decline, complete and cancel trades.
2. Ownership and item integrity: vehicles transfer correctly and ineligible ones can’t be traded.
3. Acceptance logic: any change to the offer must reset both players’ acceptance.
4. Edge cases: interruptions, different map locations, trading while inside a vehicle.
5. Player experience: is the process clear and does it give enough feedback?

Biggest risks I named: players being scammed or trading away a vehicle by accident, and wrong ownership transfers when a trade is interrupted, cancelled or modified.

Six issues from a gameplay video, each with what I saw, why it matters and how I’d investigate:

• 0:36 Currency “+” button does nothing: a possible monetization problem. Reproduce, check whether it’s consistent, then regression-test the fix.
• 0:59 Red notification points to a Jetski after a different vehicle was claimed. I had seen this myself in the live game.
• 1:38 Wheels appear to spin backward: unclear whether it’s a bug or an effect of the player moving back and forth, so I flagged it for investigation.
• 2:07 Vehicle disappears, then returns: I’d check spawning, loading, network sync and whether it affects other players.
• 4:36 Reflectance setting shows no visible change on seats and interior. I couldn’t tell if that’s intended, so I said so.
• 5:28 Sticker clips under the door ledge: a visual issue I suggested as medium priority.

I ranked six provided bug reports from highest to lowest priority:

1. Vehicle purchase: players charged several times for one vehicle (mobile). Direct currency loss on a core flow.
2. Race checkpoint: an exploit that undermines race integrity.
3. Race rewards: leaving just before the finish still pays the completion reward.
4. Vehicle customization: old colour appears after spawning; rejoining is a workaround.
5. Premium vehicle audio: wrong engine sound on a new premium vehicle; still usable.
6. Vehicle UI: speedometer stays visible after exiting; visual only.

Criteria: player impact, exploitability, financial and economic impact, competitive integrity, affected functionality and available workarounds. I stated my assumptions and said I’d re-rank if testing showed a different frequency, scope or impact.

Scenario: a new vehicle sometimes stops accelerating mid-race until the player exits and re-enters it. The developer calls it minor and wants to ship today.

• What I’d ask first: do other vehicles have it, how often does it happen, and how central is this vehicle to the update?
• How I’d find out: talk to the developers and reproduce it under different conditions.
• How I’d handle the disagreement: stay polite, present evidence, and get a second opinion from the QA Lead if I still saw significant impact.

My answer: no firm recommendation yet, leaning toward delaying until scope and impact are understood. My job is to give the team enough evidence to decide responsibly.

Three bugs I found in the live game, each written up with steps to reproduce, expected vs. actual result and player impact:

• UI / visual: speedometer overlaps the vehicle purchase menu (PC). Suggested severity Low, priority Medium, pending a check on whether any purchase option is hidden. Screenshot attached.
• Functional: tuning menu unresponsive in the NASCAR race queue. The vehicle shows but its options can’t be used, and only a respawn recovers it. Video attached.
• Rendering: lines at the horizon in the Sandbox map. I tried rain on another map and couldn’t reproduce it, so I recorded the trigger as unknown and listed what I’d test next.

Why it matters: where I couldn’t confirm something, I reported it as unconfirmed instead of guessing.