ProviderTestRule.Builder
public class ProviderTestRule.Builder
A Builder to ease ProviderTestRule creation. Users can input one or more ContentProviders and their corresponding authority for tests. It also allows to specify the prefix to use when renaming test files for isolation by setPrefix. If the ContentProvider under test is implemented based on SQLiteDatabase, users can also pass in database file to restore or database commands to run before tests.
Summary
Public constructors |
|---|
|
The basic builder to use when creating a |
Public methods |
|
|---|---|
ProviderTestRule.Builder |
<T extends ContentProvider> Allows to add additional ContentProvider and the corresponding authority for testing. |
ProviderTestRule |
|
ProviderTestRule.Builder |
Allows to pass in specific SQL commands to run against the database with a given name. |
ProviderTestRule.Builder |
Allows to pass in a file containing commands to run against the database with a given name. |
ProviderTestRule.Builder |
Allows to pass in a SQLite database file containing the intended initial data to restore. |
ProviderTestRule.Builder |
Enables users to specify the prefix to use when renaming test files for isolation. |
Public constructors
Builder
public <T extends ContentProvider>Builder(
@NonNull Class<T> providerClass,
@NonNull String providerAuth
)
The basic builder to use when creating a ProviderTestRule, which allows to specify one ContentProvider and the corresponding authority for tests.
Public methods
addProvider
public ProviderTestRule.Builder <T extends ContentProvider>addProvider(
@NonNull Class<T> providerClass,
@NonNull String providerAuth
)
Allows to add additional ContentProvider and the corresponding authority for testing. Similarly, setDatabaseFile, setDatabaseCommands, setDatabaseCommandsFile, and runDatabaseCommands can be used for this ContentProvider.
setDatabaseCommands
public ProviderTestRule.BuildersetDatabaseCommands(@NonNull String dbName, @NonNull String[] dbCmds)
Allows to pass in specific SQL commands to run against the database with a given name.
Note: The passed in commands are executed before any sql commands execution in
SQLiteOpenHelper's onCreate method defined in ContentProvider under test, also before executing commands, if any, passed in via setDatabaseCommandsFile, but after restoring the database file, if any, passed in via setDatabaseFile.
setDatabaseCommandsFile
public ProviderTestRule.BuildersetDatabaseCommandsFile(@NonNull String dbName, @NonNull File dbCmdFile)
Allows to pass in a file containing commands to run against the database with a given name.
Note: Commands in the file are executed before any sql commands execution in
SQLiteOpenHelper's onCreate method defined in ContentProvider under test, but after restoring the database file, if any, passed in via setDatabaseFile and executing commands, if any, passed in via setDatabaseCommands.
setDatabaseFile
public ProviderTestRule.BuildersetDatabaseFile(@NonNull String dbName, @NonNull File dbDataFile)
Allows to pass in a SQLite database file containing the intended initial data to restore.
Note: Restoring the database from the file are executed before any sql commands execution in SQLiteOpenHelper's onCreate method defined in ContentProvider under test, also before running the database commands, if any, passed in via setDatabaseCommands and setDatabaseCommandsFile.
In the case of the database file with prefixed name already exists, the database restoration will overwrite existing file.
setPrefix
public ProviderTestRule.BuildersetPrefix(@NonNull String prefix)
Enables users to specify the prefix to use when renaming test files for isolation. If not used, this rule will use "#DEFAULT_PREFIX" by default.