Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 6a2b4896 authored by Sungsoo Lim's avatar Sungsoo Lim
Browse files

Fix flaky test in MapClientStateMachineTest 

sendMessage() then check hasMessages() doesn't have much meaning,
but could fail if the message was already handled before checking
hasMessages().

Bug: 291160655
Test: atest BluetoothInstrumentationTests:MapClientStateMachineTest
Change-Id: Ia1dc3e2ed6408a7a75261b56d98aa1f797c4b4e5
parent 35390b96

android/app/tests/unit/src/com/android/bluetooth/mapclient/MapClientStateMachineTest.java

+0 −6
Original line number Diff line number Diff line
@@ -561,12 +561,6 @@ public class MapClientStateMachineTest { 
    @Test

    public void testGetOwnNumberTimedOut() {

        testGetOwnNumber_setup();

        Message requestIncompleteMsg = Message.obtain(mHandler,

                MceStateMachine.MSG_MAS_REQUEST_COMPLETED,

                mMockRequestOwnNumberIncompleteSearch);

        mMceStateMachine.sendMessage(requestIncompleteMsg);

        assertThat(mMceStateMachine.getHandler().hasMessages(

                MceStateMachine.MSG_MAS_REQUEST_COMPLETED)).isTrue();



        Message timeoutMsg = Message.obtain(mHandler,

                MceStateMachine.MSG_SEARCH_OWN_NUMBER_TIMEOUT,