Motivation

General Bytes developed a framework of tools to help Operators automate BATM testing, ensuring that the operation of their BATM is error-free and stable. Although GB tests their software 24/7 for bugs and code quality, it is practically impossible to test all of the possible configuration combinations that Operators can set. With the hundreds of settings in CAS and BATMs, every Operator has a unique setup. How does an Operator test that their BATMs are behaving as expected in all of those combinations? ATTT is the answer.

Quality assurance at GB side

Every time GB adds a new feature into the product, or fixes a bug - the following flow is executed:

Engineer writes new code, and tests their new feature in a separate development branch.
Engineer’s code is reviewed by other engineers, corrections are made and code is added (merged) into the next new release. Security concerns are evaluated.
The upcoming new release (RC - release candidate) is automatically tested on 1 million transactions every night to ensure that the server performance and stability hasn’t been impacted.
Each newly added feature/bug fix in the RC is again manually tested by a QA engineer. The QA engineer will also check whether the implementation is easy to use and foolproof.
A standard test suite is executed by a QA engineer to verify that a BATM can connect to a server using a VPN, perform transactions and upgrade (to an even newer RC).
When all features are approved by QA, the release is signed with the GB key and distribution of the release to the Operators begins.
The release is no longer a “candidate”, but an official supported release - and is placed in our secure storage - where it is downloaded by the Operators.

Quality assurance on the Operator's side

Before performing an upgrade of the production environment, the Operator must follow the pre-upgrade best practices, which includes the evaluation of a new release in testing and pre-production environments.

Operator recommendations include:

Test new features on your testing/development environment to ensure you understand
1. what the features are for,
2. how to use and configure them, and
3. how they impact your operation.
Test on the Operator’s pre-production environment. Ascertain that your BATMs perform transactions as expected when an identical production system configuration is set. This step can save hours of human effort, as your staff would need to check every possible choice the customer can make at the BATM, and you need to be sure that all options work.

ATTT makes this process 1000x more efficient, helping you to qualify new releases in a matter of hours (instead of days).

How ATTT works

Connector and server

GB has built an ATTT connector into its BATM software enabling BATMs to transmit the screen contents to the ATTT server (centrally operated and maintained by GB). You (the ATTT user) is then able to login to the ATTT server via a browser, and not only see the contents of the screen - but also to click on the screen - causing clicks to be delivered back to the machine as if they were your customer’s finger touch events. You are not only able to click on the screen but also able to insert virtual testing cash, or send QR codes and even keyboard events. This enables your QA engineer to perform tests from home - but there is more (read below)!

Automation

Helping your QA engineer to test your machine’s UI remotely is not the entire goal of ATTT. The goal is to perform these remote tests automatically. For that GB recommends using an existing tool called SikuliX, which enables your QA engineers to write Python scripts to look for the texts and images at the BATM’s screen - and automatically clicks on them - simulating the customer’s interaction. This enables you to not only simulate and test successful transactions at the ATM but also test negative scenarios, e.g. the reaction of the machine to scanning an address that is banned, going over the limits, and all other scenarios that your QA engineer didn’t have the time to test when they were doing all tests manually.

GB also delivers their own set of the tests that you can begin to build on.

Activation

By default (for security and privacy reasons), the ATTT connector will not connect to the ATTT server.

The ATTT feature must first be activated at the BATM, in CAS, and at the ATTT server.

Steps required:

Choose and dedicate one or more machines for ATTT testing.
- We recommend having at least one machine of each model in your fleet.
- Machines and CAS need to be on version 20240901+.
Connect selected machines to CAS and collect serial numbers of the machines.
1. We strongly discourage you from connecting machines to production CAS for security reasons.
Identify persons in your organization that will have access to ATTT server and collect their email addresses.
Contact GB support requesting access to ATTT server for the selected serial numbers and the selected email addresses: Create a Support Ticket
GB will send you an activation archive, and invitation emails to your ATTT users.
Add “attt" to the Custom String “special configuration” for each Terminal that you wish to connect to the ATTT server, and reboot the machine. See: Custom Strings
Extract the contents of the activation archive (ZIP) received from GB support to a flash drive.
- Flash drive needs to be formatted as FAT32 filesystem (not ex-FAT).
Take out the cashbox from the machine and enter the advanced administration menu.
Insert the flash drive into the machine’s free USB slot.
- You may need to disconnect a printer for a while if none of the USB ports are free.
Click on UPLOAD ATTT KEYS button to copy the activation keys from the flash drive.
Remove the flash drive from the USB port (and reconnect the printer if required).
Now press (in administration) the button ENABLE ATTT .
- After pressing the button it will connect to the ATTT server.
- No button “ENABLE ATTT"? Check your flash drive and activation keys.
The BATM is now activated and connected to the ATTT server.
- Activation is valid for one year and must be reactivated every year with new activation files.
Login to the ATTT server and click on the BATM’s serial number from the list of BATM serial numbers.
- You should now see what is displayed at the BATM and be able to perform clicks.
Try manually performing a transaction.
Install SikuliX tool and start writing your tests.

Deactivation

The ATTT connector can be deactivated in advanced administration at the BATM by clicking at the button DISABLE ATTT.

Rebooting the BATM deactivates the connection to the ATTT server.
You’ll need to return to the BATM and press ENABLE ATTT button again.

Security

The BATM is connected to GB’s ATTT server only when the ATTT connector is activated at the BATM.

Activation requires:

Physical access to the BATM’s cashbox.
Enabling the feature in CAS.
Activation at the ATTT server performed by GB.

The BATM connects to GB’s ATTT server using HTTPs Websocket protocol using client certificates issued by GB uniquely for each BATM’s serial number. Certificates can only be transferred into the machine using a USB drive.

Communication with the ATTT server is NOT routed via the built-in VPN network, but it is transmitted directly via open Internet to ATTT server listening at port 7741.

Configure your network firewall settings accordingly.

ATTT functionality has been security audited by an independent security auditor company.

Accessing BATM from ATTT server

Once you’ve received the activation keys from GB, and you’ve connected your BATM to the ATTT server -you can login to the ATTT server at https://attt.generalbytes.com

List of our BATMs

By clicking at the “Control terminal” button you will enter the BATM’s console.

Terminal Console

Now you can control the BATM remotely by clicking into the image. Additionally you can virtually insert banknotes, scan QRs, or send keyboard characters.