执行过程中INSTRUMENTATION_RESULT: shortMsg=Process crashed.导致执行中断,
以下是其中的一种情况,LOG如下
08-02 18:30:48.008 E/HwLauncher( 3466): Launcher dialog dismiss failed : java.lang.IllegalArgumentException: no dialog with id 1 was ever shown via Activity#showDialog
08-02 18:30:48.028 E/WindowManager(17869): android.view.WindowLeaked: Activity************************ has leaked window com.android.internal.policy.impl.PhoneWindow$DecorView{44be2610 V.E..... R......D 0,0-1080,152} that was originally added here
08-02 18:30:48.028 E/WindowManager(17869): at android.view.ViewRootImpl.<init>(ViewRootImpl.java:377)
08-02 18:30:48.028 E/WindowManager(17869): at android.view.WindowManagerGlobal.addView(WindowManagerGlobal.java:258)
08-02 18:30:48.028 E/WindowManager(17869): at android.view.WindowManagerImpl.addView(WindowManagerImpl.java:69)
08-02 18:30:48.028 E/WindowManager(17869): at android.app.Dialog.show(Dialog.java:323)
这里在teardown中调用的关闭方法是solo.finishOpenedActivities();
以上log可以看出,再次打开应用时出现WindowLeaked窗口泄漏,
每一个android的activity都有一个windowManager的窗口管理器,对应的每一个依附在activity上面的对话框,也有一个windowManager,如果,我在finish了activity的时候,没有对这些窗口进行处理,那么就会出现window leadked 这个异常。
如果在APP开发中可以加入 dialog.dimiss();//结束对话
在Robotium执行环境下,尽可能使用pressback结束应用,避免关闭不完全。
http://stackoverflow.com/questions/7851351/robotium-in-the-suite-of-tests-each-next-test-is-affected-by-the-previous-test
teardown方法中增加以下内容
boolean more = true;
while(more) {
try {
getInstrumentation().sendKeyDownUpSync(KeyEvent.KEYCODE_BACK);
} catch (SecurityException e) { // Done, at Home.
more = false;
}
}