Kobiton supports web, native, and hybrid applications.
Yes, an organization's admin user can invite multiple users to be part of the organization. The admin user is the only user who can add or remove users from the organization's account. An organization can have multiple admins.
Kobiton supports application files up to 1GB.
For Public Cloud devices, Kobiton automatically uninstalls the application at the end of each manual or automation test session. However, data generated during the test may not deleted. For example, if you log into a website and don't log out during the test, the cookie remains on the machine and the next user may be able to log into the site.
For Private and Local lab devices, each organization can define their cleanup policy by team.
Yes, interruptions can happen due to adverse network conditions. In some cases, devices may restart before your test completes.
A list of ADB Tunnel supported devices is available here.
Yes, as a part of the Kobiton cloud, Kobiton and its service providers may collect, process, store, modify, aggregate and otherwise use statistics and other data regarding your use of the Kobiton cloud.
For Public Devices and Private/Local devices with a cleanup policy, Kobiton automatically uninstalls tested applications after a test session, but does retain test history, including session name, description, screenshots, and logs until your account is cancelled. However, you can delete the test session at any time.
Yes, but if you prefer to keep and use your application's original certificate, you'll need to add Kobiton's cloud iOS device's UDID to the Provisioned Devices in the application's certificate.
Kobiton has a large (and growing) selection of iOS and Android devices, including latest and older devices.
Available devices can be accessed on Device List.
You can retest on the same device, however Kobiton assigns cloud devices based on your desired configuration, which does not guarantee tests will run on the same device for future test sessions.
Yes, to request a specific device, open a support ticket and include OS information. Requests are fulfilled based on demand.
Yes, devices may have manufacturer or carrier pre-installed applications.
Calls and SMS messages can be send from devices on Enterprise accounts with SIM cards. Public cloud devices do not support this feature.
Yes, you can use the device cameras- front and rear-facing cameras, but may be dark or blurry because of the way devices are mounted.
For automated tests, concurrent tests are the number of devices executing your test scripts in parallel during the test session.
No.
Yes, you can change the device location on both Android and iOS devices during manual test sessions. Automation location changes are supported on Android only; iOS is soon to follow.
Yes, currently you can only change the device timezone on Android devices during manual test sessions.
Yes, most session recordings are available to watch or download by going to session > video.
Yes, API is available here.
There are two contexts for Hybrid app: native + WebView.
On Android v5, v6, list page source on WebView is considered as native, so we can get the WebView elements as native elements normally. eg: java
driver.findElementByXPath(
"//android.widget.Button[@text='LOGIN' or @content-desc='LOGIN']")
.click(); On Android v7, WebView elements cannot be retrieved via native context, so if your script finds the WebView element while your app is still on native context => failure => timeout. In this case, just try to switch to WebView context and follow HTML elements source tree, then we can find the element appropriately. eg: java
driver.context(
"WEBVIEW_xxxxxx");
driver.findElementByXPath(
"//button/span[contains(normalize-space(text()),'Login')]"
).click(); Having done that, if your app UI is loaded on Chrome, so we must switch back to Native context in order to get element java
driver.context("NATIVE_APP");For Android v8, we are using Appium 1.13.0, switch to WebView context is NOT supported as well.
Please submit a support ticket either via the ? in the left-hand navigation of the Portal or by sending an email to support@kobiton.com
In the support ticket, include the device name + UDID for each device that you want to upgrade.
Things to consider:
- Check whether the Kobiton platform supports the new OS by checking our Supported Versions
- Devices can only be upgraded to the most recent general availability version of the OS (or the most recent beta version of the OS). Apple and Android do not allow picking lower versions.
- Downgrades are not supported by Apple and Android. So, be sure the rest of your teammates support updating the OS for a device!
- Some device models cannot be upgraded past a certain version.
- Some new iOS versions require an upgrade to the Xcode version that runs on the server hosting your devices. If an Xcode upgrade is required, we'll need to coordinate downtime to support the Xcode upgrade. All devices hosted by that particular server would be unavailable during the Xcode upgrade.
- When Android rolls out a new major OS version, the Google Pixel is often the first device that can support it. Other device manufacturers have their own timing to support the new version.