|Information in this topic applies to mobile applications.|
The options of the Android dialog affect testing of Android applications. To invoke the dialog, select Tools | Options from the TestComplete main menu, and then choose Engines | Mobile | Android from the tree displayed on the left of the subsequent Options dialog.
You can change the following options:
Auto-wait timeout for Android devices, s - This option is effective during the test run. It specifies the number of seconds TestComplete will wait for a response from the tested Android device when executing a test command. If TestComplete does not receive a response during the specified time, it considers the simulated test commands failed. Default: 60 seconds.
Path to Android SDK - Specifies the path to the Android SDK files installed on the current computer. TestComplete needs this path to find adb.exe, which is the executable of Android Debug Bridge that TestComplete uses to work with Android devices, emulators and virtual machines.
The internal structure of SDK folders can vary from one release to another. It is recommended to specify the folder that contains the adb.exe file.
Path to Java Runtime - Specifies the folder where Java Development Kit (JDK) or Java Runtime Environment (JRE) is installed. For example, C:\Program Files\Java\jdk1.7.0_45 or C:\Program Files\Java\jre7.
Terminate ADB if it does not respond - TestComplete works with Android devices via Android Debug Bridge (ADB). This setting specifies whether TestComplete will terminate the adb.exe process when the latter stops responding to TestComplete requests.
ADB can stop responding for a number of reasons. Typically, this happens if you have too many devices connected to your computer (see Possible Issues With Android Applications (Legacy)). If TestComplete detects an issue and if this setting is on (default), TestComplete terminates the current ADB process and launches a new ADB instance. This approach helps you decrease the waiting time and continue working faster. The disadvantage of this is that connections to all the devices will be broken. This may cause problems with tests or other software that are working with these devices via this ADB instance.
If you disable the option, TestComplete will not terminate the ADB process automatically. It will display an error message informing you about the issue, so that you can resolve it manually. We recommend that you disable the option if you have some important software that uses the ADB instance (for instance, it gets some logs from the device), and for which automatic disconnection will cause problems.