Remote Automation for Windows

CukeTest supports remote automation for Windows applications. This means you can run CukeTest on one computer while controlling a Windows application on another computer.

How it works and scenarios

The core of remote automation is the CukeTest Worker Service. You need to start this service on the remote Windows computer where the application under test is installed, and then the local CukeTest script connects to the service over the network and sends automation instructions.

This remote automation method is particularly suitable for the following scenarios:

• Cross-platform testing: Run CukeTest scripts on a local Linux or macOS system to automate and control applications on a remote Windows computer.
• 32-bit application automation: The desktop version of CukeTest is a 64-bit application, but in a Windows 32-bit environment, we only provide the Worker service for remote execution. Therefore, if you need to automate a 32-bit Windows application, you can achieve this by connecting a 64-bit CukeTest to the Worker service in the 32-bit environment.

To start the Worker service, simply execute the following in the command line of the remote computer:

cuketest worker

For more details on remote automation, please refer to the Remote Automation documentation.