Using Real Mobile Devices on Cloud – Testdroid Cloud ABC

Bitbar, the mobile devops company. Logo, large

Using real mobile devices (phones, tablets, even wearables etc.) on a cloud service is nowadays easy and straightforward. The only thing that you really need is your application (as an APK or IPA) – and the system can take care of the rest. Naturally, using intelligent automatic test exerciser is a great for quick smoke testing and checking if app is compatible across all possible devices, however, it doesn’t really give you deep understanding of real issues that your app might have on these devices. For this, you need to have tests – a test scripts – that hammer through your app while running on those devices.

testdroid_cloud_abc

We’ve gathered together some videos of how quickly and easily you can create test runs on these devices at Testdroid Cloud. You can start testing simply by creating an account here, activating the link sent to by email, and follow these instructions.

How to Create a New Device Group

Testdroid Cloud enables its users to create a specific device groups that are used to point out on which devices tests are executed. The device group configuration can be found under the main menu – Device Groups.

Creation of a device group starts by giving a name for device group. After this, user needs to select either to be created device group is Android or iOS. Note that device groups can include devices from either platform, not both. By clicking Create group the device group will be created.

Users can include devices in device groups by selecting device separately on the left-hand side’s browsing menu. After selection, user can drag and drop devices to newly created device group on the right-hand side. The filter options on the left-hand side, for example, OS versions, API levels, CPUs and so on can be used to browse specific devices for selection.

NOTE! Testdroid Cloud also provides a set of free of charge devices. Many of these free devices are Intel Atom-powered Android devices so users can freely use these devices to test their APKs on these devices.

The other alternative for creating device groups is to select all desired devices on the left-hand side widget and clicking ‘+’ on top of that widget. User can then configure more specific details – e.g. name – on the right-hand side widget.

The third way to configure device groups is enabled by clicking existing device group on the right-hand side widget. Devices included in the specific group will be shown and user can remove and add devices accordingly

How to Create a New Test Run

Step #1: Upload your application

Click Choose File button to locate APK or IPA file from your local harddisk. For further configuration, click Next (either on bottom or top of the view).

Step #2: Select the test type

Testdroid Cloud provides a feature called App Crawler that automatically crawls through the app and tests its functionality by exercising UI components (e.g. button clicks, opening menus, changing views). App Crawler automatically handles the screenshot taking, log writing and generally it keeps the record of application’s status.

When user selects ‘File’ instead of App Crawler the view asks user to locate test script files for the app.

When proper test method has been selected, click Next (either on bottom or arrow on top).

Step #3: Select devices for the test run

The view shows all created device groups. User can also create a new device group by clicking the left-top icon with a ‘+’ button. Device groups are either for Android or iOS. By default, Free device group is selected.

NOTE! Device groups can include only Android or iOS devices.

Step #4: Advanced options for the test run

User can specify test run name, tags, scheduling of the test run (if tests is desired to be executed simultaneously on all devices, one device at a time or on a first available device for test run).

User can select the language for devices. There is great variety of different languages available and all devices will be configured with selected language for the test run.

User can input login credentials for the application. If app requires user authentication at the beginning, login and password information can be included here.

User can specify how test cases are used – e.g. from specific package or class and then definitely the name in given field.

User can also specify hooks for finished tests by giving an URL. If this option is used, the POST call will be performed when test run is finished.

How to View Results in Testdroid Cloud:

Test run / Overview
User can access Test Run view either by starting a test run or clicking any of older test runs is dashboard or projects view. In this view test run execution information, execution time as well as success of test runs is shown in summary type of perspective.

The Testdroid Cloud test run starts always with device cleaning (removing all content from devices, cleaning SD card and rebooting devices), followed by installation and launch of the app and tests.

In this view, the test case success will be presented as well on the right-hand side.

On the top-right of the test run widget, user can filter data shown in widget. For example, user can filter passed, failed, excluded, and not executed devices for the widget. User can also restart the test run or download all data using icons on the top-right corner of the widget.

More specific error of test execution from test run can be seen when mouse is hovered on the top of red colored error message. User can focus on each device run by clicking the device row. Futhermore, user can open all device runs by clicking Show all X devices where X indicated the number of used devices in the test run.

Device run details / Test cases
After clicking any row on test run view, user is directed to view generic information about tests is shown. By selecting the name of test (presented either as green/success of red/failure) the test steps will be shown. User can also filter successful test runs by clicking the eye icon on the top-right corner.

Device run details / Screenshots
The Screenshots view shows all captured screenshots during the selected test. The number on the right-top corner of each screenshot indicates the step when screenshot was taken. For example, test run may have 22 steps. Each step will include a screenshot and if the step includes multiple screenshots, those are named as .. (e.g. 6.1, 6.2).

Device run details / Performance
The Performance view provides details of the test run for CPU and memory usage. User can click any given step/time to get more specific information about resource consumption. The performance log can be also downloaded by clicking the Download performance log button on the top right-corner of the widget.

Device run details / Logs
The log view provides line-by-line information about the test run. It can be configured with types of information user wants to investigate and show in Logs view. Available configurations are: Info, Debug, Warning, Error, Assert and Verbose.

Device run details / Device files
If the test or device run includes additional files those can be reviewed and download from this view. For example, if test run generates additional logs, users can get those files through this view after the test run is completed. All additional files can be downloaded by clicking Download all files button on the top right-corner of the widget.

Screenshot comparison
The Screenshot Comparison view makes it easy to compare captured screenshots from every test run. Users can select screenshots from dropdown menu that gets automatically shown on each device in the test run. Screenshots can be browsed also with arrow button on the top right-corner of the widget. For full-screen mode, user can click Full screen button and for downloading all screenshot Download screenshots button.

Happy Test Automation on Real Devices at Testdroid Cloud!

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.

Close