Web Specific Capabilities
Web specific capabilities are settings that you can customize in web automation tools and frameworks to control how web browsers behave during your tests. They help you adjust the behavior of web applications in different browser environments, ensuring that your tests are tailored to your specific needs.
Custom BitBar Capabilities
Capability | Value Type | Requirement | Description |
---|---|---|---|
| 32-character alphanumeric string | Required | A security parameter that allows users to provide a unique authentication key or token necessary to access and interact with specific services or resources. This capability is crucial for secure access and authorization when working with external APIs, services, or protected data. The API key is available in the My Account view. |
| String | Optional [mobiles only] | Available in BitBar Public Cloud, BitBar Private Cloud, and BitBar Enterprise, empowers you to connect to an older version of the Appium server when the need arises. This ensures compatibility and flexibility in your testing setup. Default value: |
| String | Optional | Enables you to provide a project description. For example, |
| String | Required [mobiles only] | The distinctive identifier assigned to a device within BitBar. Alternatively, you can employ a script to search for devices based on specific properties, such as using a Python script as an example. When you use the |
| Integer | Optional | The capability enables you to initiate a session with a single free device randomly chosen from a specific device group. For example, by indicating |
| Boolean | Optional [mobiles only] | Determines how a system selects a device based on the provided name. When set to When you use the |
| Integer | Optional | Available in BitBar Public Cloud, BitBar Private Cloud, and BitBar Enterprise, provides users the flexibility to utilize a testing framework other than the default. This feature is particularly useful for Private Cloud users managing various projects with different framework configurations. The default value is set to the default framework ID (for example, |
| URL | Optional | Defines the endpoint, for which the REST call will be executed after the test finishes. |
| Integer | Optional | Designates the maximum duration of inactivity in seconds that a test session or automation framework will allow before automatically ending the session. This capability ensures efficient resource management by terminating idle sessions to free up resources for other tasks. |
| String | Optional [mobiles only] | The specific device language, recognized by the Locale ID from the |
| Integer | Optional | Specifies the waiting duration in seconds (maximum 60) that the broker should wait for a new Appium session after the last call to |
| String | Optional [desktops only] | Defines the target device's operating system (OS) version for testing, ensuring compatibility and accuracy with the specified OS version during test execution. |
| String | Optional | The project name that will be displayed on the Web UI. If none is provided, the Cloud sets a Project X name to your run. For example, |
| String | Optional [desktops only] | Specifies the screen's dimensions, usually expressed as width and height (for example, Supported resolutions
|
| String | Optional | Provides a user-defined name or identifier for a specific test within a testing environment. It allows testers to label and distinguish individual tests, making it easier to track and identify test results, especially in cases involving multiple tests or test suites. |
| String | Optional | The user-provided name for each test run within a project. If a name is not specified, the Cloud service assigns a default name. For example, |
| Integer | Optional | Defines the maximum duration, in seconds, that is allowed for the complete execution of a test. This timeout is adjustable for users with an active plan or subscription and helps ensure that test execution does not exceed a specified time limit. Default value: |
| String | Optional | Enables users to define the specific time zone for a test, ensuring accurate testing under the chosen geographical time zone. This is particularly important for scenarios where time-related factors play a key role. |
Standard Selenium Capabilities
Refer to the Selenium documentation to access the comprehensive list of available capabilities for Selenium.
Here's a list of selected Selenium capabilities with extended functionality.
Capability | Value Type | Requirement | Description |
---|---|---|---|
| String | Optional | Specifies the browser version to run the test on. If not specified, the latest stable supported version will be used. You can also use |
Standard Appium Capabilities
Refer to the Appium documentation to access the comprehensive list of available capabilities for Appium.