Connect to Device Dialog

If you use BitBar and there is no BitBar API key specified in the current TestComplete project, enter the API key you will use to run tests.

Learn how to get the API Key

Learn how to get the API KeyLearn how to get the API Key

1. Log in to BitBar with your BitBar account.

   If you still do not have a BitBar account, you can sign up for a free trial.

2. Click  > My Account at the top right of the page.

3. In the My Integrations section, click API.

4. On the resulting page, click to copy your API key to the clipboard.

Click the image to enlarge it.

BitBar

Local Appium

1. On the Parameters tab, select the mobile device and a tested application for which you want to open a testing session.

   The Found devices list contains all the devices that are available for you in BitBar and that match the search criteria. If needed, you can filter the list by using the Device Type, OS Version, Resolution and Quick Search filters. Select the device to which you want to connect.

2. In the Application drop-down list box, select a mobile application for which you want to open a testing session. The application file must be either stored in the BitBar Files Library or added to the Tested Applications of the current TestComplete project. In the latter case, click Upload to BitBar to upload the application file to the BitBar Files Library and then select it in the list.

3. If needed, on the Custom parameters tab, you can specify additional capabilities to be used for the testing session. Specify the capabilities in the JSON format. For example:

   JSON

   JSON

   {
     "bitbar_project": "Automated tests",
     "bitbar_description": "Testing the Orders app"
   }

   The dialog will validate the JSON code as you are typing it.

   For the list of available capabilities, see the BitBar Documentation - Desired Capabilities.

To open the testing session and connect to it, click OK. To close the dialog without connecting any device, click Cancel.

1. In the Server URL text box, enter the URL address of your Appium server.

2. In the Application Path text editor, specify the full path to the application that you want to install on the target mobile device and from which you want to open a testing session. You can type the path manually, or you can click the ellipsis button and browse for the needed application file.

3. In the Parameters editor, enter the capabilities that describe a testing session you want to open, in the JSON format. The dialog will validate the JSON code as you are typing.

   View required capabilities

   View required capabilitiesView required capabilities

   Capability	Description	Sample value for iOS	Sample value for Android
   platformName	The name of the mobile OS where you want to open a testing session.	iOS	android
   platformVersion	The version of the mobile OS where you want to open a testing session.	14.0	11
   deviceName	The mobile device or emulator on which you want to run your test.	iPhone Simulator	Galaxy Z41
   udid	The unique identifier of the mobile device. Compulsory for physical iOS devices. To learn how to get your iOS device UDID, see Get iOS Device UDIDs.	Hxs7pLHkUZ2O3R74	80A7FO960a61Ye3h
   automationName	The test automation framework to use.	XCUITest	UIAutomator2
   app	The full file path or the URL address of your tested mobile application. For iOS devices, it could be a debug version of the application (.app) or a release version of the application (.ipa). For Android devices, it is .apk files.	.app (for emulators) .ipa (for physical devices)	.apk

   For information on all available capabilities, see Appium Desired Capabilities.

To open the testing session and connect to it, click OK. To close the dialog without connecting any device, click Cancel.