public abstract class ProviderTestCase2<T extends ContentProvider> extends AndroidTestCase
ContentProvider
and for testing your app code with an
isolated content provider. Instead of using the system map of
providers that is based on the manifests of other applications, the test
case creates its own internal map. It then uses this map to resolve providers
given an authority. This allows you to inject test providers and to null out
providers that you do not want to use.
This test case also sets up the following mock objects:
IsolatedContext
that stubs out Context methods that might
affect the rest of the running system, while allowing tests to do real file and
database work.
MockContentResolver
that provides the functionality of a
regular content resolver, but uses IsolatedContext
. It stubs out
ContentResolver.notifyChange(Uri, ContentObserver, boolean)
to
prevent the test from affecting the running system.
IsolatedContext
.
This framework is set up automatically by the base class' setUp()
method. If you
override this method, you must call the super method as the first statement in
your override.
In order for their tests to be run, concrete subclasses must provide their own
constructor with no arguments. This constructor must call
ProviderTestCase2(Class, String)
as its first operation.
mContext
Constructor and Description |
---|
ProviderTestCase2(Class<T> providerClass,
String providerAuthority)
Constructor.
|
Modifier and Type | Method and Description |
---|---|
MockContentResolver |
getMockContentResolver()
Gets the
MockContentResolver created by this class during initialization. |
IsolatedContext |
getMockContext()
Gets the
IsolatedContext created by this class during initialization. |
T |
getProvider()
Returns the content provider created by this class in the
setUp() method. |
static <T extends ContentProvider> |
newResolverWithContentProviderFromSql(Context targetContext,
String filenamePrefix,
Class<T> providerClass,
String authority,
String databaseName,
int databaseVersion,
String sql)
Creates a new content provider of the same type as that passed to the test case class,
with an authority name set to the authority parameter, and using an SQLite database as
the underlying data source.
|
protected void |
setUp()
Sets up the environment for the test fixture.
|
protected void |
tearDown()
Tears down the environment for the test fixture.
|
assertActivityRequiresPermission, assertReadingContentUriRequiresPermission, assertWritingContentUriRequiresPermission, getContext, getTestContext, scrubClass, setContext, setTestContext, testAndroidTestCaseSetupProperly
public T getProvider()
setUp()
method.protected void setUp() throws Exception
Creates a new
MockContentResolver
, a new IsolatedContext
that isolates the provider's file operations, and a new instance of
the provider under test within the isolated environment.
setUp
in class AndroidTestCase
Exception
protected void tearDown() throws Exception
Calls ContentProvider.shutdown()
on the
ContentProvider
represented by mProvider.
tearDown
in class AndroidTestCase
Exception
public MockContentResolver getMockContentResolver()
MockContentResolver
created by this class during initialization. You
must use the methods of this resolver to access the provider under test.MockContentResolver
instance.public IsolatedContext getMockContext()
IsolatedContext
created by this class during initialization.IsolatedContext
instancepublic static <T extends ContentProvider> ContentResolver newResolverWithContentProviderFromSql(Context targetContext, String filenamePrefix, Class<T> providerClass, String authority, String databaseName, int databaseVersion, String sql) throws IllegalAccessException, InstantiationException
Creates a new content provider of the same type as that passed to the test case class,
with an authority name set to the authority parameter, and using an SQLite database as
the underlying data source. The SQL statement parameter is used to create the database.
This method also creates a new MockContentResolver
and adds the provider to it.
Both the new provider and the new resolver are put into an IsolatedContext
that uses the targetContext parameter for file operations and a MockContext
for everything else. The IsolatedContext prepends the filenamePrefix parameter to
file, database, and directory names.
This is a convenience method for creating a "mock" provider that can contain test data.
targetContext
- The context to use as the basis of the IsolatedContextfilenamePrefix
- A string that is prepended to file, database, and directory namesproviderClass
- The type of the provider being testedauthority
- The authority string to associated with the test providerdatabaseName
- The name assigned to the databasedatabaseVersion
- The version assigned to the databasesql
- A string containing the SQL statements that are needed to create the desired
database and its tables. The format is the same as that generated by the
sqlite3 tool's .dump
command.MockContentResolver
linked to the providerIllegalAccessException
InstantiationException