Please note that the contents of this offline web site may be out of date. To access the most recent documentation visit the online version .
Note that links that point to online resources are green in color and will open in a new window.
We would love it if you could give us feedback about this material by filling this form (You have to be online to fill it)
Android APIs
public abstract class

ApplicationTestCase

extends AndroidTestCase
java.lang.Object
   ↳ junit.framework.Assert
     ↳ junit.framework.TestCase
       ↳ android.test.AndroidTestCase
         ↳ android.test.ApplicationTestCase<T extends  android.app.Application >

Class Overview

This test case provides a framework in which you can test Application classes in a controlled environment. It provides basic support for the lifecycle of a Application, and hooks by which you can inject various dependencies and control the environment in which your Application is tested.

Lifecycle Support. Every Application is designed to be accessed within a specific sequence of method calls (see Application for more details). In order to support the lifecycle of a Application, this test case will make the following calls at the following times.

  • The test case will not call onCreate() until your test calls createApplication() . This gives you a chance to set up or adjust any additional framework or test logic before onCreate().
  • After your test completes, the test case tearDown() method is automatically called, and it will stop & destroy your application by calling its onDestroy() method.

Dependency Injection. Every Application has one inherent dependency, the Context in which it runs. This framework allows you to inject a modified, mock, or isolated replacement for this dependencies, and thus perform a true unit test.

If simply run your tests as-is, your Application will be injected with a fully-functional Context. You can create and inject alternative types of Contexts by calling setContext() . You must do this before calling createApplication() . The test framework provides a number of alternatives for Context, including MockContext , RenamingDelegatingContext , and ContextWrapper .

Summary

[Expand]
Inherited Fields
From class android.test.AndroidTestCase
Public Constructors
)">ApplicationTestCase ( Class <T> applicationClass)
Public Methods
T getApplication ()
Context getSystemContext ()
Return a real (not mocked or instrumented) system Context that can be used when generating Mock or other Context objects for your Application under test.
final void testApplicationTestCaseSetUpProperly ()
This test simply confirms that the Application class can be instantiated properly.
Protected Methods
final void createApplication ()
Start the Application under test, in the same way as if it was started by the system.
void setUp ()
This will do the work to instantiate the Application under test.
void tearDown ()
Shuts down the Application under test.
final void terminateApplication ()
This will make the necessary calls to terminate the Application under test (it will call onTerminate().
[Expand]
Inherited Methods
From class android.test.AndroidTestCase
From class junit.framework.TestCase
From class junit.framework.Assert
From class java.lang.Object
From interface junit.framework.Test

Public Constructors

)">

public ApplicationTestCase ( Class <T> applicationClass)

Added in API level 1

Public Methods

public T getApplication ()

Added in API level 1

Returns
  • Returns the actual Application under test.

public Context getSystemContext ()

Added in API level 1

Return a real (not mocked or instrumented) system Context that can be used when generating Mock or other Context objects for your Application under test.

Returns
  • Returns a reference to a normal Context.

public final void testApplicationTestCaseSetUpProperly ()

Added in API level 1

This test simply confirms that the Application class can be instantiated properly.

Protected Methods

protected final void createApplication ()

Added in API level 1

Start the Application under test, in the same way as if it was started by the system. If you use this method to start the Application, it will automatically be stopped by tearDown() . If you wish to inject a specialized Context for your test, by calling setContext() , you must do so before calling this method.

protected void setUp ()

Added in API level 1

This will do the work to instantiate the Application under test. After this, your test code must also start and stop the Application.

protected void tearDown ()

Added in API level 1

Shuts down the Application under test. Also makes sure all resources are cleaned up and garbage collected before moving on to the next test. Subclasses that override this method should make sure they call super.tearDown() at the end of the overriding method.

protected final void terminateApplication ()

Added in API level 1

This will make the necessary calls to terminate the Application under test (it will call onTerminate(). Ordinarily this will be called automatically (by tearDown() , but you can call it directly from your test in order to check for proper shutdown behaviors.