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.
Kobiton supports application files up to 500 MB.
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.
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.
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 your. 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. 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 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.