Added in API level 1
Deprecated in API level 5

ProviderTestCase

Kotlin |Java

abstract class ProviderTestCase<T : ContentProvider!> : InstrumentationTestCase

kotlin.Any
↳	android.test.InstrumentationTestCase
	↳	android.test.ProviderTestCase

If you would like to test a single content provider with an InstrumentationTestCase, this provides some of the boiler plate in setUp and tearDown.

Summary

Public constructors
`ProviderTestCase(providerClass: Class<T>!, providerAuthority: String!)`

Public methods
open MockContentResolver!	`getMockContentResolver()`
open IsolatedContext!	`getMockContext()`
open T	`getProvider()`
open static ContentResolver!	`newResolverWithContentProviderFromSql(targetContext: Context!, providerClass: Class<T>!, authority: String!, databaseName: String!, databaseVersion: Int, sql: String!)`

Protected methods
open Unit	`setUp()`
open Unit	`tearDown()` Tears down the environment for the test fixture.

Inherited functions

From class InstrumentationTestCase

`Instrumentation!`	`getInstrumentation()` Inheritors can access the instrumentation using this.
`Unit`	`injectInsrumentation(instrumentation: Instrumentation!)` Injects instrumentation into this test case. This method is called by the test runner during test setup.
`Unit`	`injectInstrumentation(instrumentation: Instrumentation!)` Injects instrumentation into this test case. This method is called by the test runner during test setup.
`T`	`launchActivity(pkg: String!, activityCls: Class<T>!, extras: Bundle!)` Utility method for launching an activity. The `Intent` used to launch the Activity is: action = `Intent.ACTION_MAIN` extras = null, unless a custom bundle is provided here All other fields are null or empty. NOTE: The parameter pkg must refer to the package identifier of the package hosting the activity to be launched, which is specified in the AndroidManifest.xml file. This is not necessarily the same as the java package name.
`T`	`launchActivityWithIntent(pkg: String!, activityCls: Class<T>!, intent: Intent!)` Utility method for launching an activity with a specific Intent. NOTE: The parameter pkg must refer to the package identifier of the package hosting the activity to be launched, which is specified in the AndroidManifest.xml file. This is not necessarily the same as the java package name.
`Unit`	`runTest()` Runs the current unit test. If the unit test is annotated with `android.test.UiThreadTest`, the test is run on the UI thread.
`Unit`	`runTestOnUiThread(r: Runnable!)` Helper for running portions of a test on the UI thread. Note, in most cases it is simpler to annotate the test method with `android.test.UiThreadTest`, which will run the entire test method on the UI thread. Use this method if you need to switch in and out of the UI thread to perform your test.
`Unit`	`sendKeys(vararg keys: Int)` Sends a series of key events through instrumentation and waits for idle. For instance: sendKeys(KEYCODE_DPAD_LEFT, KEYCODE_DPAD_CENTER).
`Unit`	`sendKeys(keysSequence: String!)` Sends a series of key events through instrumentation and waits for idle. The sequence of keys is a string containing the key names as specified in KeyEvent, without the KEYCODE_ prefix. For instance: sendKeys("DPAD_LEFT A B C DPAD_CENTER"). Each key can be repeated by using the N* prefix. For instance, to send two KEYCODE_DPAD_LEFT, use the following: sendKeys("2*DPAD_LEFT").
`Unit`	`sendRepeatedKeys(vararg keys: Int)` Sends a series of key events through instrumentation and waits for idle. Each key code must be preceded by the number of times the key code must be sent. For instance: sendRepeatedKeys(1, KEYCODE_DPAD_CENTER, 2, KEYCODE_DPAD_LEFT).

Public constructors

ProviderTestCase

Added in API level 1

ProviderTestCase(
    providerClass: Class<T>!, 
    providerAuthority: String!)