Case Study · Gaming

Independent QA for Outsourced Development: A Gaming and Live-Streaming Startup

Manual testing, Figma design checks and a Playwright framework in progress, for a platform built by an outside development team.

engagement / gaming-startupOngoing
Client
Gaming and live-streaming startup, unnamed
Platform
Web app and admin panel; mobile apps next
Our Role
Independent client-side QA, after the vendor's own QA
Team
2 QA engineers, led by our founder
Testing
Manual functional testing, Figma design checks, regression and smoke
Automation
Playwright with TypeScript, framework being built
Signed Off Only After Our Independent Pass
2,000+Manual Test Cases for Web
7Areas Tested, Player and Admin Side
2SprintSynergy QA Engineers

The Result

What the Startup Gets

  • No milestone signed off with a blocker or critical bug. Each milestone passes the vendor's QA, then ours, before it is signed off.
  • Three bugs fixed before they reached paying players: sales that kept going after the store was switched off, a price that changed during checkout and a cancelled setting that saved itself.
  • 2,000+ test cases ready for every milestone, with golden scenarios, a regression checklist and a smoke suite.

Overview

The Client's Own QA Team

A gaming and live-streaming startup is building its platform with an outside development team. SprintSynergy is the client's independent QA team. Two QA engineers, led by our founder, test the web app and the admin panel and check screens against the Figma designs. They maintain 2,000+ manual test cases for web. The vendor tests its own work first. Our pass comes next, and a milestone is signed off only after it. A Playwright and TypeScript automation framework is being built alongside. The client is not named.

Sample Test, Simplified

The Problem

Someone on the Client's Side

A startup that builds with an outside vendor needs someone on its own side to check the work. The vendor's QA shows that the build works the way the vendor understood it. An independent pass shows whether it works the way the client asked.

This platform has a lot that can go wrong at once: accounts and security, paid packages, a wallet with payouts, games and live streams with chat. An admin panel controls all of it.

What We Test

Every Part a Player or Admin Touches

  • Accounts and Security: registration, social sign-in, email and phone verification, two-factor authentication, sessions and privacy settings.
  • Payments: paid packages, subscriptions and checkout.
  • Wallet: balances, transaction history and payout requests.
  • Games, Streams and Chat: game sessions and leaderboards, live streams, chat and its moderation tools.
  • Trust and Safety: reports, moderation cases and account restrictions.
  • Admin Panel: staff roles and permissions, platform and store settings, finance operations and the audit log.
  • Design: screens in the web app and the admin panel compared with the Figma designs.

How We Test

Vendor First, Then Us

  1. Test Cases FirstOur engineers keep 2,000+ manual test cases for web. On top of them sit golden scenarios for the journeys that must never break, a regression checklist and a smoke suite.
  2. Vendor First, Then UsThe vendor runs its own QA and then hands each task over for our independent pass. Every run, result and ticket update is recorded in writing.
  3. Two Roles at OnceSome bugs only appear when a player and an admin act at the same moment. We test with both signed in, in separate browsers.
  4. Real ConditionsWe test real network loss, not only the browser's offline mode.
  5. Design ChecksFunctional testing comes with a visual check against the Figma designs, for the web app and the admin panel.
  6. Automation in ProgressA Playwright and TypeScript framework is being built alongside the manual testing.

What We Found

Caught in the First Milestone

Three bugs from regression testing of the first milestone. All three are now fixed.

Store · Admin PanelFixed

The Store's Off Switch Did Not Stop Sales

With sales switched off in the admin panel, the buy button still worked and a real purchase request went through. Two other paid products had the same fault. This switch is the store's emergency brake, so a failure here means selling when the business must stop.

Checkout · PricingFixed

A Price Changed Silently at Checkout

An admin raised a subscription price while a player was already in checkout. The player went on to payment at the higher price, with no warning. A player who agreed to one price and pays another is how chargebacks and complaints start.

Admin Panel · SettingsFixed

A Cancelled Change Saved Itself

An admin picked a new setting, lost the network, clicked Save and then Cancel. When the network came back, the held request went through and the live setting changed. The browser's offline simulation never showed this bug. Only a real network drop did.

Where It Stands

  • Each milestone is signed off only after our independent pass.
  • 2,000+ manual test cases for web, with golden scenarios, a regression checklist and a smoke suite.
  • A Playwright and TypeScript automation framework, being built.

What Comes Next

  • Mobile app testing, as the mobile apps are built.
  • API test automation in Postman.
  • Performance testing in JMeter.

Questions

Frequently Asked Questions

With an independent QA pass after the vendor's own. The vendor checks its work against its own reading of the requirements. We check it against what the client asked for. On this platform, every milestone goes through the vendor's QA first and ours second, and it is signed off only after both.

Building with an Outside Team? Get a QA Team on Your Side.

Book a free 30-minute QA strategy call. A written QA plan follows within 48 hours.

Book a Free QA Strategy Call