page.title=Building Instrumented Unit Tests page.tags=testing,androidjunitrunner,junit,unit test,mock,instrumentation trainingnavtop=true @jd:body

Dependencies and Prerequisites

This lesson teaches you to

Set Up Your Testing Environment
Create a Instrumented Unit Test Class
Run Instrumented Unit Tests

Try it out

Instrumented unit tests are unit tests that run on physical devices and emulators, instead of the Java Virtual Machine (JVM) on your local machine. You should create instrumented unit tests if your tests need access to instrumentation information (such as the target app's {@link android.content.Context}) or if they require the real implementation of an Android framework component (such as a {@link android.os.Parcelable} or {@link android.content.SharedPreferences} object). Using instrumented unit tests also helps to reduce the effort required to write and maintain mock code. You are still free to use a mocking framework, if you choose, to simulate any dependency relationships. Instrumented unit tests can take advantage of the Android framework APIs and supporting APIs, such as the Android Testing Support Library.

Set Up Your Testing Environment

Before building your instrumented unit test, make sure to configure your test source code location and project dependencies, as described in Getting Started with Testing.

Create an Instrumented Unit Test Class

Your instrumented unit test class should be written as a JUnit 4 test class. To learn more about creating JUnit 4 test classes and using JUnit 4 assertions and annotations, see Create a Local Unit Test Class.

To create an instrumented JUnit 4 test class, add the {@code @RunWith(AndroidJUnit4.class)} annotation at the beginning of your test class definition. You also need to specify the {@code AndroidJUnitRunner} class provided in the Android Testing Support Library as your default test runner. This step is described in more detail in Getting Started with Testing

The following example shows how you might write an instrumented unit test to test that the {@link android.os.Parcelable} interface is implemented correctly for the {@code LogHistory} class:

import android.os.Parcel;
import android.support.test.runner.AndroidJUnit4;
import android.util.Pair;
import org.junit.Test;
import org.junit.runner.RunWith;
import java.util.List;
import static org.hamcrest.Matchers.is;
import static org.junit.Assert.assertThat;

@RunWith(AndroidJUnit4.class)
@SmallTest
public class LogHistoryAndroidUnitTest {

    public static final String TEST_STRING = "This is a string";
    public static final long TEST_LONG = 12345678L;
    private LogHistory mLogHistory;

    @Before
    public void createLogHistory() {
        mLogHistory = new LogHistory();
    }

    @Test
    public void logHistory_ParcelableWriteRead() {
        // Set up the Parcelable object to send and receive.
        mLogHistory.addEntry(TEST_STRING, TEST_LONG);

        // Write the data.
        Parcel parcel = Parcel.obtain();
        mLogHistory.writeToParcel(parcel, mLogHistory.describeContents());

        // After you're done with writing, you need to reset the parcel for reading.
        parcel.setDataPosition(0);

        // Read the data.
        LogHistory createdFromParcel = LogHistory.CREATOR.createFromParcel(parcel);
        List<Pair<String, Long>> createdFromParcelData = createdFromParcel.getData();

        // Verify that the received data is correct.
        assertThat(createdFromParcelData.size(), is(1));
        assertThat(createdFromParcelData.get(0).first, is(TEST_STRING));
        assertThat(createdFromParcelData.get(0).second, is(TEST_LONG));
    }
}

Creating a test suite

To organize the execution of your instrumented unit tests, you can group a collection of test classes in a test suite class and run these tests together. Test suites can be nested; your test suite can group other test suites and run all their component test classes together.

A test suite is contained in a test package, similar to the main application package. By convention, the test suite package name usually ends with the {@code .suite} suffix (for example, {@code com.example.android.testing.mysample.suite}).

To create a test suite for your unit tests, import the JUnit {@code RunWith} and {@code Suite} classes. In your test suite, add the {@code @RunWith(Suite.class)} and the {@code @Suite.SuitClasses()} annotations. In the {@code @Suite.SuiteClasses()} annotation, list the individual test classes or test suites as arguments.

The following example shows how you might implement a test suite called {@code UnitTestSuite} that groups and runs the {@code CalculatorInstrumentationTest} and {@code CalculatorAddParameterizedTest} test classes together.

import com.example.android.testing.mysample.CalculatorAddParameterizedTest;
import com.example.android.testing.mysample.CalculatorInstrumentationTest;
import org.junit.runner.RunWith;
import org.junit.runners.Suite;

// Runs all unit tests.
@RunWith(Suite.class)
@Suite.SuiteClasses({CalculatorInstrumentationTest.class,
        CalculatorAddParameterizedTest.class})
public class UnitTestSuite {}

Run Instrumented Unit Tests

To run your test, follow the steps for running instrumented tests described in Getting Started with Testing.