The following is the first few sections of a chapter from The Busy Coder's Guide to Android Development, plus headings for the remaining major sections, to give you an idea about the content of the chapter.

Measuring Test Coverage

Test coverage is our way of determining whether or not we have adequately tested our code. Part of the work that has gone into the Android Gradle Plugin has been to make obtaining test coverage reports fairly easy, so ideally it is something that you can incorporate into your regular testing regimen.

In this chapter, we will explore the concept of test coverage in general, along with how to generate coverage reports for your Android instrumentation tests.


Understanding this chapter requires that you have read the chapter on instrumentation testing with JUnit.

Who Tests the Testers?

The preview of this section is being chased by zombies.

Some Types of Test Coverage

The preview of this section will not appear here for a while, due to a time machine mishap.

Coverage and Your Instrumentation Tests

The preview of this section is off trying to sweet-talk the Khaleesi into providing us with a dragon.