Skip to content
This repository was archived by the owner on Feb 22, 2023. It is now read-only.

[quick_actions] Fix Android integration test flake #6688

Merged
merged 2 commits into from
Nov 18, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,6 @@
import org.junit.After;
import org.junit.Assert;
import org.junit.Before;
import org.junit.Ignore;
import org.junit.Test;
import org.junit.runner.RunWith;

Expand Down Expand Up @@ -86,9 +85,6 @@ public void appShortcutsAreCreated() {
}
}

// TODO(bparrishMines): The test is ignored because it fails when ran on Firebase Test Lab. See
// https://github.com/flutter/flutter/issues/114246.
@Ignore
@Test
public void appShortcutLaunchActivityAfterStarting() {
// Arrange
Expand Down Expand Up @@ -119,7 +115,7 @@ public void appShortcutLaunchActivityAfterStarting() {
"AppShortcut:" + firstShortcut.getId() + " does not launch the correct activity",
// We can only find the shortcut type in content description while inspecting it in Ui
// Automator Viewer.
device.hasObject(By.desc(firstShortcut.getId() + appReadySentinel)));
device.hasObject(By.descContains(firstShortcut.getId() + appReadySentinel)));
// This is Android SingleTop behavior in which Android does not destroy the initial activity and
// launch a new activity.
Assert.assertEquals(initialActivity.get(), currentActivity.get());
Expand Down