|

Introduction to Android Testing Presented by Amy Klatt July 25, 2012

|

Agenda

• Overview

• Best practices

• Installing apps

• Setting up a test environment

• Screenshots and video

• Logs

• Q & A

2

The Challenge

| | 3

Overview

|

Overview

Why is “in the wild testing” so important?

4

Android as a testing platform is highly

fragmented and diverse.

As of mid 2012, there were nearly 4,000 unique

makes and models of Android devices on the

market.

|

Overview

• These devices have an immense number of

different hardware specifications and screen

sizes.

• These devices may be running any of at least a

dozen different versions of Android.

• There are hundreds of mobile carriers with

different network quality conditions to consider.

5

|

Overview

• uTest plays an vital role in mobile app testing.

• Helping a developer test across the spectrum of

device configurations can be crucial to an app’s

success.

• Submitting quality bugs is important!

• We can affect the outcome of testing positively by

filing useful, high quality bugs.

6

The Challenge

| | 7

Best Practices

|

Best Practices

As with any other test cycle, bugs should follow

standard uTest conventions and guidelines.

Do include:

• Clear, actionable steps to reproduce

• Useful documentation

Quality attachments are important. Your bug might

not occur across every device.

This is your evidence the bug actually exists!

8

|

Best Practices

What documentation should I include?

It’s helpful to include:

• Screenshots

• Videos

• Logs

• The exact error message (if needed)

Does my bug really need a log?

Do I need to make a video or is a screenshot OK?

9

The Challenge

| | 10

Installing apps

|

Installing apps

First, make sure your phone is set to allow non-

market apps.

Then, do one of the following:

• Drag and drop

• Send via Bluetooth

• Email the file to yourself

What if I get an error when I try to install?

Is an installation error always a bug?

11

The Challenge

| |

Setting up a test environment

12

|

Setting up a test environment

Setting up the Android SDK

• Install the USB driver for your phone

• Install the Java JDK

• Install the Android SDK

• Download the required packages

• Add the SDK tools location to your path

This allows you to use tools such as ADB to obtain

logs and take screenshots.

13

The Challenge

| | 14

Demo:

Setting up the Android SDK

The Challenge

| | 15

Tools:

Logs and screenshots

|

Utilities - Screencast

Having the Android SDK installed will allow you to

take screenshots and screencasts.

Some useful tools:

• Droid Explorer (Windows only)

• Android Screencast

• Droid@Screen

• Jing

You can use these tools while your device is

connected to your computer.

16

|

Utilities - Logs

Use ADB to capture logs.

Different types of logs:

• Catlog

• Traces.txt

• Tombstones.txt

• Bug or crash reports

A catlog will be sufficient for most purposes, but

you may be asked to provide other logs.

17

|

Utilities - Logs

You can also capture browser debugging

information on an Android device.

Use the command “about:debug” in your browser’s

address bar to output errors to the console.

The error output will also be captured in your catlog

output.

This is helpful for testing mobile websites.

18

|

Summary

As you test Android mobile applications and

websites, be sure to do the following:

• Write high quality bugs

• Provide clear steps to reproduce

• Attach useful documentation

• Use tools and utilities to help demonstrate the

issue you’re reporting.

19

The Challenge

| | 20

Thank You

Questions?