Manual Testing

Bitbar Testing Cloud Manual Testing feature provides users a way to have manual access to Bitbar Testing devices. By clicking Manual Testing in the main menu, user will be directed to the Manual Testing setup view.

The overall process for manual testing is straight forward. Select the device to be used, start a session and once the session is up select any app to be installed or file to be uploaded onto the device. The app and files are then usable during the manual testing session. Once the session is ended, all files and apps are removed from the device and are not usable anymore.

Bitbar Testing supports manual testing for Android and iOS devices. Android manual testing is available to all users, but iOS manual testing is available through dedicated devices in public cloud. Enterprise and private cloud customers can decide to make iOS devices available to all or not.

Getting Started

Select Device For Manual Testing

First a device for manual testing needs to be selected. To find the appropriate device the filters can be used or then simply searching by device name. The devices that are grayed out and have a lock are currently being used by some other user.

Selecting a device for manual testing

Once the device is selected the connection to the device is created. It can take up to 15 seconds for the connection to get created.

Some rare Android devices do not support the used remote connection technology and for this reason are not visible in the manual testing device selector. Manual testing on iOS devices is not supported on public cloud devices but is available to On-premise and Private Cloud customers.

Interacting With Device

When the connection to the device has been created, user can interact with the device using the mouse and keyboard.

Sometimes instead of swiping from screen to screen on iOS it might be easier to use the small “home screen dots”. Clicking on these you can move to next screens.

Switching home screens on iOS

Installing Apps and Additional Files

More applications can be installed and uploaded during the manual testing session. To install an application on the connected device, click on “Upload or choose files” button, which opens a file picker.

Session status information Selecting files to upload or install to device

If an .apk or .ipa file is uploaded the app gets automatically installed onto the device. It is also possible to upload here additional data files with images or location information too.

Interacting With Device

Once the connection is up, and possible apps installed, it’s possible to give control how the device should behave. Using the buttons next to the device it is possible to take screenshots for later usage or rotating the device.

Tools to interact with device

Supported actions on the device are:

  • Power -switch the device off / end session.
  • Volume - speaker volume can be turned up or down.
  • Rotate - the device under session can be switched to portrait and landscape mode.
  • Screenshot - take a screenshot of ongoing device session. The screenshot is stored and shown in Screenshots widget at the bottom of the browser window.
  • Expand the device widget to full window.

Viewing the Logs

While interacting with the device, it can interesting of viewing the device logs to see what is happening in the tested application. The logs view shows exactly this. Going from left to right, here is what can be done with the logs.

  • Search for a string inside the logs. Every occurrence of the string gets highlighted.
  • The logs can be paused and turned back on. This is especially useful for checking a particular behavior from the application.
  • Clearing the log buffer. When things get complicated, it’s good to start from a clear starting point. Cleaning the logs and restarting the test case can be a great way to locate what is causing problems.
  • Changing the logs color scheme. When reading logs, there are some color schemes that are better to others and each developer has it’s own preferences. Thus the possibility of selecting the preferred colour scheme.
  • Downloading logs for later usage and possible bug reporting purposes. Bugs with application logs are much more likely to get fixed.
  • Expanding the logs view to full window. When searching the logs, the log window should be large enough to show one full line length.

Screenshot widget


The Screenshots view shows all captured screenshots during the Manual Testing session.

All captured screenshots can be downloaded by clicking Download screenshots button on the top right-corner of the widget.

Screenshot widget