If the device is disconnected during execution, has a problem, or times out, the device will be untested. The untested amount will be automatically returned to the original account.
Parallel tests indicate the number of tests that can be run at the same time.
In some situations, the devices may not be tested, such as
1） The task reaches the maximum timeout period and automatically ends the test.
2） The device’s current state is abnormal.
There is no limit to the number of tasks that can be submitted for an account, but the number of devices that can be tested at the same time is limited by the number of parallels in the account.The number of parallel you purchase is the maximum number of devices that can be tested at the same time.
The test order of the devices is randomized.
Once the task is submitted, the task starts running.
In Public Cloud, setting a Google account on the device are not allowed. However, you can use a Google API/Service to log in an App with your own account.
There are several reasons why test runs can fail on WeTest Cloud. The first and the most typical case is that there is something wrong with the application or script, you can view our official sample on Github.
Now, WeTest only supports mobile Apps testing. However, the capability of testing mobile web is in our future plan.
You can contact our business team using email.Contact us
Our devices are real, physical devices. They are standard, commercially available devices and not modified or rooted. All of them are managed in our IDC standard data center.
Each device is cleaned of apps that are not expected to be there after each test run.
Now, Real devices only. Simulators will coming soon.
The complete list of devices with all details can be found in WeTest Supported Devices. We are adding new devices to increase device availability on existing models and add new models as they come out continually.
No, each device has a certain version of OS and cannot be changed.
No. None of our devices is jail broken or rooted.
No. Public Cloud is not allowed. However, you could use our Private Cloud by contacting sales team.
Yes, but only for Live Testing. The change can be made in the Settings of the device manually.
No, none of our devices have SIM cards and are not connected to the Carrier Network.
No, our devices which do not have SIM cards can not access to the Carrier Network.
Yes, some of our Android real devices maintain a pre-release OS version.
Now, Appium(Unittest/JUnit), Flutter and Espresso will come soon.
For each real devices in the public cloud, it’s up to the advanced settings of time-out period. Maximum is 1 hour, default is 10 minutes.
Based on our Perfdog service, client performance data could be extracted easily during your automated testing. You could quickly locating the performance issues with no need of modification on hardware or apps. We provide CPU and Memory usage data, etc.
30 minutes by default. You can increase it up to 45 minutes using a timeout capability in advanced settings.
Yes. we have the number of concurrent test sessions which means that multiple devices your test scripts can be executed at the same time, in the case of automated testing
Yes. The five other tests will try to get the requested devices for the next 15 minutes. That’s the default time – it can be increased to 45 minutes through a timeout command.
No. There is no extra certification need for Android.
No. If there is, it means our automated cleaning process didn’t work as intended. If this happens, please let us know so the Operations team can reset the device and see what went wrong with the cleaning process.
No, there are no inspection tools. We recommend using Appium Desktop for UI inspection, it has built in support for devices on the Real Device Cloud.
No, it will be automatically created by the platform before starting the script.
The script running environment in the cloud is different from the directory structure of the local script executing computer. The pwd that executes the script is in the script root directory and can be replaced by a relative path.
You need to install the environment in the script file runTest.sh, for example, appium-python-client version 2.8.1.
You can execute the following command to install it.
pip3 install Appium-Python-Client==2.8.1 --proxy $HTTPPROXY -i https://mirrors.tencent.com/pypi/simple
Yes, the documentation with the full API description can be found at REST API.
We provide a Jenkins plugin, see detail at WeTest Jenkins Plugin.
You can create yourself a free account at WeTest.net. After confirm your email address, you’ll get an activation email with a link guiding you through the registration process.
Your free 30-day trial includes：
50+ Android real devices in Trial Device Cloud.
You can run as many tests as you wish on your trial account with unlimited minutes in 30-day free trial, but you will only be able to access to Trial Device Cloud and run 5 parallels at the same time.
You can upgrade your plan at any time and get access to all its features immediately. Please contact our sales team.Contact us
If you are not familiar with automated testing, we recommended you follow the quick start section and use our samples. Quick Start
We promise that no other user can have access to your data. This is why we have a clean up phase after each test. We will uninstall all user apps and delete data.
Finally, we will check whether the clean-up was successful and block the device for other users when we find your data has not been removed properly.