iGaming Software Testing Guide: How Casino Platforms Get Tested and Certified
This guide covers how iGaming platforms are tested and certified: the four QA disciplines, the laboratories that certify software, the confusion between GLI-19, GLI-11 and GLI-33, and a realistic view of programme sequencing, timing and cost, not RNG certification alone and not API conformance testing alone.
Casino software testing is the structured verification of an iGaming platform across four disciplines: functional testing, performance testing, security testing and compatibility testing. It runs alongside, but is not the same as, certification of the platform and its games by an accredited testing laboratory.
Testing an iGaming platform is not one activity. This guide covers the whole-platform quality assurance (QA) and certification programme, its sequencing, duration and cost, distinct from RNG certification specifically and from API conformance testing specifically, each of which has its own dedicated guide linked below.
Why is QA mandatory before an iGaming platform can launch?
Casino software certification and gambling industry tester certification are two different things, rarely made explicit. Laboratories such as GLI and eCOGRA certify the software itself. ISTQB, the global software testing standards body, separately accredits individual testers through its Certified Tester Gambling Industry Tester qualification.
Operators do not really choose whether to test a platform before launch. Regulators decide that for them: a licence application in most serious jurisdictions requires evidence from an accredited testing laboratory in the technical file, not a self-certified claim.
That evidence covers four separate disciplines, functional, performance, security and compatibility testing, each addressing a different failure mode. A regulator expects all four represented before laboratory certification, not folded into one generic QA pass.
ISTQB's CT-GT syllabus, version 1.0, published in 2019, covers math testing, platform testing, casino system testing and online gambling testing as a distinct specialism within professional QA, evidence that this is a recognised discipline with its own accredited qualification.
Operators weighing whether to build this capability in-house have two other paths: choosing a casino software platform that already carries a documented testing history, or buying a pre-tested turnkey casino platform outright, where the four disciplines already happened before the operator saw the code.
What types of testing does a casino platform need?
eCOGRA states on its own testing services page that its casino test services "include testing functionality, performance, compatibility, integration and security, to ensure the game mechanics, features, and gameplay work as stipulated by technical standards and as described to players." That sentence, from an accredited laboratory rather than a vendor blog, maps almost exactly onto the four disciplines below.
Read the source directly on eCOGRA's own testing services page, which also lists Game Engine Certification and Penetration Testing among its service lines.
Functional testing
Functional testing checks that game rules, paytables, bonus triggers and payout calculations behave exactly as documented, across every stake and currency supported. It also covers the back office and administrative tooling staff rely on daily, not only the player facing client.
Performance testing
Performance testing puts the platform under realistic load: concurrent sessions, peak volume during a major sporting event, and the latency a bet or spin can tolerate before a player notices. A platform that passes functional testing alone can still fail publicly once real traffic arrives.
Security testing
Security testing protects player data, payment credentials and transaction integrity against the wallet. It overlaps with the wider hardening practices in the online casino security guide, which addresses account takeover and infrastructure defence beyond one pre-launch cycle.
Compatibility testing
Compatibility testing confirms consistent behaviour across devices, browsers, operating systems and third party systems, including game provider and payment connections. The conformance work behind API and integration testing is its own process, covered separately.
| Testing type | What it verifies | Who typically runs it |
|---|---|---|
| Functional | Game rules, paytables, payout accuracy, back office and admin tooling | Internal QA team, or a specialist iGaming QA vendor |
| Performance | Load handling, concurrency, latency under peak betting traffic | Internal QA team, or a specialist QA vendor |
| Security | Player data protection, payment integrity, transaction security | Internal security team, a penetration testing vendor, or the certifying laboratory |
| Compatibility | Device, browser, operating system and provider integration behaviour | Internal QA team, with conformance checked against each provider's own test suite |
Category descriptions follow eCOGRA's own published testing service scope, retrieved 31 August 2026. Table cells summarise typical practice, not a laboratory's own responsibility matrix.
Where does RNG testing and certification fit in?
RNG certification is one laboratory-run component inside a wider testing programme, not the whole of it. It verifies only the random number generator itself; functional, performance, security and compatibility testing separately verify the rest of the platform built around that generator.
A platform can hold a fully valid RNG certificate and still fail every one of those four disciplines: a mispriced paytable, a session that drops under load, or an exposed payment endpoint are none of them RNG defects.
RNG certification already has its own laboratory comparison, standards map and cost figures published elsewhere on this site, so this page does not repeat them. The RNG testing guide covers that ground.
Which laboratories test and certify casino software?
Four laboratories test and certify most iGaming platforms: Gaming Laboratories International (GLI), eCOGRA, iTech Labs and BMM Testlabs. Each is accredited to ISO/IEC 17025 and recognised by a different mix of regulators, so the right laboratory is decided by target jurisdiction, not price or turnaround time.
Each publishes its own description of what its casino software testing practice covers at the platform level, not only the RNG level, worth reading directly rather than taking on trust.
Gaming Laboratories International (GLI)
GLI runs a dedicated quality assurance testing practice built on test automation, functional testing, load and performance testing, security testing and source code review. Its own materials state that its methodology follows industry best practice and that its testing experts hold ISTQB certification.
eCOGRA
eCOGRA's casino test services cover functionality, performance, compatibility, integration and security testing, confirming game mechanics, features and gameplay work as stipulated by technical standards. It also runs dedicated Game Engine Certification and Platform Certification service lines.
iTech Labs
iTech Labs describes itself as one of the leading accredited testing laboratories for the certification and quality assurance testing of online gaming systems worldwide, verified directly on itechlabs.com, a platform-level scope rather than a single-game one.
BMM Testlabs
BMM Testlabs lists independent iGaming testing, certification, platform testing, transaction monitoring, vulnerability assessment and penetration testing among its service lines, confirmed on bmm.com, well beyond RNG validation alone.
Game studios integrated through the platform, including those listed among OHS Gaming's game providers, typically carry their own certification obligations for the titles they supply, a separate exercise from the platform-wide programme described here.
GLI-19, GLI-11 or GLI-33: which standard actually applies?
Gaming Laboratories International publishes three standards operators often confuse. GLI-11, Gaming Devices v3.0, covers land-based gaming machines. GLI-19, Interactive Gaming Systems v3.0, covers online casino platforms. GLI-33, Event Wagering Systems v1.1, covers sports and event wagering systems, not casino games or platforms.
Getting the wrong one into a licence submission costs real time, and the three are easy to confuse since they share a publisher and a numbering scheme. Full definitions for related terms sit in the iGaming glossary.
GLI-19: Interactive Gaming Systems v3.0, the online platform standard
GLI-19 is the standard that actually applies to an online casino platform: the software, wallet and reporting infrastructure an operator runs online. Most platform certification work referenced on this page is measured against it.
GLI-11: Gaming Devices v3.0, the land-based machine standard
GLI-11 covers land-based gaming devices, physical slot machines and cabinets on a casino floor. It is not the standard for an online platform, even though the two are confused often, simply because they share a publisher.
GLI-33: Event Wagering Systems v1.1, the sports and event wagering standard
GLI-33 covers event wagering systems, sports betting and other event-based wagering platforms, not casino games. An online sportsbook is measured against GLI-33, not GLI-19, even where it shares infrastructure with a casino product.
| Standard | Title as published | What it actually covers |
|---|---|---|
| GLI-19 | Interactive Gaming Systems v3.0 | Online casino platforms |
| GLI-11 | Gaming Devices v3.0 | Land-based gaming machines |
| GLI-33 | Event Wagering Systems v1.1 | Sports and event wagering systems |
Standard titles and version numbers verified directly against Gaming Laboratories International's own standards index, retrieved 31 August 2026. All three rest on the same accreditation basis, ISO/IEC 17025, cited by each of the four labs above in its own accreditation claims.
How should testing be sequenced against launch and licensing?
Testing should run alongside the wider launch programme, not after it. Functional, performance, security and compatibility testing typically start as soon as a feature is stable, well before the platform is feature complete, because a defect found after laboratory submission restarts that submission's clock.
Laboratory certification sits downstream of internal testing but upstream of a licence decision: a regulator's technical file usually needs the laboratory's report attached first, which makes sequencing a compliant platform launch and testing one planning exercise, not two.
Back office and reporting tooling, used to manage campaigns, reconcile transactions and respond to a regulator, need their own testing pass. The casino back office guide covers that scope, distinct from the player-facing testing described here.
Build the test calendar backward from the date your gambling licence application is due, not forward from a development milestone. Laboratory submission queues, more than the testing itself, are usually what moves a launch date.
How long does casino software testing take, and what does it cost?
Published figures for a full platform testing and certification programme vary widely and rarely name a source. Expect functional, performance, security and compatibility testing to run largely in parallel with laboratory certification rather than after it, and get a fixed, scoped quote from each laboratory before setting a launch date.
Treat any specific dollar figure or week count for a whole-platform programme with caution unless it names its laboratory and exact scope. Most public figures describe a single game or a single RNG certification, not the platform-wide programme this page covers.
| Programme phase | Typical duration driver | Typical cost driver |
|---|---|---|
| Internal QA | Platform complexity, and how much of it runs in parallel with development | Mostly internal engineering time, or a specialist QA vendor's day rate |
| Laboratory certification | The laboratory's own submission queue, more often than the testing itself | Laboratory fees, scoped per platform and per jurisdiction, quoted directly by the lab |
| RNG certification | Priced and timed separately from the whole-platform programme | Quoted directly by the laboratory performing it, outside this table's scope |
Directional only. No dollar figure or week count is asserted here because no source in this research round names one for a whole-platform programme; laboratory-specific RNG figures sit in the RNG testing guide referenced above, not repeated here.
The honest planning approach is qualitative rather than a single number: size internal testing against the length of the final development phase, add each laboratory's own submission queue on top, and confirm a fixed, scoped quote before a launch date goes on a contract. For a platform-specific plan, an iGaming consulting engagement can help build that calendar around actual scope rather than a published average.
Frequently Asked Questions
Scope your QA and certification programme with OHS Gaming
Test plan design, laboratory sequencing, standards mapping and a dated certification calendar.
Talk to an iGaming Specialist
