2016-09-14 56 views
1

我试图调试大约3%时间内失败的Android UI测试。由于Robotium无法找到ImageButton对象,Android UI测试偶尔会失败

我们的测试类开始时是这样的:

@RunWith(AndroidJUnit4.class) 
public class ActionWidgetAdapterTest { 

    private Solo solo; 

    @Rule 
    public ActivityTestRule<SampleContainer> mActivityRule = new ActivityTestRule<>(SampleContainer.class); 

    // SampleContainer is used exclusively for the test case and extends AppCompatActivity 

    @Before 
    public void setUp() throws Exception { 
     solo = new Solo(InstrumentationRegistry.getInstrumentation(), mActivityRule.getActivity()); 
    } 

    @After 
    public void tearDown() throws Exception { 
     solo.finishOpenedActivities(); 
    } 
    // rest of class 
    // [...] 
} 

有问题的测试案例如下:

@Test 
@LargeTest 
@FlakyTest 
public void testAddActions() throws Exception { 

    final ArrayList<Action> actions = new ArrayList<>(); 

    // Action is our in-house version of the Action class from the Leanback library 
    final Action a1 = new Action(0, "text1", R.drawable.action_button_focused); 
    final Action a2 = new Action(1, "text2", R.drawable.action_button_focused); 
    final Action a3 = new Action(0, "text3", R.drawable.action_button_focused); 
    final Action a4 = new Action(1, "text4", R.drawable.action_button_focused); 

    actions.add(a1); 
    actions.add(a2); 
    actions.add(a3); 
    actions.add(a4); 

    // handler for posting to the main thread 
    Handler mainHandler = new Handler(mActivityRule.getActivity().getBaseContext() 
                   .getMainLooper()); 

    Runnable myRunnable =() -> { 

     // add actions to adapter 
     mActivityRule.getActivity().mActionWidgetAdapter.addActions(actions); 
    }; 
    mainHandler.post(myRunnable); 

    solo.sleep(1000); // pause to resolve any timing issues 
    assertTrue(mActivityRule.getActivity().mActionWidgetAdapter.getItemCount() == 4); 

    // test edge case - navigate all the way to the left 
    solo.sendKey(Solo.LEFT); 
    pressUpDownEnter(); 
    solo.sendKey(Solo.LEFT); 
    pressUpDownEnter(); 
    solo.sendKey(Solo.LEFT); 
    pressUpDownEnter(); 
    solo.sendKey(Solo.LEFT); 
    pressUpDownEnter(); 
    solo.sendKey(Solo.LEFT); 

    assertTrue(solo.getImageButton(0).isFocused()); 
    assertFalse(solo.getImageButton(2).isFocused()); 
} 

测试用例通过了绝大多数的时间。但是,执行assertTrue(solo.getImageButton(0).isFocused());时出现故障的可能性很小; Robotium抱怨说“发现3个ImageButtons”。这似乎没有任何模式。我将Robotium框架升级到最新版本,但这并不能解决问题。

任何人都知道我们做错了什么?

回答

1

我相信我找到了原因。从我所知道的情况来看,这个问题是由于tearDown()中的竞态条件造成的。根据Robotium源代码,finishOpenedActivities()通过发送Back按钮三次。但是,这似乎是在单独的线程上完成的。因此,即使在新的测试用例开始时,这些命令也可能会继续发送,从而导致应用程序被测试从视图中消失,并使Robotium无法读取UI。

考虑到应用程序已经在每次测试结束时被杀死,finishOpenedActivities()似乎有点多余。在我评论此行后,问题没有再出现。

相关问题