Once the integration is completed, you can run our automated tests and confirm that you passed them all. After you passed all the tests, please send a screenshot of the tests status (just the part where it says how many tests you passed) to the CWS Support representative.

Automated Test tool can be found here: https://www.cryptoclub.casino/plugins/unit_testing/games_rgs/

⚠️IMPORTANT: Please make sure to open the testing link in incognito mode in your browser or to use a different browser than the one used for playing the games.

What the tool needs

Your Operator ID, the API username and password of your account, a player username that exists on your platform, and the API version you integrated. The tool then calls your wallet endpoints exactly the way the games do, with the same requests described in Receive Data from RGS-CWS API - Seamless Wallet.

What it checks

  • Get balance — your endpoint answers the balance request for the player.
  • Bet, then win — a round in the order a slot plays it.
  • Bet, bet again, then win — a second bet on the same round, as card games do.
  • Idempotency on bets — the same bet transaction ID sent twice must be processed once.
  • Idempotency on wins — the same win transaction ID sent twice must be processed once.
  • Natural free spins — a bet, a zero win on the main spin, then the total win of the free spins.
  • Cancel bet and cancel win on the same gameplay ID, and a repeated cancel that must not be processed again.
  • Bet too high — a bet above the balance must be refused.
  • Corrupted JSON — a malformed request must be rejected, not processed.

Every test shows the request sent, the answer received and a pass or fail mark. Fix the failed ones, run the suite again, and send the summary screenshot once every test passes. The rules behind the checks — transaction IDs, idempotency, timeouts and refused wins — are described in the Receiving Data from our API collection.

Automated testing. A game opens on its start screen and waits for one player click (PLAY / tap to start — browsers allow sound only after a click). A test robot must click it before it can spin; the spin button is part of the game's canvas, so drive it by position or by the game's visible state, not by an HTML element.