Web — The Magic of QA Processes in (Super) High-Load Systems
summary
Wargaming Kyiv describes how they run QA for very high‑load web systems (up to 800,000 concurrent users in beta) by using pre‑production design reviews, a master test plan plus per‑version Jira plans, and staged environments (sandbox, staging, production) with defined release types (emergency, independent, package/game). They use Python automation frameworks for testing, run both synthetic and organic performance tests, perform security audits, generate automated interactive release reports and monitoring triggers, and collect post‑release metrics and retrospectives to verify deployments.
AI-written summary · about
chapters (9)
- 0:00QA in high-load systems
- 4:13Team roles and quality
- 9:13Pre-production testing
- 15:36Test scenarios
- 21:43Non-functional testing
- 25:36Release types
- 29:48Post-release activities
- 35:13Monitoring feedback
- 38:48Conclusion
related talks
43mLean QA: Automation, Monitoring, Experiments
35mQA in GameDev. How to: build outsource processes, hire right people, successfully release projects
56mNo QA resources? You can still deliver a quality website
46mQA to QE: Scaling Quality with Ownership, Code, and Culture
37mTesting Games
01h 04mQA in GameDev: How to Build Processes, Hire the Right People and Successfully Ship Projects
53mWhat Happens When Everyone is QA? And I Mean Everyone!
48mBeyond Bugs: How AI Turns QA into Full-Cycle Engineers