Check that games and bonuses behave the way you promised.
We check what the player sees and does: entering a game, interacting, coming back to the lobby and claiming a bonus. Every case is run against the rules you provide.
What we check
- Game entry, loading and return flows
- Feedback after player interactions
- Balance display
- Bonus eligibility messages
- Bonus claim states
What you receive
- Case outcomes
- Recordings of any issue
- Expected-versus-actual results
- Agreed retests on updated builds
- A likely cause and suggested fixes from engineers experienced in iGaming
Every finding comes with the evidence behind it.
This is the shape of a single record in your report.
Examples of what this can surface
- A game returns to a blank screen after a network interruption
- The balance shown in the game differs from the wallet
- A bonus shows as available when the player is not eligible
- A claimed bonus is still offered again
Bonus shows as eligible but the claim returns an error
- Case
- Claim the welcome bonus after the first deposit
- Expected
- Bonus is credited and its status changes to claimed
- Observed
- Claim button returns an error; status stays "available"
- Environment
- Shenzhen · mid-range Android · local 4G
- Evidence
- Recording, expected-versus-actual note
- Likely cause
- Eligibility is checked when the offer is displayed, but the claim re-checks it with different rules.
- Suggested fix
- Use one eligibility check for both the display and the claim.
We agree the details before any test runs.
What we need from you
- The bonus and game rules, with expected results
- Test accounts in the required states (new, deposited, eligible)
- The games and bonus offers in scope
What we agree up front
- 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
We check the player experience against your rules. Game-math and random-number validation are not part of this service. Functional QA does not constitute security testing, game-math validation or certification. Additional work is scoped separately. Likely causes and fixes are our engineers' assessment from observation and experience. Please confirm them against your own logs and code.
Often run together.
Want this tested in your markets?
Tell us the product, the markets and the journeys that matter. We will come back with a scope and a plan.