Releases 2016 - 2017

Release 2.50 Dec 12th, 2017

Last release got delayed a few days after our QAs found some blocking bug. Once that fixed we were able to get out a great release with some interesting new features. Something for the end users and something for the admins! We believe in providing our users with as much data from their test runs as possible to make it easier for them to do their job. Either report progress, verify new features in an application or fix some bug. For this reason there are now additional dashboard widgets to bring additional data to our users.

  • With our new manual testing released last time we forgot to include the button for changing the device orientation. Thanks for the feedback, we now brought it back.

  • iOS manual testing is available for on-premise setups. It behaves pretty close to same as the Android manual testing.

  • Plenty of UI updates that are best described in our blog by our front end developers. Just go check that out to see all cool stuff.

  • New user dashboard. If you read the above blog post, you must have noticed the new dashboard.

  • As cloud admin it is important to know how the devices in cloud are distributed by eg. operating system or API versions. New admin dashboard widgets give you exactly this!


Release 2.49 Nov 23rd, 2017

Great Thanksgiving! Hopefully you managed to get your apps tested and are now enjoying a well deserved break with your app delivery cycle! We have some great new features to make your app testing a lot more fun.

  • Manual testing has been redone from scratch. We are true believers of test automation, but there are valid cases for doing manual testing too. With our new manual testing implementation you’ll want to do manual checks just because it’s so much fun. Even when using shared public cloud devices app feedback is great. For on-premise customers, responsiveness can further be improved. We are increasing the number of supported devices gradually while we make sure each device supports the new solution.


    Our manual testing has the extra benefit it can be integrated into other tools like eg. IDEs. If you are interested in knowing more about such an option please get in touch with us through

    Currently manual testing is enabled for Android devices. For iOS device support a dedicated device is required. For getting access to iOS devices please contact our

  • Devices view and device groups. Last release brought a new devices view and now we updated the device groups handling page. Full documentation is described at Device Groups.

  • iOS test runs are now showing performance data similar to what has been available for Android test runs. This shows CPU and RAM usage of the device during test execution.


Release 2.48 Nov 8th, 2017

We are working on introducing an improved manual testing solution that is just awesome. But that’ll come in the next releases. With this release we brought some general improvements to the public cloud.

  • Introduced Appium 1.7.1 to Android side test runs. On iOS we are running version 1.7.0. There is no major difference between the two. If for any reason you need to run Appium 1.6 or 1.5, it is possible on our Android server side runs. You need to select which version to use in you script. If you want to take 1.7.1 into use check your script is updated to call new version!

    # start the Appium server
    echo "Starting Appium ..."
    appium-1.7 --log-no-colors --log-timestamp
  • Customers with dedicated devices see these as first devices in the devices view. It’s easier to start using those.

  • A whole new devices view! You probably noticed that from previous small screenshot, but it now looks fabulous. Select the filters to suite your test requirements and create a new device group by dragging the selected devices on top of the device groups on right hand side.


Releases 2.47 Oct 18th, 2017

Release was mostly focused on getting last hurdles with remaining testing frameworks to properly work with iOS11. Also we improved cleaning of iOS devices after test runs.

  • iOS11 support on all iOS side test frameworks. Appium support was already there but now also Calabash support for iOS11 was introduced. Of course you can also use any other (or own) test framework by installing it at the beginning of the test run. More information here.
  • Cleanup of Safari browser (history and cache) after test runs. Even if we do these cleanups you should not leave any open sessions from your test sessions. For improved security you should go for dedicated devices. Sales can help you with these at
  • We brought a place holder for our Monitoring service to the cloud UI. This page will get updated during the end of the year to include creating and viewing basic checks.

Release 2.46 Oct 4th, 2017

A lot of things brewing in our development pipeline for new features and performance improvements. There was release on Wed 4th of October that brought out some neat improvements and new features.

New Features

  • We are rolling out support for iOS11 with latest Appium 1.7.0. We first introduced a limited number of dedicated devices with this setup and now bringing additional devices online. These devices support XCUITest, XCTest and Appium test frameworks. We’re bringing Calabash support also during the next two weeks.
  • Bitbar cloud is moving forwards with iOS build support! We have had support for iOS builds but have not really made a number of it. We are now introducing dedicated iOS build environments to our private customers. The solution is targeted for companies with well defined build environments requiring a fast and always available iOS build environment.
  • We have introduced improvements to cloud usage activity logging. The list of actions is now more detailed on who has used the cloud and how with cleaner logs.
  • Users coming from external marketplaces like Bluemix or AWS Marketplace have now a more streamlined user interface.
  • We created a new tool enabling Android device network management and traffic. On-premise and Private customers can now monitor the device network availability in their test environments.

Fixed Bugs

  • We fixed some bugs related to our Android device cleanup mechanism. Cleanup happens now faster and it is more robust.
  • GB integration was brought back to Android UIAutomator runs. We had to limit GameBench usage with some of our test frameworks but were now able to bring it back. This particularly affects the AppCrawler runs.

Releases 2.42-2.45 Sep 20, 2017

During the past three months we have had several releases of which some were minimal and for this reason did not put anything here. There was a major release that could have gone better but kept us so busy we waited until now to write about.

The last release in August was a huge one, where we updated most of our infrastructure to support a more flexible and service oriented architecture. This included the switch to using Docker images for running our tests. There have been multiple blog and email posts on this earlier.

This week’s release was mostly a preparation release for upcoming Xcode9 support with iOS11 and test framework upgrades at the end of September. Also we’ll be available on some new marketplaces in the coming days which is also cool.

Release 2.41 Jun 08, 2017

  • Additional options for Slack and HipChat notifications. In addition to getting notification from test runs, you can now also get notifications about cloud status or news about new devices included into cloud.


  • Private and On-premise administrator get more control on what and how to inform end users. The admin menu has a totally new menu item to control to whom, what information and how is sent. This is a great way of letting users know about the addition of new devices or frameworks to run tests on.

  • iOS updates rolling out after release!

  • Fastlane - Fastlane is now available as pre-installed on the test machines.

  • Xcode - was updated to Xcode8.3. We’ll start upgrading devices to support the latest available iOS version 10.3.2 during next week.

  • We decided on not updating Appium version as the new stable version came very late and we didn’t know how stable it would be.

  • Calabash upgraded to latest version 0.20.5

  • Support for Gemfile-file in uploaded test zip files. This should make it easier to setup special Ruby test environments.

  • new registration and activation process. If you don’t yet have an account for Bitbar Testing go and create a new trial account!

  • Video recording is now available and set on for all Android test runs, except manual test sessions. For now, videos of test runs are available on the device test run view next to log files. Note some devices do not support video recording and getting the videos into the result files can take up to a minute longer than the other files.


Release 2.40 May 24, 2017

  • HipChat integration. Last time we brought support for posting test run results to Slack, this time the same is available for HipChat. The integration is described at HipChat notifications.


  • iOS device availability was improved significantly. We have improved the way how our iOS devices are visible and available in the public cloud. All existing users were notified about this change beforehand as it affected all existing iOS device groups. As a summary this update broke existing device groups with iOS devices and these groups need to be recreated.
  • Making management of the main users easier for Bitbar Testing admins - especially useful for on-premise installations or private cloud installations with admin rights - main admin can now convert a project sub-user into a main user. This action will make the original main user into a sub user.
  • Lastly, we hope you’ll enjoy the updated colors in our UI. We think these bring a breeze of freshness.
  • All users wishing to get in contact with us, can do so directly from the cloud, using the get in touch window. This is now moved to the top bar next to system notifications. You’ll be able to send us screenshots and files through this feedback form too.


Fixed bugs

  • We were wrongly presenting some Android Appium server side test runs as iOS UIAutomation tests. This had stayed from when we disabled support for UIAutomater altogether.

Release 2.39 May 10, 2017

  • To get a better overview of the cloud usage for on-premise customers we’ve added some reporting about the cloud to Admin - Dashboard. You’ll here be able to check which users and teams are most using the cloud, which devices are being used (you might want to add additional instances) etc.


  • On-premise customers get improved tracking on project and user creations so admins know who are using which parts of the product!
  • Slack notifications! We too love our Slack and thought that you should be able to get your test notifications to the channels that you use in your daily work. We’ll be adding some additional chat integrations here in the coming releases.

Slack notifications

  • A new widget for getting email notifications was also added while working on the Slack notifications. You just need to add your email here, and select what type of notifications you want to receive into your mailbox!

Email notifications

  • Support for running Gamebench analytics on the client side Appium runs. To get started with this you just need to have Gamebench configured and use the testdroid_gamebench capability in your script. Check out more on the capability here.

Gamebench capability

  • And a plethora of other things under the hood that is not directly visible on the UI.

Release 2.38 April 20, 2017

A few big changes in today’s release. First the change in our free trial plan and the second in our API. Additionally some fun stuff for manual testers.

  • Free plan changes to a free limited time trial period.
  • API change for file uploading. We wrote about this in a blog post last week. In practice this affects all users using
  • the Java client
  • Run in Cloud Jenkins plugin
  • Gradle plugin
  • Access to Bitbar Monitoring. As you may have read we are working on a new product Bitbar Monitoring. This is a mobile application synthetic monitoring solution that can be accessed with Bitbar Testing credentials.
  • Possibility to set key bindings to your manual testing session. When testing some application that needs the user clicking on particular buttons or regions in the app multiple times. Doing this by mouse can be cumbersome but assigning keybindings for these make testing really simple. To try this out, you’ll need to enable Beta features under ‘My account’. When a manual session is started at the bottom of the device widget there will be an option to create key bindings.


Release 2.37 March 22, 2017

While previous release 2.36 did not bring much visible improvements to public cloud, there are some major ones with this release. This is also the reason there is no release notes for the previous release.

  • Notable changes relate to using manual testing. In short whole of the manual session was rewritten to make it faster, more usable and easier for the user to install all the apps that are needed during the testing session. For a whole description on how the manual testing works, please check the user manual page.
  • The used notification system got also updated. This is the reason cloud now asks at first login to allow showing of notifications.


This will get used more in the future as we implement support for it. Our main developer wrote about it a blog post.

In addition to the above UI changes there were several back end fixes that improve the security and availability of devices.

Release 2.35 February 16, 2017

This release consisted mostly of technical improvements to our iOS test runs infrastructure. With the last releases of Xcode there has been a lot of changes in mobile testing behavior.

Old Apple UI Automation framework got removed from the supported test frameworks as it hasn’t been supported by Apple either for years.

There are visible UI changes on the My Account page. For those interested in the reasons behind the changes can be read here.

Support for integrating to Gamebench service directly from the UI. Also note that the other possible integrations are now grouped here under My account.


Release 2.34 February 1, 2017

  • iOS AppCrawler enabled again. Due to the iOS side updates that were done since the beginning of the year, now the AppCrawler was done from scratch. Because of this the AppCrawler won’t work exactly the same as the old one. Also, for now, it won’t be able to fill in login or other forms.


  • UI modifications and improvements. Notably changes in the My Account page which now contains available and enabled integrations and the list of account users. Account users are users that are allowed to run test runs billed to the current user.


  • Interested in getting deeper hardware statistics about how apps behave on various devices in Bitbar Testing? It’s now possible by providing existing Gamebench credentials to get device and app statistics gathered from each test run in Bitbar Testing. This same Gamebench integration is also supported on On-premise and private cloud setups.


Once a testrun is executed and Gamebench has been enabled then a link to the results is presented in the test run results page.


This link will take you directly to the Gamebench portal where the results for the used devices are presented.

  • A ton of small fixed here and there, especially on our iOS side Appium execution.

Release 2.33 January 17, 2017

During the past month there have been multiple updates done to Bitbar public cloud. Some have been visible to end users and some not. The below list of enhancements are available on the public cloud but also available to our On-Premise and Private cloud customers. To get all latest features whole or parts of On-Premise or Private cloud needs to be updated. Please contact your dedicated support contact.


Added Features

  • XCTest and XCUITest frameworks are available to all users of Bitbar Testing cloud! These have been available to a limit number of users already since December but now all public cloud users get access to these. Bitbar Github samples present an example test project with both XCTest and XCUITest test steps.

    The documentation on how to prepare your Xcode project for these frameworks is available here.


  • Latest stable Appium version 1.6.3, supporting newest iOS and Android devices has been installed to public cloud. This is the default Appium available for client side and server side test executions. On Android server side it is still possible to select some older version if required. For iOS, this is the only supported version.

    iOS side Appium Safari testing and iOS AppCrawler support are introduced to public cloud in few weeks with separate updates.

    Attention Users using older versions of Appium (before 1.5) may need to update their test scripts. Appium has made changes to default desired capabilities and deprecated some methods since Appium version 1.4. For example with Android tests, the method find_element_by_name(<some string>) has been deprecated and needs to be updated with find_element_by_android_uiautomator('new UiSelector().text(<some string>)). Please check our sample tests online for updated tests or Appium release notes.

    Next major Appium version upgrade on Bitbar Testing is done towards end of Q1 2017.

  • Public cloud iOS devices are upgraded to latest available and Apple supported versions. As with earlier version of iOS most users have already updated their devices to the latest iOS 10.2 version. In public cloud, only a limited number of devices with older iOS versions 6, 7 or 8 remain.

Mixpanel stats for iOS10 adoption until Jan 2017

  • Support for Java 8 is available for test runs.
  • Chromedriver was updated to 2.27.440175. This update was done already before Christmas, but we had a bug and the update didn’t go through everywhere as it should have.

Release 2.32 December 22, 2016

Added Features

  • XCTest for iOS10 devices available to all paid plans. iOS10 devices were introduced to public cloud about a month ago and now the support for running XCTest test on them is available to all users. For more information on how to build the app IPA and how to package the tests is available in our documentation

Bitbar’s Github sample repository also contains an example XCTest project that can be used as a starting point with the above documentation, when starting out.

With the support for XCTest project type, it is now also possible to run KIF tests in Bitbar Testing public cloud. The same has been available for a long time in Private and Enterprise installations.


XCTest is available only on newer iOS devices with iOS version 10 or above. Support for older devices is coming in the following weeks.

  • Calabash project type available to all new users regardless of the registered plan. Free users are limited by number of available free devices. Existing free users get access to Calabash projects by upgrading to a paid plan.
  • iOS manual testing support is now part of default Bitbar Testing. Manual testing with iOS devices was until now enabled per device for dedicated devices and for Private and Enterprise installations. Testing how the app looks and behaves on real Apple devices is now easier than ever.
  • Jenkins Run in Cloud plugin updated to version 1.0.17. This fixes issues with downloading results and starting Appium server test runs.

Release 2.31 November 24, 2016

Added Features

  • Calabash environment variables. For better control over Calabash test run executions environment variables are typically used. In Bitbar Testing it is possible to give values to the two pre-existing environment variables CALABASH_TAGS and CALABASH_PROFILE, in the advanced settings of a test run. These can be used to better orchestrate in which order tests get executed.


For private and on-premise installations it is also possible to allow users create their own variable and value pairs.

  • Project type names were renamed for better clarity. Bitbar Testing solution is very test framework agnostic but we have a number of predefined common project types available. Below is how we have renamed the project types.

  • Android -> Android Instrumentation

    Android’s own unit testing framework meant to run on the device for functional testing.

  • Appium Android -> Appium Android client side

    To unify the naming convention with Appium client and server side projects. Earlier naming was not explicit about the client side approach.

  • Appium iOS -> Appium iOS client side

    Uniformity to project naming conventions between client and server side projects.


  • Chromedriver gets a version upgrade to latest version of 2.25.

Release 2.30 November 9, 2016

Technical release with reliability updates and preparations for upcoming features.

Added Features

  • For easier screenshot step recognition in device test run view, the screenshot names are attached below the screenshots.


  • Appium server side image recognition sample test gets a total rework. The sample project shows step by step how to do image recognition testing using Appium for testing eg. games.

Setting up needed environment is much easier to earlier example with less external dependencies and libraries. Used libraries were updated to the latest ones.

Launching server side tests is simplified by introducing the script. This script is able to create the test zip, handle uploading of the required files as well as creating a new test project, when needed. Ideally the script is used by CI systems, but manual usage works just as well.

$ bash
Either -a or -i flag must be provided, but not both! - create and upload test project to Testdroid Cloud and run it

  Usage: -a/i -g <DEVICE_GROUP_NAME> -k <API_KEY>
   -a for Android test
   -i for iOS test
  Optional: -p <PROJECT_NAME> to choose a specific profile. If not given, a new project will be created
  Optional: -t for creating and uploading a new test zip file
  Optional: -f <APP_FILE_PATH> for uploading a new app file
  Optional: -e <API_ENDPOINT> for private cloud instances

The script is already available in image recognition samples.

  • We setup our Maven central proxy making any Maven installs more robust and a lot faster. This is great news for all and especially Java server side mobile test runs. For more information about Maven mirrors check here.
  • Sample demo project is removed in Bitbar testing after user creates first new project.

Release 2.29 October 27, 2016

Added Features

  • Improvements to device filters. The back end behavior for handling various device properties was improved to make sure the search criteria are better up to date and results more accurate than before. It’s now easier to add new device labels (for On-Premise installations) and to search for devices from the UI.
  • Small changes make a difference. Uploaded apps to manual testing now show the upload date and time making it easy to select the latest uploaded app for testing.


  • Filtering of tests inside of test run view. To make it easier to debug the cause of failures in apps, it’s now possible to filter device runs to show only those where tests have failed. It is possible to have multiple filters enabled at a time making it possible to filter out failed devices and look only at successful test runs.


  • The documentation to integrate JIRA with Bitbar Testing is updated and can be found in docs at Integrations/jira
  • Big updates in Bitbar’s image recognition samples on Github samples. In addition to library updates, there are a lot of new improvements. iOS screenshots speed was dramatically improved by changing screenshots mechanism to use idevicescreenshot. Image recognition does not need the testdroid-appium-driver anymore, but uses the native Appium driver.

Bug fixes

  • Improvements in iOS server side test runs. There were multiple reasons with this of which OSX upgrade was one. Work on further stabilization is in progress.
  • Appium client side runs were terminated if a test could not find some element. This is now fixed.

Release 2.28 October 17, 2016

Added Features

Single Sign On (SSO) using Google accounts has been enabled to public cloud. This is especially useful for teams and enterprise customers using Google mail services. It is enough to invite a co-worker to own project in Bitbar Testing cloud after which the invited user is able to SSO and instantly start contributing in testing or debugging of mobile apps.

Bug fixes

  • Device run logs widget fixed.
  • Improvements to iOS test run stability. There are still issues but improvements are being rolled out in phases.

Release 2.27 September 29, 2016

Added Features

Dedicated devices - a new service for getting customers devices connected to our public cloud but also available to all other clouds. Use Bitbar Testing’s large device range for manual and automated testing, but run regression and continuous integration tests on named devices hosted and managed by Bitbar. To get and pick the dedicated devices, please get in contact with Bitbar sales.

Enterprise customers can use this functionality to create device pools visible and accessible only to particular teams.

Known Issues

  • Since the past week there have been issues in running tests on our iOS devices. We are investigating the issue and are fighting to get it fixed. We are really sad about this.

Release 2.26 September 14, 2016

Added Features

  • Testdroid Cloud supports video recording of Android test runs. This is a premium feature that is available for Team and Business plans. To enable video recording of your test runs, please contact your named service representative or Bitbar sales. Support for iOS test run recording is coming shortly.
  • AppCrawler quick project creator includes credential fields. Instead of having to go through creating a new AppCrawler test run from the create test run menu, it’s now possible to include app credentials also in the quick AppCrawler creator.


  • Enterprise customers get yet more admin capabilities to manage their dedicated device cloud. Admins can now easily create teams inside of Testdroid Cloud which allows reporting per team based usage statistics. Getting an answer to which team uses device cloud most is then straight forward.

  • Find the user that needs to be added as sub user and on user information page click on the button to set main user


  • It’s then possible to select the main user


  • Enterprise users can define how many times test runs get retried or not. There’s now a new API call that can be used for changing the number of times that a test is retried. There are multiple cases when a test should not be re-run even if there’s a problem with the test or device. If you have an Enterprise or Private cloud setup please be in touch with your customer success contact person to get more information about this.

Release 2.25 September 1, 2016

Added Features

A small back end update focused on upgrading the Appium version used in server side test runs. Default for server side runs is still Appium 1.4.16. Modifying the run tests script, allows using of Appium version 1.5.2.

This is the old approach of starting Appium in the script.

# on iOS
/opt/appium/bin/appium.js -U ${UDID} --command-timeout 120 >appium.log 2>&1 &

# on Android
/opt/appium/appium/bin/appium.js >appium.log 2>&1 &

To use Appium 1.5, the above lines need to be updated to as below. It is suggested to update the script even if older Appium version is used. The launch procedure has been improved with this new approach.

# on iOS
#appium-1.4 -U ${UDID} --command-timeout 120 >appium.log 2>&1 &
appium-1.5 -U ${UDID} --command-timeout 120 >appium.log 2>&1 &

# on Android
#appium-1.4 -U ${UDID} >appium.log 2>&1 &
appium-1.5 -U ${UDID}  >appium.log 2>&1 &

Due to how Appium is started there is no more a need for a constant sleep after the launch. The following line should be commented out in the as unnecessary.

sleep 20 # Sleep for appium to launch properly  #<- this is not needed anymore

For now Appium client side runs continue to use older Appium 1.4 version.

Release 2.24 August 15, 2016

Added Features

  • New project types for server side runs available to all users with SOLO plan or up. To create a server side Appium project, simply select Appium iOS or Android Server side project type from the project drop down list.


  • Appium client side testing picks similar available device by default

We updated our client side Appium to work in a way where the user does not need to provide an exact device name. The Appium client will search for a device that matches the requested device but does not guarantee that the requested device is used. The used device is visible in Testdroid Cloud test run view.

For example by passing “iPhone” as testdroid_device capability name, Testdroid Appium client will pick any of the available iPhone devices, regardless of iOS or iPhone version. The test could be run on an iPhone 5s or iPhone 6.

If the user wants to turn off this feature and use a specific device then the testdroid_findDevice Appium desired capability needs to be set to True like in below Python example. By default this is False.

desired_capabilities_cloud['testdroid_findDevice'] = True
  • Enterprise cloud admin users are now able to manage project ownership through the admin panel. Go to Admin - Projects, select the project that you want to move to other user and click on the “Project owner” icon.


    You can then change the owner by selecting new user from the list.

  • Support for iOS 9.3.x devices using XCode 7.3.

  • Python version 3.5.1 is available for server side runs. To use it, just call your Python scripts with python3

  • A touch or personalization is always fun. Testdroid Cloud now supports avatars through the Gravatar service.

Release 2.23 July 5, 2016

Fixed Bugs

  • Results processing in some cases was taking a long time or even failed. Test results processing problem was solved and solution improved.

Added Features

  • AppCrawler - Testdroid Cloud has had since its very early days an automated app tester that crawls through an app, checking for correct behavior. AppCrawler can be accessed directly from the main menu, or by creating a new project. When creating a new project the user has more options on guiding AppCrawler forward.


To smoke test an application the app needs to be uploaded, then choose project to include the results or create a new one and select the number of devices the app needs to be tested on. If device groups are defined then these can also be used. Clicking ‘Go’ starts the test run. Free users are limited to running on only one free device at a time.

  • The view to read and debug a test run’s test steps or error logs can now be enlarged for better clarity. Once the view enlarged it’s easy to use the search box to find keywords. Of course browser’s own search is also supported.

    image27 image28

  • A better support for presenting results as test steps for users using Cucumber with Appium.

Release 2.22 June 23, 2016

Fixed Bugs

  • Getting always the same device from device group. Some customers had an issue when running sequential tests on a device group where the test + first device configuration failed. In future the devices from a selected group are proposed in a randomized order to increase success of sequential test runs.

Added Features

  • Enterprise and Private cloud administrators get a new menu element for managing used test frameworks. This gives Testdroid Cloud administrators the possibility of sharing test projects configurations between teams and modify the configurations of a specific test project.

  • Calabash test framework is updated to latest version in Enterprise Clouds. Available versions are 0.19.0 for iOS and 0.7.3 for Android Calabash.

  • Users are now able to cancel a test run with multiple devices and keep the results for the finished devices. Earlier when canceling a test run, the execution and results processing was canceled for all devices. Even those that had already finished test execution. With this release cancellation cancels only tests for those devices that have not yet started or finished running the tests. Results are presented for device runs that already have results.


  • Throughout the spring there has been updates to better visualize the test results. The last part (for now) comes to end with the updates to the device run view. The view has changed to give a better overall view of the device run. The page is divided in four. First view lets the user to switch which device from the run is inspected and present general relevant information on that device run.


Logs are in their own widget. Different logs have their own syntax highlighting and everything can be text searched. Switching between various gathered logs is easy. The test framework specific logs are highlighted (eg. Appium and Calabash) and additional logs can be selected from the drop down.


Know Issues

  • There is an issue with post processing of some test results in our Public Cloud. This release fixes part of the problem but there can still be issues with some runs. A robust solution is being implemented. More on this when final solution is coming out.

Release 2.21 May 30, 2016

Release has mostly changes important to Enterprise Cloud users and internal to Testdroid Cloud handling of project related data. More on this with the upcoming releases, with more visible changes.

Fixed bugs

  • Performance fixes to creating new device groups. There was an annoying bug when creating a new device group by dragging new devices to the “New group” icon. The group got created but the correct number of devices in the group was slow to get updated.


Added Features

  • Jenkins plugin, Bitbar TestingRun in Cloud Jenkins Plugin was published to Jenkins Wiki. Also an update release (1.0.12) was made available and can be installed through the Jenkins Manager.


  • Improved the presentation of test steps in View Screenshots by Test Step view. This functionality is available for Calabash users but also for AppCrawler (automated test runner) and Android UiAutomation tests. Now the screenshot comparison view presents erroneous steps and devices.

The comparison view also got some new icons next to device titles. These show whether there were errors in the tests or running the tests. As elsewhere when everything is good we give it green color, otherwise orange or red when things got really bad.


Release 2.20 May 11, 2016

Technical release mostly intended to fixing some back end issues. Release targeted for Enterprise installations.

Fixed bugs

  • Unable to use function buttons in manual testing: Using Firefox 44 some UI elements on the manual testing view did not react correctly.
  • Our resign-ipa script did not handle app Bundle display name with spaces correctly: Fixed.

Added Features

  • UI improvements to device run view. To ease access to the project information, like downloading log files, screenshots etc. we moved the project information up above the test run status view.


  • Bread crumbs to improve navigation. To help navigation inside of projects we added bread crumbs under top menu so it’s easy to navigate back to where you came from.


Release 2.19 April 27, 2016

Technical release with improvements for Private Cloud users and bug fixes.

Fixed bugs

  • Changes to IBM Marketplace integration
  • Performance issues for administrator users (Enterprise and Private Clouds)

Added Features

  • Improved usage details reporting

Release 2.18 April 4, 2016

Release for Private and Enterprise installations in mind.

Fixed bugs

  • Improvement to Calabash iOS test run reporting

Added Features

  • Administration interface was upgraded. Administrators can now use the same look and feel throughout the whole service.

  • Integration to IBM Marketplace. IBM Marketplace users can now get started using Testdroid Cloud.


  • Possibility to reprioritize test runs in queue (Enterprise & Private

    Clouds). While an other team is running long regression tests reserving all the devices, you might want to prioritize your bug fix test run higher to get your fix tested. You can now do so by setting the priority of your test run in the admin panel of your Enterprise Cloud installation. Clicking the “edit pencil” admin is able to set the wanted priority to the test run.