GoogleCodeExporter
commented
9 years ago Please see
https://code.google.com/p/android-test-kit/wiki/AndroidJUnitRunnerUserGuide#Inst
rumentation_Thread_Handlers
Basically the new AndroidJUnitRunner prevents any Handler from being created on
the Instrumentation worker thread. ActivityUnitTestCase.startActivity() needs
to be called on the main thread. There are several ways to do this:
1. Use Instrumentation's runOnMainSync()
getInstrumentation().runOnMainSync(new Runnable() {
@Override
public void run() {
activity = startActivity(new Intent(Intent.ACTION_MAIN), null, null);
}
});
2. Create your own base class that extends ActivityUnitTestCase<T extends
Activity> and override startActivity
@Override
protected T startActivity(final Intent intent, final Bundle savedInstanceState,
final Object lastNonConfigurationInstance) {
return startActivityOnMainThread(intent, savedInstanceState, lastNonConfigurationInstance);
}
private T startActivityOnMainThread(final Intent intent, final Bundle
savedInstanceState,
final Object lastNonConfigurationInstance) {
final AtomicReference<T> activityRef = new AtomicReference<>();
final Runnable activityRunnable = new Runnable() {
@Override
public void run() {
activityRef.set(YourBaseActivityUnitTestCase.super.startActivity(
intent, savedInstanceState, lastNonConfigurationInstance));
}
};
if (Looper.myLooper() != Looper.getMainLooper()) {
getInstrumentation().runOnMainSync(activityRunnable);
} else {
activityRunnable.run();
}
return activityRef.get();
}
You would extend your base test class instead of ActivityUnitTestCase directly
3. If you call startActivity() in a test method and your entire test can run on
the main thread, you can simply annotate your test method with @UiThreadTest.
Hope this helps.Original comment by mhernan...@gmail.com on 28 Jan 2015 at 7:24
Original issue reported on code.google.com by
littledo...@gmail.comon 16 Jan 2015 at 7:31