Erik Hellman - Android Programming Pushing the Limits by 2014

Author:2014
Format: epub
Published: 0101-01-01T00:00:00+00:00

Chapter 10: Writing Automated Tests 201

In a real-life application, you would add additional tests that cover many more cases to ensure that everything is

handled correctly. Let this serve as a guideline for how to write tests for your own ContentProviders.

Running Tests

To run your test, you can either use the built-in feature of Android Studio or execute Gradle from the command

line with the task connectedInstrumentTest. During a normal development cycle, using the built-in

runner from Android Studio is recommended because it gives you full integration between the test results and

your code. Figure 10-1 shows an example of how to configure a test-runner from within Android Studio.

Figure 10-1 Custom test run configuration in Android Studio

When developing a new feature, the temptation to run all your test cases every time you want to verify your

code can be impractical because of the time involved in your development cycle. To manage this issue, you can

define custom test suites and test runners that execute only a partial set of your tests cases.

The following example shows how to create a test runner that executes only the tests from

MainActivityTest shown earlier. This approach is useful when you’re focusing on developing a new UI

feature and want to perform only the tests that relate to that feature.

public class MyTestRunner extends InstrumentationTestRunner {

@Override

public TestSuite getAllTests() {

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.