Project Properties - BitBar and Local Appium Options

Applies to TestComplete 15.10, last modified on November 30, 2021

You use the BitBar & Local Appium project properties to bind your TestComplete project to a BitBar account that you will use to run automated mobile tests in the BitBar device cloud.

Requirements
  • An active license for the TestComplete Mobile module.

  • The Appium Support plugin must be enabled in TestComplete. The plugin is installed and enabled by default. In the File > Install Extensions dialog, you can find the plugin in the Mobile group.

  • You must have a valid BitBar account.

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

To view or modify properties
  1. Select Tools > Current Project Properties from the TestComplete menu.

    – or –

    Double-click the project in the Project Explorer. In the project editor, switch to the Properties tab.

    – or –

    From the context menu of the project in the Project Explorer, select Edit > Properties.

  2. In the tree on the left of the project properties editor, select BitBar.

TestComplete Project Properties - BitBar

Click the image to enlarge it.

Available properties
  • API key - A secret token that you will use to access the BitBar API.

    Learn how to get the API key

    You can click Test Connection to make sure that TestComplete can access the BitBar API using the specified key.

  • Criteria for finding BitBar device - The search criteria that TestComplete will use to find a mobile device to connect to if the exact device specified in the test is not available. To set the criteria, click Edit iOS criteria or Edit Android criteria correspondingly and specify the desired criteria in the resulting Edit Criteria for Finding Device dialog.

    These criteria are only effective if:

    – or –

    • In script tests, the Mobile.ConnectDevice method has the bitbar_findDevice capability set to true.

  • New command timeout - The number of seconds that a connected mobile device waits for an action over it. If there are no actions before the timeout elapses, the testing session on the device will be closed and the device will be disconnected.

    Note: This does not affect exploring the tested mobile applications by using the Object Browser and Object Spy. The device will remain connected until you disconnect from it explicitly.

See Also

About Mobile Tests
Project Properties - Mobile Devices Options

Highlight search results