Handle inconsistent ordering of intent filter arguments

Ensure both filter actions are found but assume any order.

Test: treehugger
Bug: 262574315
Change-Id: I248f5dd70683b36109b35f511067c42a44b24120
This commit is contained in:
Mady Mellor
2022-12-14 09:31:17 -08:00
parent e0401be59c
commit 98d02e7108

View File

@@ -1332,10 +1332,10 @@ public class BubblesTest extends SysuiTestCase {
mBubbleController.updateBubble(mBubbleEntry);
verify(mContext).registerReceiver(mBroadcastReceiverArgumentCaptor.capture(),
mFilterArgumentCaptor.capture(), eq(Context.RECEIVER_EXPORTED));
assertThat(mFilterArgumentCaptor.getValue().getAction(0)).isEqualTo(
Intent.ACTION_CLOSE_SYSTEM_DIALOGS);
assertThat(mFilterArgumentCaptor.getValue().getAction(1)).isEqualTo(
Intent.ACTION_SCREEN_OFF);
assertThat(mFilterArgumentCaptor.getValue()
.hasAction(Intent.ACTION_CLOSE_SYSTEM_DIALOGS)).isTrue();
assertThat(mFilterArgumentCaptor.getValue()
.hasAction(Intent.ACTION_SCREEN_OFF)).isTrue();
mBubbleData.dismissBubbleWithKey(mBubbleEntry.getKey(), REASON_APP_CANCEL);
// TODO: not certain why this isn't called normally when tests are run, perhaps because