Home » Google » Page 4

Tag: Google

[Video] Breaking the Matrix – Android Testing at Scale

Today, I want to share a video with you. The topic of the video is “Breaking the Matrix – Android Testing at Scale” and shows a talk from Google employees explaining how to scale your Android test automation using emulators.

Testing Android apps manually on emulators is not my first choice, however at some point it makes sense to use them as a part of your mobile test automation strategy to save time and money.

How is oour Android testing environment look like? Are you using emulators in your test environment?

Have a great day and happy mobile testing.

How to record your Android tests with Robotium Recorder

A couple of weeks ago, I wrote a post about the release of Robotium Recorder.
Today I want to show you, how to install and how to use the tool to record your Android tests. This tutorial based on the example Notepad app provided by the Robotium project, the source code can be found here.

Prerequisites & Installation

Before you start with recording, you have to install the Java JDK and the Android SDK. Be sure you have the latest version of the Android SDK installed or updated. If your development environment is up to date, you can import the sample app, provided by the Robotium project. Please follow the instructions in the sample, on how to insert the existing project to eclipse.

If Java, the Android SDK and the sample project is downloaded and installed, start Eclipse and open the Install New Software section in the Help menu (Help → Install New Software). In the input field “Work with” enter: http://recorder.robotium.com/updates and Press the Add… button and enter a name for the installation.

1_install_robotium_via_help

Read more

Espresso for Android

Last week the google Android team announced the launch of the developer preview for Espresso. Espresso is the new UI testing tool presented at the GTAC earlier this year. In the google testing blog it says:

The compelling thing about developing Espresso was making it easy and fun for developers to write reliable UI tests. Espresso has a small, predictable, and easy to learn API, which is still open for customization. But most importantly – Espresso removes the need to think about the complexity of multi-threaded testing. With Espresso, you can think procedurally and write concise, beautiful, and reliable Android UI tests quickly.

Google is using Espresso in more than 30 applications by now e.g. Google(Drive, Maps or G+). I just had a really quick look at the documentation and example of the tool and its looking quite nice. I will try it in the next couple of weeks and will post my impression here.


Find the Espresso sources here:

Espresso at GTAC 2013

Have fun!

How to improve your mobile testing skills

In the last couple of months I was asked by several people how I improve my mobile testing skills. The mobile world is changing quite fast and you have to keep the pace, if you want to be a good and up to date mobile tester.

I recommended to read lots of QA related blogs, read QA books, follow the right people on twitter, try new mobile testing tools at home or at work (if you have the time) to get a broader knowledge in the mobile area. Another thing I recommended was to do new things (be creative while testing), try new testing techniques or just try to break the app in a crazy way. Furthermore I recommended another way of improve the own skills. Use as many apps as possible from different categories to see how apps are developed and how they behave. Besides using them, the important thing is, check the update texts of the apps! Do not just install the latest version of the app, read before installing the app. Some app developers are really precise in what the new version of the app is all about. Which nasty bug was fixed, which new feature is developed and so on.
If there are bug fixes described, don’t install the new version, instead try to reproduce the bug and see how to get this bug to life!

Here are some examples of apps that descibed very well, what was fixed: Read more