Fix the flaky browser test LauncherPlatformAppBrowserTest.SetIcon
AppService is used to load icons for windows. AppService uses async mojom. So it might be not very appropriate to test with update number when we have the custom icon, because if the icon is updated fast from AppService, then it might be updated 4 times, however if slow, then there are 3 updates only, becuase it has got the customer icon, and the icon update from AppService could be skipped. Modify the test case LauncherPlatformAppBrowserTest.SetIcon to check the final image. If the custom icon is set, check the window's icon is set as the custom icon. BUG=1115533 Change-Id: Ief034842fef9360a49a504effb54cf51c8d4c51a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2364156Reviewed-by:Xiyuan Xia <xiyuan@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Commit-Queue: Nancy Wang <nancylingwang@chromium.org> Cr-Commit-Position: refs/heads/master@{#800144}
Showing
Please register or sign in to comment