Book Image

Android Application Testing Guide

By : Diego Torres Milano
Book Image

Android Application Testing Guide

By: Diego Torres Milano

Overview of this book

<p>It doesn't matter how much time you invest in Android design, or even how careful you are when programming; mistakes are inevitable and bugs will appear. This book will help you minimize the impact of these errors in your Android project and increase your development productivity. It will show you the problems that are easily avoided, to help get you quickly to the testing stage.<br /><br />Android Application Testing Guide is the first and only book providing a practical introduction to the most common available techniques, frameworks, and tools to improve the development of your Android applications. Clear, step-by-step instructions show how to write tests for your applications and assure quality control using various methodologies.<br /><br />The author's experience in applying application testing techniques to real world projects enables him to share insights on creating professional Android applications. <br /><br />The book starts by introducing Test Driven Development, which is an agile component of the software development process and a technique where you will tackle bugs early on. From the most basic unit tests applied to a sample project to more sophisticated performance tests, this book provides a detailed description of the most widely used techniques in the Android testing world in a recipe-based approach.<br /><br />The author has extensive experience of working on various development projects throughout his professional career. All this research and knowledge has helped create a book that will serve as a useful resource to any developer navigating the world of Android testing.</p>
Table of Contents (17 chapters)
Android Application Testing Guide
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Getting started with TDD


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

A single test is added, then the code needed to satisfy the compilation of this test and finally the full set of test cases is run to verify their results.

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 several advantages. First, is that the tests are written in one way or another, while if the tests are left till the end it is highly probable that they are never written. Second, developers take more responsibility for the quality of their work.

Design decisions are taken in single steps and finally the code satisfying the tests is improved by refactoring it.

This UML activity diagram depicts the Test Driven Development to help us understand...