IT. Expert System.

Android Reference



Class ApplicationTestCase<T extends Application>

  • public abstract class ApplicationTestCase<T extends Application>
    extends AndroidTestCase
    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.

    • Constructor Detail

      • ApplicationTestCase

        public ApplicationTestCase(Class<T> applicationClass)
    • Method Detail

      • getApplication

        public T getApplication()
        Returns the actual Application under test.
      • setUp

        protected void setUp()
                      throws Exception
        This will do the work to instantiate the Application under test. After this, your test code must also start and stop the Application.
        setUp in class AndroidTestCase
      • createApplication

        protected final void createApplication()
        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.
      • terminateApplication

        protected final void terminateApplication()
        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.
      • tearDown

        protected void tearDown()
                         throws 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.
        tearDown in class AndroidTestCase
      • getSystemContext

        public 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.
        Returns a reference to a normal Context.
      • testApplicationTestCaseSetUpProperly

        public final void testApplicationTestCaseSetUpProperly()
                                                        throws Exception
        This test simply confirms that the Application class can be instantiated properly.


Android Reference

Java basics

Java Enterprise Edition (EE)

Java Standard Edition (SE)





Java Script








Design patterns

RFC (standard status)

RFC (proposed standard status)

RFC (draft standard status)

RFC (informational status)

RFC (experimental status)

RFC (best current practice status)

RFC (historic status)

RFC (unknown status)

IT dictionary

All information of this service is derived from the free sources and is provided solely in the form of quotations. This service provides information and interfaces solely for the familiarization (not ownership) and under the "as is" condition.
Copyright 2016 © ELTASK.COM. All rights reserved.
Site is optimized for mobile devices.
Downloads: 103 / 158848782. Delta: 0.04852 с