Compliance Verification Tool (CVT)
Incredibly innovative gaming solutions.

Compliance Verification Tool (CVT)

The Compliance Verification Tool (CVT) is a Game-to-System (G2S) test tool designed to provide game developers, test engineers, regulators and operators with a tool that quickly verifies that gaming products meet a basic standard for G2S implementation.

The CVT helps ensure interoperability, provides a cost-effective way for vendors to quickly get their products to market, and is the definitive method for assessing whether games  satisfy the requirements of the G2S protocol.

CVT

System Requirements:

  • Operating System: 64-bit version of Windows 7, 8, 10 or  Windows Server
  • Four cores (minimum)
  • Memory: 8 GB (minimum)
  • Disk Space: 250 MB
Compliance Verfication Tool (CVT) Downloads:
Version 62 | 64-bit Windows


The short-term goal for the CVT is to bring test-driven development to the masses by having engineers run the CVT against their EGMs on a daily basis to discover G2S problems as soon as they are introduced. Longer-term, the goal for the CVT is to become a tool that can be used for certifying the G2S protocol when run by a certified lab.

Does the CVT replace existing RadBlue products, such as RST or RGS?

No. The goal, and subsequent functionality, of the CVT is different from other RadBlue tools.

RadBlue tools, such as RST and RGS, allow you to test any scenario you like, either on a command basis or through a custom script. They are designed to give you the flexibility to do both positive and negative testing, and to really wring-out any performance issues in a product. This flexibility is crucial to test performance and edge conditions specific to your products and network environment.

The CVT, on the other hand, is intended to ensure that a product has been implemented in a way that is consistent with GSA specification standards according to a requirement authority. The requirement authority selects the requirements that will be tested.  RadBlue then works with the requirement authority to define the test scripts.  Since the focus of the CVT is interoperability, there is no flexibility in the content of the test scripts it runs. Everyone who uses the CVT with the same requirement authority uses the same set of testing scenarios.