iGaming game testing: scope, versions and release evidence
A game-test report is meaningful only when its scope matches the product and deployment being used. Check the game version, configuration, RNG and applicable regulatory requirements. A supplier’s certificate should not be treated as approval for every future release.
iGaming Cyprus · Last updated:
What does the regulator require?
The UKGC’s games-information guidance requires relevant game and RNG test results from an approved test house and states that satisfactory testing and submission must precede release. The detailed requirements depend on licence and product scope.
Start with the applicable market and testing strategy. A report produced for one standard or deployment may not answer the questions raised by another. Ask the supplier and test house to identify the precise scope in writing.
What should the evidence register contain?
Maintain a register that connects the approved evidence to the live catalogue.
| Item | Why it matters |
|---|---|
| Game and version | Identifies the product actually tested |
| RNG and platform context | Shows dependencies and configuration |
| Applicable standard | Connects testing to the market requirement |
| Test house and report | Provides the evidence and scope |
| Release and change record | Shows whether the deployed product still matches |
How should changes be assessed?
The UKGC testing procedure addresses new games, fairness-affecting updates and integration changes. Assess changes before release rather than assuming an earlier report remains sufficient.
For example, a game may retain its marketing name while its mathematical configuration or underlying platform changes. The release review should identify the technical change, not rely on the unchanged name. Record the testing and reporting conclusion with the release approval.
What remains the operator’s responsibility?
The operator should know which games are offered, the evidence relied on and the process for removing or restricting an affected game. The UKGC guidance also addresses B2C maintenance of its games register when using B2B content.
Agree how suppliers communicate defects, withdrawn reports and material updates. Test whether the operator can identify affected versions and stop distribution promptly. A long list of certificates is less useful than a maintained link between each live game and its evidence.
What should a launch rehearsal include?
Select sample games and trace them from supplier contract through testing evidence to production configuration. Check reporting references where applicable, access controls and rollback procedures.
Record gaps as release blockers where necessary. Testing should be part of controlled deployment, not a folder checked once during licence preparation. Reconcile the catalogue again when adding markets, suppliers or major platform changes.
Frequently asked questions
No. Compare the report scope with the actual version, configuration and deployment.
No. The evidence needs to identify the technical product, not only its marketing label.
Sources and scope
This guide was prepared with AI assistance using the linked sources. It provides general information and practical preparation suggestions, not a legal opinion for a particular business. No personal professional review is claimed.
Get the right structure for your case
Book a free, no-obligation consultation. We’ll confirm the right Cyprus company + licence setup and a fixed fee for your business.