QA for gaming Part 2: Phases and the Value of Crowdtesting

This assumption leads to delayed issue identification and release delays. For modern games, QA is a continuous discipline that spans the full development and requirement lifecycle from early concept through years of post-launch operations.

In large-scale gaming projects, development can take three to seven years. QA begins with the first line of code, starting with three to ten testers. During mid-production, the team grows to 20–50 testers, and in alpha and beta phases, it expands to 50–200+. After launch, live-service games maintain 10–50 testers for updates, events, and patches. With a global testing model, QA can begin immediately and scale across thousands of devices worldwide.

This article walks through nine QA phases in game development, detailing what occurs at each stage, why it’s important, and how studios maintain quality from launch through post-release.

TL;DR

• QA is a continuous process covering nine phases, from pre-production through post-launch support.
• Quality Assurance covers core systems, visuals, multiplayer performance, localization, security, and platform compliance.
• Console certification typically spans one to three months per platform and covers all critical test cases.
• Live-service and MMORPG titles require QA for server load testing, anti-cheat systems, and continuous operations.

Gaming QA: 9 Phases From Pre-Production to Live Operations

As games grow in scope and complexity, teams can’t confine quality efforts to just one phase. Each stage of development introduces different technical and gameplay risks, requiring deliberate processes, experienced testers, and the ability to scale coverage when needed.

AAA (Large, high-budget games) titles and massively multiplayer online role-playing games (MMORPGs) rely on rigorous QA to ensure performance, stability, and player trust. 

Let’s explore all nine QA phases, covering timelines, team responsibilities, and practical insights from real-world projects. 

Phase 1 – Pre-Production QA: Laying the Foundation

Timeline: Two to six months
Team size: Two to five testers

QA teams begin in pre-production by aligning the testing approach with the Game Design Document (GDD) and flagging risks before development accelerates. Decisions made at this stage affect test coverage, tooling, and workflows for the entire project. Addressing gaps early reduces rework, keeps timelines predictable, and lowers the risk of late-stage failures. T cgb 

Core activities in Phase 1

• QA strategy: Create a plan defining the testing approach, KPIs, risk assessment, milestone entry and exit criteria, and resource allocation for the development timeline.
• Risk assessment: Identify problem points, technical constraints, and platform-specific challenges, including server stability, database performance, persistent world issues in MMORPGs, and device compatibility.
• Certification review: Start checking TRC, TCR, and Lotcheck requirements early. Facilitate the team's compliance and avoid last-minute development problems.
• Tool selection & test environment setup: Set up tools and test environments, including JIRA for bug tracking, TestRail for test management, automation frameworks, performance profiling tools, and dedicated test servers or CI/CD pipelines for multiplayer projects.
• Real-world testing insight: In pre-production, running early builds on a small set of real devices often reveals platform-specific constraints, such as memory limits, OS throttling, or rendering quirks, that are not visible in emulators. Catching these issues early ensures the testing approach, tools, and workflows are built around realistic device behavior, reducing rework later in development.

Building a strong QA culture in pre-production supports proactive quality and helps avoid costly issues later in development.

Phase 2 – Early production QA: validating the core systems

Timeline: Three to 12 months
Team size: Three to ten testers

At this stage, testers check core systems daily, collaborate closely with developers, and run automated checks to prevent delays. They track performance, physics, and rendering to maintain stable builds.

Core activities in phase 2

• Unit testing oversight: Monitor unit tests to ensure critical systems follow the Arrange–Act–Assert methodology.
• Smoke testing & automated builds: Validate daily builds using smoke and automated tests to catch early failures.
• Core systems baselines: Establish early performance baselines for core systems to detect issues before escalation.
• Feedback loops: Maintain daily QA–developer feedback cycles to address issues promptly.
• White-box validation: Review code-level behaviour to confirm critical systems operate as designed.
• Commit-based automation: Run automated test suites on each code commit to surface issues immediately.
• Documentation & test cases: Keep defect logs organized and update test cases regularly to ensure full regression coverage.
• Expanded core systems testing: Validate rendering, physics, animation, pathfinding, and memory stability.

Early production QA verifies core systems, catches issues early, and maintains smooth development progress.

Phase 3 – Mid-production QA: netcode and multiplayer

Timeline: Six to 18 months
Team size: Five to 15 networking specialists

QA tests multiplayer servers under real-world loads to ensure smooth matchmaking and validate layer interactions. Teams also verify social systems, economies, and persistent mechanics to prevent issues before alpha.

Core activities in phase 3

• Network testing: Validate gameplay under varying network conditions, simulating latency, packet loss, and disconnections across regions.
• Server load testing: Validate server stability under sustained and peak player loads, covering database limits, backend capacity, and matchmaking behavior.
• MMORPG-specific QA: Verify persistence, economy balance, server-client synchronization, instance management, phasing, and social systems, and social systems to ensure smooth multiplayer experiences.

Entry/Exit criteria:

Entry: Confirm stable multiplayer infrastructure before testing begins.

Exit: Check that servers stay stable under maximum load, latency remains acceptable, no critical sync issues occur, and the system is ready for launch.

Historical Risk Context

Lessons from past launches, such as Anarchy Online in 2001, show that underestimated server load can crash live games. Early load testing prevents similar failures, reducing the risk of catastrophic multiplayer issues during beta or launch.

‍

Mid-production QA confirms that multiplayer systems can handle real player load, reducing the risk of server failures and gameplay instability as the game moves toward alpha.

Phase 4 – Late production QA: visual assets and integration

Timeline: 12-36 months

Team size: Ten to 50 QA testers

Late-production QA validates visuals and gameplay, preventing regressions and ensuring a polished experience. Teams identify integration issues early to avoid disruptions before alpha and beta testing. They also benchmark performance and memory usage to maintain stability across devices.

Core activities in phase 4

• Visual asset testing: Check for rendering glitches, missing textures, animation overlaps, LOD issues, UI problems, localization errors, and audio-visual timing in cinematics.
• Integration testing: Verify that combat, quest, inventory, progression, and social systems work together correctly without breaking gameplay.
• Performance profiling: Benchmark frame rates, memory usage, and load times across devices and platforms.
• Regression & functional testing: Test every update to prevent breakages, using automation to let testers focus on new features and exploratory testing.
• Scale & tools: Manage large content volumes, track defects in JIRA, and prioritize critical issues to maintain stability at scale‍
• Real-world testing insight: Cross-device and cross-region testing helps surface integration and performance issues that may not appear in limited test environments, supporting consistent gameplay quality worldwide.

Late-production QA checks that all game systems and assets function together, preventing integration issues and ensuring a polished player experience.

Phase 5 – Alpha testing: feature-complete validation

Timeline: Three to six months
Team size: 50 to 200+ testers

QA verifies all core systems during alpha, spotting remaining performance, stability, and visual issues. This phase confirms the game is feature-complete and ready for beta and platform certification.

Core activities in phase 5

• Functional & integration: Validate that all core systems function correctly across platforms.
• Performance & load: Identify and fix remaining performance, stability, and visual issues.
• Localization & UX: Verify translations, UI, controls, HUDs, and cinematic timing.
• Security & analytics: Check data protection, anti-cheat, and event tracking.
• Compliance: Begin internal checks against platform requirements.
• Regression & smoke testing: Re-test previous fixes to prevent regressions.
• Exit criteria: Ensure that the exit criteria are met, i.e., all critical bugs fixed, major bugs mostly resolved, and core gameplay validated.
• Real-world testing insight: Testing across devices and regions helps teams identify potential gameplay, integration, and performance issues early, allowing critical problems to be prioritized and addressed before beta and certification.
  
  

Alpha testing verifies core functionality and stability, addressing remaining issues before the game moves into beta and certification.

Phase 6 – Beta testing: validation at scale with real players

Timeline: Two to eight weeks (closed beta), two to six months (open beta)
Team size: 100-10,000+ players

Beta testing is a phase of software testing where a near-final version of a product is released to a limited group of real users outside the development team to validate it in real-world conditions.

It’s the stage where you check:

• Does the product work as expected in real usage?
• Are there bugs that didn’t show up in internal testing?
• Is the user experience clear and usable?

Pro Tip

Test with real players, not just test cases. Internal QA follows structured paths, but players don’t. Testing with real users across devices, regions, and networks reveals edge cases, balance issues, and progression breaks that lab testing routinely misses.

Core activities in phase 6

• Server load: Test the system under heavy and sustained player activity.
• Gameplay & UX: Collect player feedback to improve mechanics, UI, and progression.
• Closed beta: Conduct testing with a small, controlled group under NDAs, resetting progress after completion.
• Open beta: Conduct large-scale testing across devices and playstyles to gather community feedback.
• Bug prioritization: Focus on critical issues for resolution before launch.
• Analytics: Monitor player interactions to refine progression, balance, and matchmaking.
• Real-world testing insight: Beta testing with players across regions and devices helps teams identify potential gameplay and performance issues before launch, enabling prioritization and fixes that improve stability and player experience. 

Beta testing exposes actual player-facing issues, giving the team a chance to improve the game. Insights from players help enhance performance and overall quality.

Phase 7 – Certification testing: platform compliance

QA tests every console requirement early to ensure stability, performance, and UI consistency. Teams validate achievements, save/load, and network features to prevent launch delays. Early checks not only identify potential compliance risks before they become costly. This also takes a proactive approach, keeps certification on track, and reduces last-minute issues.

Platform requirements

• PlayStation TRC: Twenty-six major entries covering suspend-resume, save integrity, controller handling, trophies, parental controls, UI consistency, and memory limits (170+ test cases).
• Xbox TCR: Thirty-four major entries for Quick Resume, Xbox Live integration, achievements, multiplayer, crossplay, privacy, save roaming, and account privileges (134+ test cases).
• Nintendo Lotcheck: Fourteen major entries for Joy-Con configurations, handheld-to-TV transitions, sleep-wake state, touch screen, local wireless play, and performance stability (140 test cases).
• PC stores: Steam and Epic have simpler requirements that emphasize clean builds, accurate in-game assets, and optional achievements.
  

Best practices

• Build automated test suites for TRC/TCR/Lotcheck checks.
• Run internal certification simulations before submission.
• Hold regular syncs with platform representatives to address issues early.
• Start certification preparation during the alpha and beta phases to avoid last-minute delays.

Common Failure Points

• Crashes during suspend/resume
• Save/load errors
• Outdated SDK/API usage
• Inconsistent metadata
• Missing required warnings

‍

Passing certification testing confirms the game follows platform standards, reducing the risk of technical problems at launch.

Phase 8 – Release candidate and launch

 Timeline: Two to four weeks
Team Size: Full QA team

Release candidate QA validates all fixes and updates under real launch conditions, preventing issues that could affect players on day one. Teams test server stability, load performance, and device compatibility to ensure a smooth release. They catch last-minute problems before launch, protecting player experience. This phase builds confidence that the game is ready for a polished, reliable launch.

Core activities in phase 8

• Complete regression: Confirm all certification fixes and late-stage changes have not introduced new issues.
• Day-one patch: Finalise remaining B-level fixes for inclusion in the launch patch.
• Launch readiness: Validate storefront assets, entitlements, build signing, and review/marketing builds.
• Server validation: Simulate launch-day traffic to verify load handling, matchmaking stability, and backend performance.
• Exit criteria: Verify that the team has resolved all critical issues, met all performance targets, and proven server capacity for the expected load.

Comprehensive RC validation minimizes launch-day risk, confirming server scalability and build stability. Final RC testing ensures the game is stable, servers are ready, and the launch proceeds smoothly for players.

Phase 9 – Live operations QA: continuous quality post-launch

Timeline: Continuous
Team size: Ten to 50 QA specialists

QA specialists actively monitor servers, analyze player feedback, and validate content updates. They catch issues before they impact gameplay and maintain smooth performance. Ongoing live testing ensures stability across devices and regions. This proactive approach keeps players satisfied and loyal.

Pro Tip

Live QA is an operational requirement, not post-launch cleanup. Every patch, event, and backend change introduces new risk. Continuous testing is essential to protect stability, player trust, and long-term retention.

Core activities in phase 9

• Monitoring: Track server health, crashes, load, and latency.
• Patch & update testing: Verify hotfixes, content updates, and seasonal events.
• Anti-cheat & security: Detect exploits and protect player data.
• Player feedback: Use support tickets, community reports, and in-game feedback to prioritize fixes.
• Economy & balance: Confirm game systems, progression, and events operate correctly.
• Infrastructure: Manage server scaling, CDN performance, and backend system health.
• Release control: Test new features safely with feature flags, gradually roll out updates, and validate rollback procedures.

Continuous QA after launch preserves game stability, keeps players satisfied, and ensures updates and new content run smoothly without introducing critical issues.

Final Thoughts

Games today are long-term services. Sustained success depends on reliable updates, stable live operations, and player confidence that the game will work every time they log in. QA shapes release schedules, certification success, and player retention. Delays force teams to rush fixes, risking launch quality and player trust.

Running QA across the full development lifecycle reduces these risks. Early validation limits rework, keeps certification predictable, and ensures performance holds up across real devices, regions, and network conditions. For live-service and multiplayer titles, this approach is critical to maintaining stability beyond day one. Continuous QA supports that goal by protecting quality at scale and preserving player trust over time.