{"id":1755,"date":"2015-04-09T02:20:09","date_gmt":"2015-04-09T09:20:09","guid":{"rendered":"http:\/\/wiebe-elsinga.com\/blog\/?p=1755"},"modified":"2015-04-09T02:21:33","modified_gmt":"2015-04-09T09:21:33","slug":"whats-new-in-android-testing","status":"publish","type":"post","link":"http:\/\/wiebe-elsinga.com\/blog\/whats-new-in-android-testing\/","title":{"rendered":"What\u2019s new in Android Testing"},"content":{"rendered":"
\n<\/div>\n\n

<\/p>\n

During Droidcon Italy Stephan Linzner<\/a> from Google explained upcoming features in the Android Testing Support Library<\/a>. Lets have a closer look at some:
\n
\n<\/p>\n

Test Filtering<\/h3>\n

If you want to suppress a test to run on certain target Api levels, just add the @<\/span>SdkSuppress<\/span><\/code> annotation.<\/p>\n

@SdkSuppress(<\/span>minSdkVersion=<\/span>15<\/span>)<\/span>
\n@Test
\npublic<\/span> void<\/span> featureWithMinSdk15(<\/span>)<\/span> {<\/span>
\n  ...
\n}<\/span><\/div><\/div>\n

You can also filter tests to only run on a (physical) device by adding the @<\/span>RequiresDevice<\/span><\/code> annotation.<\/p>\n

@RequiresDevice
\n@Test
\npublic<\/span> void<\/span> SomeDeviceSpecificFeature(<\/span>)<\/span> {<\/span>
\n  ...
\n}<\/span><\/div><\/div>\n

<\/p>\n

ActivityTestRule<\/h3>\n

Because ActivityInstrumentationTestCase2<\/span><\/code> will become deprecated you need to define a @<\/span>Rule.<\/span><\/code><\/p>\n

Rules allow very flexible addition or redefinition of the behavior of each test method in a test class<\/p><\/blockquote>\n

https:\/\/github.com\/junit-team\/junit\/wiki\/Rules<\/small><\/div>\n

\nSo in your test add a @<\/span>Rule<\/span><\/code> annotation, and create an ActivityTestRule<\/span><\/code> for your Activity<\/p>\n

@RunWith(<\/span>AndroidJUnit4.class<\/span>)<\/span>
\n@LargeTest
\npublic<\/span> class<\/span> ChangeTextBehaviorTest {<\/span>
\n    ...
\n
\n    @Rule
\n    public<\/span> ActivityTestRule<<\/span>MainActivity><\/span> mActivityRule =<\/span> new<\/span> ActivityTestRule<><\/span>(<\/span>MainActivity.class<\/span>)<\/span>;<\/span>
\n
\n    @Test
\n    public<\/span> void<\/span> changeText_sameActivity(<\/span>)<\/span> {<\/span>
\n        \/\/ Type text and then press the button.<\/span>
\n        onView(<\/span>withId(<\/span>R.id<\/span>.editTextUserInput<\/span>)<\/span>)<\/span>.perform<\/span>(<\/span>typeText(<\/span>STRING_TO_BE_TYPED)<\/span>, closeSoftKeyboard(<\/span>)<\/span>)<\/span>;<\/span>
\n        onView(<\/span>withId(<\/span>R.id<\/span>.changeTextBt<\/span>)<\/span>)<\/span>.perform<\/span>(<\/span>click(<\/span>)<\/span>)<\/span>;<\/span>
\n
\n        \/\/ Check that the text was changed.<\/span>
\n        onView(<\/span>withId(<\/span>R.id<\/span>.textToBeChanged<\/span>)<\/span>)<\/span>.check<\/span>(<\/span>matches(<\/span>withText(<\/span>STRING_TO_BE_TYPED)<\/span>)<\/span>)<\/span>;<\/span>
\n    }<\/span>
\n}<\/span><\/div><\/div>\n

Now create your ActivityTestRule<\/span><\/code><\/p>\n

public<\/span> class<\/span> ActivityTestRule<<\/span>T extends<\/span> Activity><\/span> {<\/span>
\n
\n    public<\/span> T getActivity(<\/span>)<\/span> {<\/span>}<\/span>
\n
\n    protected<\/span> Intent getActivityIntent(<\/span>)<\/span> {<\/span>}<\/span>
\n
\n    protected<\/span> void<\/span> beforeActivityLaunched(<\/span>)<\/span> {<\/span>}<\/span>
\n
\n    protected<\/span> void<\/span> afterActivityFinished(<\/span>)<\/span> {<\/span>}<\/span>
\n}<\/span><\/div><\/div>\n

<\/p>\n

Espresso-Intents<\/h3>\n

Espresso-Intents is like Mockito<\/a> but for Intent, basically hermetic inter-app testing.
\nTo give you an example, lets say in your application when a user presses a “call” button, you want to know if the correct data will be send to the Intent.ACTION_CALL<\/span><\/code>. <\/p>\n

\"EspressoIntent\"<\/p>\n

So first create an IntentsTestRule<\/span><\/code> and then verify that the Intent was sent using Espresso-Intents<\/p>\n

@RunWith(<\/span>AndroidJUnit4.class<\/span>)<\/span>
\n@LargeTest
\npublic<\/span> class<\/span> DialerActivityTest {<\/span>
\n    ...
\n    @Rule
\n    public<\/span> IntentsTestRule<<\/span>DialerActivity><\/span> mRule =<\/span> new<\/span> IntentsTestRule<><\/span>(<\/span>DialerActivity.class<\/span>)<\/span>;<\/span>
\n
\n    @Test
\n    public<\/span> void<\/span> typeNumber_ValidInput_InitiatesCall(<\/span>)<\/span> {<\/span>
\n        onView(<\/span>withId(<\/span>R.id<\/span>.edit_text_caller_number<\/span>)<\/span>)<\/span>.perform<\/span>(<\/span>typeText(<\/span>VALID_PHONE_NUMBER)<\/span>,
\n                closeSoftKeyboard(<\/span>)<\/span>)<\/span>;<\/span>
\n        onView(<\/span>withId(<\/span>R.id<\/span>.button_call_number<\/span>)<\/span>)<\/span>.perform<\/span>(<\/span>click(<\/span>)<\/span>)<\/span>;<\/span>
\n
\n        intended(<\/span>allOf(<\/span>
\n                hasAction(<\/span>is(<\/span>equalTo(<\/span>Intent.ACTION_CALL<\/span>)<\/span>)<\/span>)<\/span>,
\n                hasData(<\/span>equalTo(<\/span>INTENT_DATA_PHONE_NUMBER)<\/span>)<\/span>,
\n                toPackage(<\/span>PACKAGE_ANDROID_DIALER)<\/span>)<\/span>)<\/span>;<\/span>
\n    }<\/span>
\n}<\/span><\/div><\/div>\n

<\/br>
\nSo now you know…
\n
\nAll code can be found in android-testing github<\/a>:<\/p>\n