java.lang.Object | ||||
↳ | junit.framework.Assert | |||
↳ | junit.framework.TestCase | |||
↳ | android.test.AndroidTestCase | |||
↳ | android.test.ApplicationTestCase<T extends android.app.Application> |
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.
createApplication()
. This gives you a chance
to set up or adjust any additional framework or test logic before
onCreate().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
.
[Expand]
Inherited Fields | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
From class
android.test.AndroidTestCase
|
Public Constructors | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Public Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
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.
| |||||||||||
This test simply confirms that the Application class can be instantiated properly.
|
Protected Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Start the Application under test, in the same way as if it was started by the system.
| |||||||||||
This will do the work to instantiate the Application under test.
| |||||||||||
Shuts down the Application under test.
| |||||||||||
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
|
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.
This test simply confirms that the Application class can be instantiated properly.
Exception |
---|
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.
This will do the work to instantiate the Application under test. After this, your test code must also start and stop the Application.
Exception |
---|
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.
Exception |
---|
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.