My short game testing career
█████░▒▓░▒▓░▒▓░▒▓████
I was there at Sony for a week in 2005 .
There is a reason why they expect testers to have a degree and a willingness to write hours of documentation.
They want a cost vs benefit analysis to justify breaking the game further to fix a load bearing anomaly.
( Hide or Fix ? ) .
Either way, the long commute & the sleep deprivation was not worth it .
Testers are easy to replace .
█████░▒▓░▒▓░▒▓░▒▓████
## Documentation is the “audit trail” for risk decisions ##
When a load‑bearing anomaly shows up late (e.g., a crash in the monetization flow, a progression blocker, a network exploit), producers and executives don’t just ask “Can we fix it?” They ask:
- How likely is this to hit players?
- How bad is the impact if it does?
- What’s the cost (time, money, schedule slip) to fix vs. to hide/ship around it?
- What’s our legal/PR risk if we ship it?
Your documentation becomes part of the decision record:
- “We knew about X on date Y, assessed severity as Z, chose to ship because…”
- If something goes wrong post‑launch, that trail matters for internal accountability and sometimes legal/PR reasons.
So they want testers who can:
- Log hours of structured notes without burning out.
- Summarize patterns (“this crash happens when…”), not just dump anecdotes.
- Keep consistent terminology so data can be aggregated and analyzed. [1][3]
## The cost–benefit analysis you’re describing
When a “load bearing anomaly” appears, the studio is effectively running this:
### Costs of fixing
- Engineering time: who can fix it, how many days, what else slips?
- QA time: retesting, regression testing, platform certification reruns.
- Schedule risk: missing a marketing window, seasonal launch, publisher milestone.
- Opportunity cost: features cut or delayed to make room.
### Benefits of fixing
- Reduced crash rate / churn.
- Better reviews / retention / monetization.
- Lower support burden and fewer refunds.
- Reduced risk of PR disaster or platform rejection.
### Benefits of hiding/working around it
- Hit the launch date.
- Preserve marketing spend and partnerships.
- Buy time to fix it properly in a patch.
Studios often formalize this with triage categories:
- **Blocker / Must‑fix**: threatens release or core loop (e.g., progression, payments, crashes).
- **High**: serious but maybe shippable with a day‑one patch.
- **Medium/Low**: can be documented, worked around, or fixed post‑launch.
Your role as a tester is to feed clean, quantified data into that process so they can justify “fix” vs. “hide/patch later” to stakeholders. [1]
Citations:
[1] FAQ 5: Testers -- The Unsung Heroes of Games https://www.sloperama.com/advice/lesson5.html
[2] How To Become A Video Game Tester (FAQ) https://www.gameindustrycareerguide.com/how-to-become-a-video-game-tester/
[8] Why game testing is so underpaid https://www.reddit.com/r/gaming/comments/166cli4/why_game_testing_is_so_underpaid/
