Compliance Verification Tool (CVT)
The Compliance Verification Tool (CVT) is a Game-to-System (G2S) test tool designed to provide game and system 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 and systems satisfy the requirements of the G2S protocol.
This is another major step forward for the gaming industry. With the Compliance Verification Tool, suppliers will be able to quickly and easily verify G2S compliance at any stage during the development cycle. This will aid adopters by catching errors early, thereby dramatically shortening the development process and giving interoperability assurance to operators and regulators.
-Peter DeRaedt, GSA President
We are building the CVT in conjunction with the Gaming Standards Association (GSA) and our CVT Customers. The CVT is being built from the ground up to thoroughly test requirements in the G2S Requirement Checklists, which are extracted directly from the protocol documents by the G2S technical committee. Our strategy is to work closely with GSA’s Technical Director to ensure that what we build accurately tests these requirements. As each new CVT version is finalized by RadBlue, our CVT Customers and GSA’s Technical Director review the new version of the tool, along with the underlying test cases, to approve each new version before it is released.
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.
The CVT Development Portal keeps everyone up-to-date with CVT development scheduling, installers, test cases, documentation and release information. If you have any questions, please send us an email.
Frequently Asked Questions
Who should use the CVT?
The CVT is intended to be used by software developers, test engineers, casino testing centers and independent testing laboratories to verify G2S protocol compliance.
What are the benefits of CVT?
- Compliance testing at the point of software creation significantly reduces last minute identification of implementation errors, thereby speeding up time to market.
- A single CVT tool provides repeatable results, generating immediate and significant value for the industry.
- The effort required for GSA certification testing by Independent Test Labs (ITLs) is expected to drop significantly – automation will benefit the manufacturers as well as the ITLs.
- Operators significantly benefit from the increased interoperability resulting from the use of the CVT tool. They can also use the tool to perform their own testing, which lets them quickly understand the capabilities of any G2S EGM or G2S Host System.
Who is developing the test cases that the CVT uses?
RadBlue works closely with the GSA’s Technical Director to identify important G2S requirements in each class and in the review of the test cases used by the CVT. Test cases are created by RadBlue, based on the G2S Requirements Checklist, and are then thoroughly documented in the Test Case Encyclopedia.
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. 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 uses the same set of testing scenarios, which are created by RadBlue and approved by GSA.