No you don’t, unless you choose to use a test framework that specifically requires this.
Each phone is cleaned of apps that are not expected to be there.
Android browser: we do remove any browser app local data implying there will not be any navigation data on next session. We also uninstall all apps that is possible to uninstall and remove files we know are created during tests.
iOS browser: we rely on iOS’s own browser history cleaning services to revert Safari to an initial state.
Each device is put through a clean up phase after each test run. Regardless of all these efforts some files or data may stay hidden somewhere on the device in the Public Cloud. For a truly private environment we recommend a Private or Enterprise Cloud installation.
The app needs to be an ad-hoc distribution developer debug build. You can find more information here.
For Public cloud the only way is for the customer servers to whitelist our public IPs to allow connections from our devices. For private clouds or dedicated devices we can implement a VPN or proxy connection. In on-premise setups the customer has complete freedom on implementing the networking as needed.
This is not supported in Public Cloud. There is support for this in Private and Enterprise environments.
For Public Cloud you could try to mock the BLE connection data as required by the tests. Otherwise we can pair devices to required Bluetooth devices in Private or Enterprise Cloud environments.
Real devices only.
For Public cloud the only way is for the customer servers to whitelist our public IPs allowing our devices to connect. For private cloud we can implement a VPN or proxy connections. In Enterprise Cloud it is up to the customer to define as the installation is in their own premise.
In Public Cloud it is complicated to manage Google account cash. If a test account can be used to log in and do the purchase completely inside the tested app, then we support it. For Private and Enterprise environments we can set accounts controlled by the customer to enable such purchases.
If the used test framework supports testing push notifications, then we can support them too. Triggering of push notifications is up to the customer to handle.
In Public Cloud it is not allowed to access device settings at all. For Private and Enterprise environments settings can be changed through remote access to the device.
We provide CPU and Memory usage data.
Yes, for most Android and iOS devices. Some models are incompatible with the used technology. Manual testing on iOS devices is supported on public cloud through dedicated devices. Enterprise and Private cloud users can decide which users get access to manual testing.
Yes. Here is more information.
In Public Cloud setting a Google account on the device isn’t allowed. Using a Google API/Service to log in to an app with your own account can be done. For Private and Enterprise environments a customer’s own Google account can be set on the devices.
In Bitbar public cloud a number of Google accounts are in use. These Google accounts may appear when running tests in Bitbar public cloud.
The complete list of devices - with all details – can be found under Bitbar Cloud. We are adding new devices to increase device availability on existing models and add new models as they come out.
Dedicated devices are available through Private Cloud installations or as part of the public cloud. In a private cloud installation the customer is able to freely select the number and type of devices and these are managed by Bitbar. In Public cloud users can reserve one or multiple devices to their use only to assure device availability and security. For more information please contact sales.
No, devices have certain version of OS and cannot be changed. We do the changing when time goes on and if OEM releases relevant OS update. The purpose is to keep up with the actual use of certain OS versions globally and provide as versatile setup of different devices and OS as possible.
Yes, but your application needs to be configured to receive email. The regular email application in device cannot be currently configured for sending/receiving emails.
You can create yourself a free account at bitbar.com. After leaving your email address, you’ll get an activation email with a link guiding you through the registration process. You’re now able to login to Bitbar Cloud using your new credentials and access our trial device group.
There are several reasons why test runs can fail on Bitbar Cloud. First and the most typical case is that there is something wrong with the application, and instrumentation makes it crash. A good rule of thumb is that if AppCrawler run crashes with your app, then the problem is in app itself. Device problems is typically seen as pending test runs.
No. None of our devices are jail broken or rooted.
No, this does not cause problems to our devices or environment. Our system automatically cleans, reboots and hard resets devices before any new test run.
We have two public cloud data centers with IP ranges 126.96.36.199/28 and 188.8.131.52/28. Public Cloud users can also implement a test app to find the current IP of used device/connection and communicate it to external service that can open that IP for connections. For Private and Enterprise Cloud installations most special network configurations are possible.
When you are running an Appium client side test, your host will be making a connection to a dynamic IP address and a port range 10010 to 10090.
Bitbar devices are located in our data centers in San Jose, CA and Wroclaw, Poland.
All our user data, applications and results are stored in Amazon Cloud and are very safe. We also use SSL and encrypt the data as seen appropriate. Only users with valid accounts can access their own data and results. We also track all IPs connecting to our Bitbar.
The time between a start of test run and delivering results depends entirely on test case length, current queue, time of the day and a desired device set. Typically we’re talking about 2 to 15 minutes. Sometimes it can be longer if you start multiple test runs on same devices. We have multiple copies of devices at Bitbar so some devices can ensure results in few minutes (depending on test run length). The customers with higher priority plans (platinum > gold > silver) can get their app running first in case of queue.
We periodically clean unused projects and project files from our public cloud. For unused projects (where tests have not been run) after three months the project files are removed. After this the whole project is removed after next three months.
Yes, you can. Our devices are not positioned for any specific photo target and recording of audio can give you arbitrary recording. However, our devices are fully functioning Android and iOS devices, and both mentioned functions are enabled on the devices.