Testdroid Recorder 1.0 is now out from Beta!

Bitbar, the mobile devops company. Logo, large

We are proud to announce that Testdroid Recorder is now officially out from Beta. The production version includes numerous new features, usability improvements and a lot of bug fixes.

The feature highlights of Testdroid Recorder 1.0 are:

Automatically configures your Android Test project for Robotium use
Testdroid Recorder takes your Android Test project and automatically generates all files needed to set up a working Robotium test project. This means that you will have your first automated Android tests in matter of minutes – not hours or days!

Recording test cases without application source code (just APK is needed)
We have listened to our customers and added the capability to record test cases without the application source code. Now you can take almost any APK file and create either Robotium or monkey runner tests for that APK by using Testdroid Recorder. Sweet!

Test output either in Robotium Java test code or monkeyrunner test programs
Even though Robotium is coolest and most versatile testing framework for Android it has some limitations. For instance it is not very easy to create test cases spanning multiple applications using Robotium. For this reason you can also choose Google’s monkeyrunner as an output format for your automated tests. The output is executable monkeyrunner test program that can be executed on an Android device like any other automated test. Long live the freedom of choice!

Editing test steps during recording:
One of the greatest usability improvements it the capability control and edit test steps during test recording. The following options are now available for controlling and editing your test case recording:

  • Pause
    With Pause button you can pause the recording and go to any screen of the application and resume recording from there. This helps when you want to break the tests to several individual tests or if you want to append some new features to existing test sets. (appending of the test code still has to be done by copy/paste).
  • Delete Action
    When the recording is paused you can use delete action button to delete any recorded action before Testdroid Recorder generates the test code. You just highlight the action and press delete. This feature is useful to get rid of unwanted clicks and to remove parts of test recording that are not relevant for a specific test case.
  • Split one recording to several tests
    With New Test Method button you can split your test recording to several test methods (or test cases). During recording you just click New Test Method button, give a name to the new test method and then right click and choose “Set current recording” and off you go! All following activities will go to this new test methods. With this feature you can create test suites that consist of several test cases and can still be executed as one test APK package.

User defined screenshot capture steps during test execution
Quite often just getting pass or fail for each test is not quite enough but also visual verification is needed to ensure right scaling, layout etc. This is the case especially when the same tests are executed on several devices. To help with this we have added a “Take screenshot” button. By clicking this button you can define places in your test case where a screenshot is taken during the test execution. The screenshots are stored to SD-card from where they can be fetched for inspection.

User defined UI widget call methods
Testdroid Recorder let’s you decide in which order the UI widget call methods are used when your Robotium test code is generated. Each of the UI Widget call methods have their pros and cons and it always depends on the application itself which one is the most appropriate and which ones can be used. The options are

  • R.id
    This option is great if you have several localized versions of the same application because by using dynamic widget ID’s you can test all language versions with same test code.
  • Text Label (Clicks UI element with defined string)
    This option is very reliable but is appropriate for applications with one language version only (or you have to record one set of tests for each language version). Also all widgets do not necessarily have text labels but when text labels are available this method creates very solid test cases.
  • x,y click
    x,y clicks are the most basic way to simulate user interaction and this method is used if r.id and text label fails. The limitation with x,y clicks is that they don’t always scale perfectly when tests are executed on different resolutions. Having said that, in many cases x,y clicks can still create quite robust tests.

As you can see Testdroid Recorder is now ready to be rolled out in masses! Naturally there are a lot of good usability and productivity improments in the roadmap but already now you can turbocharge your development productivity and application quality with Testdroid.