Some test cases have the need to exercise databases or ContentProviders operations, and soon comes the need to mock these operations. For example, if we are testing an application on a real device, we don't want to interfere with the normal operation of applications on such devices, mainly when we change values that may be shared by more than one application.
Such cases can take advantage of another mock class that is not a part of
android.test.mock package but of
android.test instead, namely
This class lets us mock file and database operations. A prefix supplied in the constructor is used to modify the target of these operations. All other operations are delegated to the ...