Commit 27ccfb23 authored by Rohit Rao's avatar Rohit Rao Committed by Commit Bot

[ios] Speculative fix for testAppLaunchManagerForceRelaunchByKilling.

On the bots, these tests appear to fail because they can't find the
Restore infobar after a crash. This CL changes the test to wait for the
infobar to become visible, rather than doing a single check, in case the
test runs so quickly that the infobar hasn't yet had a chance to appear.

BUG=1149370

Change-Id: I8b65c1796408e8151582398d4b2c3c12534c209b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2540426Reviewed-by: default avatarJustin Cohen <justincohen@chromium.org>
Commit-Queue: Rohit Rao <rohitrao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#827817}
parent 43f3aa92
...@@ -264,8 +264,8 @@ ...@@ -264,8 +264,8 @@
[[AppLaunchManager sharedManager] ensureAppLaunchedWithFeaturesEnabled:{} [[AppLaunchManager sharedManager] ensureAppLaunchedWithFeaturesEnabled:{}
disabled:{} disabled:{}
relaunchPolicy:ForceRelaunchByKilling]; relaunchPolicy:ForceRelaunchByKilling];
[[EarlGrey selectElementWithMatcher:grey_text(@"Restore")] [ChromeEarlGrey
assertWithMatcher:grey_sufficientlyVisible()]; waitForSufficientlyVisibleElementWithMatcher:grey_text(@"Restore")];
[ChromeEarlGrey waitForMainTabCount:1]; [ChromeEarlGrey waitForMainTabCount:1];
} }
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment