ForwardingTest.javaAPI DocAndroid 1.5 API5367Wed May 06 22:41:08 BST


public class ForwardingTest extends android.test.ActivityUnitTestCase
This demonstrates completely isolated "unit test" of an Activity class.

This model for testing creates the entire Activity (like {@link Focus2ActivityTest}) but does not attach it to the system (for example, it cannot launch another Activity). It allows you to inject additional behaviors via the {@link android.test.ActivityUnitTestCase#setActivityContext(Context)} and {@link android.test.ActivityUnitTestCase#setApplication(} methods. It also allows you to more carefully test your Activity's performance Writing unit tests in this manner requires more care and attention, but allows you to test very specific behaviors, and can also be an easier way to test error conditions.

Because ActivityUnitTestCase creates the Activity under test completely outside of the usual system, tests of layout and point-click UI interaction 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.

Fields Summary
private android.content.Intent
private android.widget.Button
Constructors Summary
public ForwardingTest()

Methods Summary
protected voidsetUp()


        // In setUp, you can create any shared test data, or set up mock components to inject
        // into your Activity.  But do not call startActivity() until the actual test methods.
        mStartIntent = new Intent(Intent.ACTION_MAIN);
public voidtestLifeCycleCreate()
This test demonstrates ways to exercise the Activity's life cycle.

        Forwarding activity = startActivity(mStartIntent, null, null);
        // At this point, onCreate() has been called, but nothing else
        // Complete the startup of the activity
        // At this point you could test for various configuration aspects, or you could 
        // use a Mock Context to confirm that your activity has made certain calls to the system
        // and set itself up properly.
        // At this point you could confirm that the activity has paused properly, as if it is
        // no longer the topmost activity on screen.
        // At this point, you could confirm that the activity has shut itself down appropriately,
        // or you could use a Mock Context to confirm that your activity has released any system
        // resources it should no longer be holding.

        // ActivityUnitTestCase.tearDown(), which is always automatically called, will take care
        // of calling onDestroy().
public voidtestPreconditions()
The name 'test preconditions' is a convention to signal that if this test doesn't pass, the test case was not set up properly and it might explain any and all failures in other tests. This is not guaranteed to run before other tests, as junit uses reflection to find the tests.

        startActivity(mStartIntent, null, null);
        mButton = (Button) getActivity().findViewById(;
public voidtestSubLaunch()
This test demonstrates examining the way that activity calls startActivity() to launch other activities.

        Forwarding activity = startActivity(mStartIntent, null, null);
        mButton = (Button) activity.findViewById(;
        // This test confirms that when you click the button, the activity attempts to open
        // another activity (by calling startActivity) and close itself (by calling finish()).