Get started

Get AltTester® Desktop

You can download AltTester® Desktop from our website.

Upgrade to AltTester® Desktop Pro

You can upgrade the AltTester® Desktop to the Pro version by either purchasing a Pro subscription or starting a free trial directly from our website.

Once you’ve obtained the Pro license subscription, you can activate it in AltTester® Desktop app using the Activate Pro license button located in the top-right corner of the application header.

Note

After a successful activation, the license will be stored on your device. There’s no need to reactivate the license each time you open the application. AltTester® Desktop will automatically handle activation and deactivation processes upon application open and close, respectively

Note

If you’re running AltTester® Server in the terminal (see Advanced Usage), please note that there might be a delay of up to 5 minutes in license deactivation after closing the terminal process. This delay won’t affect the reactivation process if AltTester® Server is reopened within this timeframe.

Connect to a game build

Prerequisite:

Note

The AltTester® Desktop needs all scenes to be included in the build. Even if you are loading your scenes from AssetBundle. Make sure to include all scenes in the build. See also known issues.

Connect to the built-in AltTester® Server

Connection panel

Through built-in server we refer to the AltTester® Server placed inside the AltTester® Desktop. Your instrumented build will connect to the server in order to communicate with AltTester® Desktop.

  • AltTester® Server Status: shows whether the server is running or idle. You can switch between states using the toggle to the right.

  • AltTester® Server Port: should have the same value as your instrumented build’s port.

  • Connected Apps List: displays information about the instrumented apps that are connected to the local server. You can copy-paste any of the tags (appName, platform etc.) and use them in your automated tests to select the app to run your tests on. The appId tag can be used to uniquely identify an app and the status tag informs you that in case you have an older version of instrumented app then the live update won’t work.

Important

If you want to run your tests using the AltTester® Server, start the AltTester® Desktop and make sure that the AltTester® Server Status says running. There is no need to press the Inspect App button.

Important

In case you are running your app on a device, make sure both the machine the AltTester® Desktop is running on and the device with the mobile game are in the same network.

Note

In order to restart the AltTester® Server Port, after changing the port you either have to press Enter or click outside of the input field to see any effect.

Connect to a remote AltTester® Server

Connection panel

Through remote server we refer to a server that is not part of the AltTester® Desktop (ex. server running in the cloud).

  • AltTester® Server Host: is the remote host the server is running on.

  • AltTester® Server Port: should have the same value as your instrumented build’s port.

  • Connected Apps List: displays information about the instrumented apps that are connected to the remote server. You can copy-paste any of the tags (appName, platform etc.) and use them in your automated tests to select the app to run your tests on. The appId tag can be used to uniquely identify an app and the status tag informs you that in case you have an older version of instrumented app then the live update won’t work.

Important

With our Community plan, you can connect concurrently to the AltTester® Server a maximum of 1 instrumented app and 1 driver. With our Pro plan, the number of concurrent connections is 2 (for instance, you can have 1 AltTester® Desktop and 1 set of tests, or 2 sets of tests executed in the same time). In case you need more concurrent connections, you can buy more from our site or you can contact us.

Connect through IP

Prerequisite:

Start AltTester® Desktop on your machine.

In case you are running the instrumented app on the same machine, the IP displayed in the green popup (inside the app) should be set to 127.0.0.1 (localhost); otherwise, if you are running your app on a device, you have to specify the IP of your machine inside the IP field of the green popup.

After this, press Inspect App in the AltTester® Desktop.

Connect through reverse port forwarding

Prerequisite:

Start AltTester® Desktop on your machine.

In case you are running the instrumented app on your machine, you do not need reverse port forwarding. On the other hand, if you are running your app on an Android device, you will need to do reverse port forwarding.

How to set up reverse port forwarding for Android?

  1. You need to install ADB.

  2. Type adb reverse tcp:device_port tcp:local_port in the command line. Ex: adb reverse tcp:13000 tcp:13000

  3. Remember to remove reverse port forwarding when you no longer need it by adb reverse --remove tcp:device_port. Ex: adb reverse --remove tcp:13000

After this, press Inspect App in the AltTester® Desktop.

Note

If you want to connect your instrumented app that runs on an IPhone to the AltTester® Desktop, you can do it by connecting through IP as reverse port forwarding is not available on iOS with iProxy.