Test scope

Clear scope. Useful evidence.

Know what will be checked, how it will be recorded and what your team will receive. Our own local QA teams run the agreed cases on real devices and local networks, and our iGaming engineers add a likely cause and suggested fixes.

Onboarding

Sign-up, verification codes and sign-in, step by step.

You receiveAccount preconditions for each case · A step-by-step recording · The messages the player saw

See what we check →

Payments

Deposits, redirects, status and withdrawals through local methods.

You receiveTimestamps for each action · Before-and-after states and balances · Agreed test references for every attempt

See what we check →

KYC

Document upload, guidance and verification status.

You receiveThe input conditions for each case · Messages shown to the player · State changes and blockers

See what we check →

Gameplay & bonuses

Game entry, interactions and bonus claims against the rules.

You receiveCase outcomes · Recordings of any issue · Expected-versus-actual results

See what we check →

In-market performance

Load time, interruptions and reconnects on real networks.

You receiveDevice and network context · Timestamps and recordings · Definitions of each measurement

See what we check →

Localization

Language, currency, dates and time zones, read by locals.

You receiveThe screen location of each item · The text as observed · Screenshots

See what we check →

Compatibility

Layout and key journeys on agreed phones, computers and browsers.

You receiveAn environment matrix · A result for each combination · The affected screens

See what we check →

Benchmarking

Your product against competitors, on the same device and network.

You receiveThe actual test conditions · Observed differences · Evidence for each observation

See what we check →

Before we start

Agree before testing

Target market and test location
The build, accounts and access we will use
Devices and networks
Steps and expected results
Number of attempts, delivery timing and retests
For payment and KYC work: methods, data, amounts, stop conditions and sensitive-data handling

Good to know

What this is, and is not

Observed performance is distinct from concurrent load testing.
Functional QA does not constitute security testing, game-math validation or certification. Additional work is scoped separately.
Results describe the tested build, devices and time.

Not sure which scope fits?

Describe the problem your players report. We will suggest the services and the markets to start with.

Talk to us cs@factqa.com