I am just starting out wih junit
and the first issue I'm running into is, how should I test fragments?
The activity being tested has 1 fragment which is the main layout.
@Override
protected void setUp() throws Exception {
super.setUp();
Intent intent = new Intent(getInstrumentation().getTargetContext(),
ActivityWelcome.class);
startActivity(intent, null, null);
FragmentManager fragmentManager = getActivity().getSupportFragmentManager();
mFragmentWelcome = (FragmentWelcome) fragmentManager.findFragmentByTag(FragmentWelcome.TAG);
if (mFragmentWelcome == null) {
mFragmentWelcome= FragmentWelcome.newInstance();
fragmentManager
.beginTransaction()
.replace(android.R.id.content, mFragmentWelcome, FragmentWelcome.TAG)
.commit();
}
}
I then go on to test the layout:
@SmallTest
public void testLayout() {
ImageButton buttonImage = (ImageButton) getActivity().findViewById(my.package.R.id.button_invites);
assertNotNull(buttonImage);
assertEquals("ImageButton Invite has an invalid drawable"
, getActivity().getResources().getDrawable(my.package.R.drawable.light_social_invite)
, buttonImage);
}
Error:
java.lang.NullPointerException
at my.package.test.ActivityWelcomeUnitTest.testLayout(ActivityWelcomeUnitTest.java:55)
at java.lang.reflect.Method.invokeNative(Native Method)
at android.test.InstrumentationTestCase.runMethod(InstrumentationTestCase.java:214)
at android.test.InstrumentationTestCase.runTest(InstrumentationTestCase.java:199)
at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:169)
at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:154)
at android.test.InstrumentationTestRunner.onStart(InstrumentationTestRunner.java:545)
at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1551)
it fails on:
ImageButton buttonImage = (ImageButton) mFragmentWelcome.getView().findViewById(my.package.R.id.button_invites);
I'm not sure why the fragment is null, I am obviously performing this operation incorrectly, could someone please enlighten me?
Actually you have to wait for the UI thread composes the main view with the fragments.
I had the same errors and so I looked at the sources of Robotium to see how they handle that. The response is they use some methods that wait the required time.
For fragment you can use something like that before performing your assertions :
I use a timeout of 5000ms, it seems to work well.
So in your code you should replace
by
EDIT : This response assumes your junit extends
ActivityInstrumentationTestCase2<T>
For an
ActivityUnitTestCase
test, I had to add the following line(s) to thewaitForFragment
method:U can use com.robotium.solo.Solo from
'com.jayway.android.robotium:robotium-solo:5.2.1'