A Glimpse into the World of QA
summary
This talk explains how QA teams investigate bugs by answering what/how/where/when/why and filing reports with title, description, reproduction steps, and attachments (screenshots, logs). It covers testing access modes (black/white/gray-box), organizing checks with test cases and suites, typical studio QA staffing across development stages (alpha, meta/beta, public beta), and using automation and a QA engineer to handle scripted tests and extend coverage.
AI-written summary · about
chapters (18)
- 0:00QA in video games
- 1:09Game tester role
- 3:16QA value for gaming
- 5:41Dev testing phases
- 7:04Crowd testing pros/cons
- 9:10Testing by game type
- 10:12Daily tester workflow
- 13:06Black vs white vs gray box
- 17:40Exploratory and play testing
- 21:30Writing bug reports
- 25:41Essential QA tools
- 27:26Test cases workflow
- 29:10QA job challenges
- 32:21Skills for testers
- 34:45QA career paths
- 36:32Key tester qualities
- 39:47QA future automation
- 42:59QA role evolution
related talks
46mWhat can QA do and what should it not fear?
53mIs having a QA a symptom of a dysfunctional team?
39mQA Has a Voice
45mWhat Would You Say You Do Here? Reframing Your Role In The QA Field
45mSame Old Story: Foundation of the QA Department. Tips and Tricks
41mLife Without QA
43mLean QA: Automation, Monitoring, Experiments
51mQuality Assurance vs. Testing