6. Practicing Test-driven Development | Learning Android Application Testing

Sign In Start Free Trial

Book Overview & Buying
Table Of Contents
Feedback & Rating

Learning Android Application Testing

By : Paul Blundell

3.8 (4)

Learning Android Application Testing

3.8 (4)

By: Paul Blundell

Overview of this book

If you are an Android developer looking to test your applications or optimize your application development process, then this book is for you. No previous experience in application testing is required.

Preface

Preface

What this book covers

What you need for this book

Who this book is for

Conventions

Reader feedback

Customer support

Free Chapter

1. Getting Started with Testing

1. Getting Started with Testing

Why, what, how, and when to test?

Types of tests

Java testing framework

Android testing framework

Creating the Android project

Summary

2. Understanding Testing with the Android SDK

2. Understanding Testing with the Android SDK

The demonstration application

Assertions in depth

View assertions

Even more assertions

The TouchUtils class

Mock objects

The TestCase base class

The AndroidTestCase base class

Instrumentation

The InstrumentationTestCase class

The ActivityTestCase class

The ActivityInstrumentationTestCase2 class

The ProviderTestCase2 class

The ServiceTestCase

The TestSuiteBuilder.FailedToCreateTests class

Using libraries in test projects

Summary

3. Baking with Testing Recipes

3. Baking with Testing Recipes

Android unit tests

Testing activities and applications

Testing files, databases, and content providers

Testing exceptions

Testing local and remote services

Extensive use of mock objects

Testing views in isolation

Testing parsers

The parser test

Testing for memory usage

Testing with Espresso

Summary

4. Managing Your Android Testing Environment

4. Managing Your Android Testing Environment

Creating Android Virtual Devices

Running AVDs from the command line

Additional emulator configurations

Speeding up your AVD with HAXM

Alternatives to the AVD

Running monkey

Test scripting with monkeyrunner

Summary

5. Discovering Continuous Integration

5. Discovering Continuous Integration

Building Android applications manually using Gradle

Git – the fast version control system

Continuous integration with Jenkins

Summary

6. Practicing Test-driven Development

6. Practicing Test-driven Development

Getting started with TDD

Creating a sample project – the temperature converter

Creating a Java module

Creating the TemperatureConverterActivityTests class

Adding functionality

Viewing our final application

Summary

7. Behavior-driven Development

7. Behavior-driven Development

Given, When, and Then

FitNesse

GivWenZen

Summary

8. Testing and Profiling Performance

8. Testing and Profiling Performance

Ye Olde Logge method

Timing logger

Performance tests in Android SDK

Using the Traceview and dmtracedump platform tools

Dmtracedump

Microbenchmarks

Summary

9. Alternative Testing Tactics

9. Alternative Testing Tactics

Code coverage

Temperature converter code coverage

Introducing Robotium

Testing on the host's JVM

Introducing Robolectric

Google's march on shadows

Introducing Fest

Introducing Spoon

Introducing Fork

Summary

Index

Index

Customer Reviews

3.8 (4)

5 star

25%

4 star

50%

3 star

0%

2 star

25%

1 star

0%

Getting started with TDD

Briefly, Test-driven Development is the strategy of writing tests in parallel with the development process. These test cases are written in advance of the code that is supposed to satisfy them.

A single test is written, and then the code needed to satisfy the compilation of this test is written, then the behavior that the test decrees should exist is written. We continue writing tests and implementation until the full set of desired behaviors is checked by the tests.

This contrasts with other approaches to the development process, where the tests are written at the end when all the coding has been done.

Writing the tests in advance of the code that satisfies them has the following advantages:

Tests get written one way or another, while if the tests are left till the end it is highly probable that they will never be written
Developers take more responsibility for the quality of their work, when having to consider the tests as they code

Design decisions are taken in smaller...

Visually different images

CONTINUE READING

83

Tech Concepts

36

Programming languages

73

Tech Tools

Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.

Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.

50+ new titles added per month and exclusive early access to books as they are being written.

Learning Android Application Testing

Search

Your notes and bookmarks