Android Application Testing Guide

Android Application Testing Guide

Diego Torres Milano

Language: English

Pages: 332

ISBN: 1849513503

Format: PDF / Kindle (mobi) / ePub

Adroid Application Testing Guide is a highly detailed book which gives step-by-step examples for a great variety of real-world cases, providing professional guidelines and recommendations that will be extremely valuable for optimizing your development time and resources. In the chapters you will find an introduction to specific testing techniques, and tools for specific situations. 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.




















news is that you have all of these alternatives available to run your tests. The emulator is probably the most powerful target as you can modify almost every parameter from its configuration to simulate different conditions for your tests. Ultimately, your application should be able to handle all of these situations, so it is much better to discover the problems upfront than when the application has been delivered. [ 25 ] Getting Started with Testing The real devices are a requirement for

is to use a default constant test case name in this constructor and invoke the Given name constructor afterwards. public class MyTestCase extends TestCase { public MyTestCase() { this("MyTestCase Default Name"); } public MyTestCase(String name) { super(name); } } The given name constructor This constructor takes a name as an argument to give to the test case. It will appear in test reports and will be helpful when you try to identify failed tests. The setName() method There are some classes

ActivityInstrumentationTestCase2.getActivity() method has a side effect. If the Activity under test is not running, it is started. This may change the intention of a test if we use getActivity() as a simple accessor several times in a test and for some reason the Activity finishes or crashes before test completion. We will be inadvertently restarting the Activity, that is why in our tests we discourage the use of getActivity() in favor of having it in the fixture. Test preconditions We

analyze the evolution of your changes. This feature is accessed by clicking Test History at the bottom of the list of options on the left pane. In the following image we can see the results for the last 4 test runs, where 3 failed and 1 succeeded. Also by clicking on the "+" (plus) or "-" (minus) signs, you can expand or collapse the view to show or hide detailed information about the test run. GivWenZen GivWenZen is a framework that builds upon FitNesse and Slim to allow the user to exploit

are much less useful * in this configuration. It's more useful here to concentrate * on tests that involve the * underlying data model, internal business logic, or exercising * your Activity's life cycle. * *

See {@link} for * documentation on running * all tests and individual tests in this application. */ public class ForwardingTest extends ActivityUnitTestCase { private Intent mStartIntent; private Button mButton; public ForwardingTest() {

Download sample