ATTT – Automated Test Suite for GB ATMs and CAS (using SikuliX)

This repository provides a publicly available automated tests suite for General Bytes ATMs and CAS.

Overview

General Bytes (GB) has developed the Automated Terminal Testing Tool (ATTT) to help operators efficiently automate testing of their BATM fleet.
ATTT ensures error-free, stable operation across various configurations, reducing testing time from days to hours.

Tip

For more details, refer to the Knowledge Base.

Use Cases

• Verifying new pre-production BATM software releases
• Automatically checking transaction flows
• Testing negative scenarios and other cases

Requirements

• Java Development Kit (JDK) 8 (OpenJDK or Oracle JDK/JRE)

• SikuliX IDE 2.0.5 (Download here)

  Officially tested on JDK 8; Java 9+ is supported but may require additional JVM flags

• 64-bit operating system (Windows, macOS or Linux) — SikuliX supports only 64-bit systems

• FAT32-formatted USB flash drive

• ATTT activation provided by GB Support

Security

• Communication with the ATTT server is only possible using unique client certificates issued by GB.
• Certificates must be physically uploaded to each terminal using a FAT32-formatted USB flash drive.

Note

A FAT32-formatted USB flash drive is required to upload certificate to the terminal during activation.

• The ATTT system has been independently security audited.

Architecture

Key Components:

• ATTT Connector
  Streams the terminal’s screen to the ATTT server and processes click events, virtual testing cash insertions, QR scans, and keyboard events.

• ATTT Server
  Hosted and maintained by GB; enables remote control of terminals via a web browser.

• SikuliX
  Automation tool that lets QA engineers write Python scripts for visual recognition and interaction with terminal screens.

Prerequisites

Clone this repository to your local machine:

git clone https://github.com/GENERALBYTESCOM/batm_test_public.git

Setup & Activation

Warning

This tool is not recommended for use on terminals connected to production CAS servers. Proceed at your own risk.

Risks to keep in mind when testing production configurations:

• Sending real cryptocurrency to wallets without any fiat deposited
• Inadvertent dispensing of cash during automated sell flows

1. Request Activation

Contact GB Support to request ATTT server access by providing your terminal serial numbers and user email addresses. Support portal: Create a Support Ticket

2. Prepare CAS Settings

Before setting up terminals, configure the following settings in CAS.

2.1.Create a new AML/KYC Setting:

• Select the following checkboxes (✓):
  • Reject PEPs
  • Allow withdrawals only for the same identity as sell transaction
  • Verify Wallet Ownership

KYC configuration for registered/unregistered customers

• Set Default Fiat Currency to USD - United States dollar
• For Registered and Unregistered Customers:
  • Require Cellphone Number

Customer Limits

• Anonymous: Cash Limit Per Transaction = 500.00 (check Enable cash payments)
• Unregistered: Cash Limit Per Transaction = 1000.00 (check Enable cash payments)
• Registered: Cash Limit Per Transaction = 5000.00 (check Enable cash payments)
• In Total Terminal Limits:
  • Cash Limit Per Day (For Buy & Sell) = 100000.00

2.2. Create a new Fiat Settings:

• Fiat Currency: USD - United States dollar
• Accept All Banknotes

2.3. Create a new Crypto Settings:

• For each supported currency: BTC, LBTC, LTC, ETH.
• Configuration Cash Currency: USD.

Warning

The Configuration Cash Currency must remain consistent across all CAS components. Any mismatch between related currency settings is not supported and may prevent proper operation of transactions or configurations.

2.3.1 Buy Settings:

• Minimum Buy Cash Amount per Transaction: 100.00
• Minimum Buy Card Amount per Transaction: 0.00
• Buy Rate Source: Demo Rate Source
• Hot Wallet Buy: Demo Wallet
• Exchange Buy: Demo Exchange
• Buy Profit (%): 10.00%
• Fixed Transaction Fee: 10.00

2.3.2 Sell Settings (except ETH):

• Sell Rate Source: Demo Rate Source
• Hot Wallet Sell: Demo Wallet
• Exchange Sell: Demo Exchange
• Sell Strategy - 1: Receive coins to the Hot Wallet
• Sell Profit (%): 10.00%
• Fixed Transaction Fee: 10.00
• Invalid Payments Address: 15nvjrMZbxyLAAr9RAnqkoMXcFriAmbeLE

Note

ETH does not support sell wallets, thus sell transactions for ETH are not tested.

2.4. Create a new Discount:

• Discount Type: Discount from fee
• Set all discount values (Discount From Buy Profit Fee, Discount From Sell Profit Fee, Buy Fixed Fee Discount, Sell Fixed Fee Discount) to 10.00%
• Crypto Currencies: BTC, LBTC, LTC, ETH
• Set Valid From and Valid To dates to define the period the discount is active (e.g., 01.09.2024 – 01.02.2030)

2.5. Create a new Location:

• Create and select the actual location of your BATM.
• The location's capacity must be equal to or greater than the number of testing terminals.

3. Configure Terminal Details in CAS

3.1. Custom Strings (on the terminal detail page):

• Add the attt flag to the special_configuration custom string.

Warning

Without this flag, ATTT will not be enabled on the terminal!

• Configure following custom strings (Values are case-sensitive: must match exactly):
  • terms_and_conditions: TERMS AND CONDITIONS
  • scam_disclaimer: SCAM DISCLAIMER
  • custom_pep_question: PEP QUESTION
  • required_disclosures_text: REQUIRED DISCLOSURES
  • privacy_policy: PRIVACY POLICY
  • marketing_opt_in_agreement_text: Marketing agreement text. Agree?

3.2. Set previously created configurations:

• AML/KYC Setting from step 2.1.
• Fiat Settings from step 2.2.
• Crypto Settings from step 2.3.
• Discount from step 2.4.
• Location from step 2.5.

3.3. Main Cash Currency: USD - United States dollar

3.4 Crypto Currencies: Select BTC, LBTC, LTC, ETH

3.5 Administration Settings:

Select the following checkboxes (✓):

• Customer Can Cancel Transaction
• Show Marketing Agreement Screen
• Blur Detection Limit: 1

3.6. Languages:

• Default Language: en - English
• Preferred Languages: cs - Czech, de - German, es - Spanish, ar - Arabic, fi - Finnish, ja - Japanese, fr - French, bg - Bulgarian, el - Greek, et - Estonian, hr - Croatian, hu - Hungarian, hy - Armenian, it - Italian, kk - Kazakh, ko - Korean, lv - Latvian, ka - Georgian, mk - Macedonian, lt - Lithuanian, nl - Dutch, no - Norwegian, pl - Polish, pt - Portuguese, sk - Slovak.

3.7. Printing Settings:

• Select the following checkboxes (✓):
  • Disable Printer Warnings
• Print Buy Receipt — set value to Never
• Print Withdrawal Receipt — set value to Never
• Sell Tickets Delivery: set to None (to be used with withdrawal using phone number)

Tip

Disabling printer warnings and setting receipt printing to “Never” or “None” helps prevent unwanted paper slips from being printed or falling out of the terminal.

3.8. Publish Settings:

The Publish checkbox must NOT be selected.

3.9. Terminal Template:

You can save all required settings in a Terminal Template and select it in the "Use Terminal Template" field, instead of configuring each setting manually.

Note

Reboot the terminal after configuration (recommended, but not required).

4. Upload Activation Keys (on the BATM terminal)

Warning

Each terminal has its own unique keystore file (attt.bks).
You must repeat this step for every terminal individually, using the correct attt.bks file provided specifically for that terminal.
If you upload a keystore meant for another terminal, ATTT will not work correctly.

• Extract the activation ZIP archive (received from GB Support) and copy the extracted file to a FAT32-formatted USB drive. The extracted file must be named attt.bks
• On the BATM terminal:
  Enter the Advanced Administration menu.

Tip

For access instructions, see Access ADVANCED Administration

• Click on the UPLOAD ATTT KEYS button.
• Insert the USB drive into any available USB port on the BATM. If all USB ports are in use, you may temporarily disconnect the printer. After successful upload, a notification will appear.
• Remove the USB drive (and reconnect the printer if necessary).
• Press the button ENABLE ATTT.
  The terminal will now establish a secure connection to the ATTT server.

Caution

After terminal reboot or upgrade, you must enter the Advanced Administration menu and press the button ENABLE ATTT again.
There is no need to re-upload the keystore file (attt.bks).
If you skip this step, remote testing will NOT be possible: the terminal will not be able to connect to the ATTT server, and automated tests will not function.

Warning

The UPLOAD ATTT KEYS option will only be visible if the attt flag is set in the special_configuration custom string for this terminal in CAS.

5. Access a BATM from the ATTT Server

Before running tests, you must configure access to the ATTT server by importing a client certificate into your web browser.

5.1. Request a Certificate

To access the ATTT server, request a client certificate (in .p12 format) and the associated password from GB Support.

Tip

Request the certificate and password from GB Support as described from step 1.

5.2. Import the Certificate into Your Browser

You can use any major browser that supports client certificate authentication (e.g., Google Chrome, Mozilla Firefox). Below are general instructions that work across browsers:

• Open your browser. Go to Settings → Security → Manage certificates:
  • In the Your Certificates tab, click Import.
  • Select the .p12 file received from GB Support.
  • Enter the password provided along with the file.
  • Confirm import. The certificate will now appear in your certificate list.

Note

This certificate is required to establish a secure connection to the ATTT server. Without it, you will not be able to access the login page.

5.3. Log in to the ATTT Server

• Go to the ATTT server website at https://attt.generalbytes.com.
• Enter your Username and Password, then click Log In.
• Open your authenticator app and enter the OTP code.
• Click Submit OTP.
• You will now see a list of BATMs.
• Find the terminal you wish to test.
• Click at the Control terminal button to access the BATM’s console.

Running Tests

• Start SikuliX IDE:
  • Open a terminal or command prompt.
  • Navigate to the folder where SikuliX IDE was downloaded (for example, ~/Downloads).
• Run:

  java -jar sikulixide-2.0.5.jar

• In SikuliX IDE:
  • Click File → Open
  • Select and open a test file from the cloned batm_test_public repository.
  • Click the Run button.

Troubleshooting

• Ensure screen resolution and display scaling are set to 100%.
• Supported and tested screen resolutions: 1920×1080 (16:9) 1600×900 (16:9) 1366×768 (16:9) 1280×720 (16:9) 1680×1050 (16:10) 1440×900 (16:10) 1280×800 (16:10)
• Tests are optimized for these screen resolutions. Using other resolutions may reduce the reliability of SikuliX visual matching.