Enable PrecisionTouchpadBrowserTest.* browser tests
These tests started being flaky as soon as they were initially landed. It seems to be a timing issue, so I added in two pieces to ensure timing is correct: 1. MainThreadFrameObserver - I was seeing that occasionally, the frame wouldn't have been produced by the time the test was sending the first scroll or zoom, resulting in the scroll or zoom bailing early and not happening. The MainThreadFrameObserver will make sure that execution waits until a frame is produced and everything is in sync before continuing. 2. InputMsgWatcher - This ensures that the test receives an ACK back from the expected event type each time a scroll or zoom is performed. The ACK can technically be a few different things based on different conditions but it doesn't really matter what it is, just that an ACK is received. This allows us to be certain that we are waiting long enough before checking the zoom or scroll amounts. Bug: 1010911 Change-Id: Ieb1c3993cdc17afacd8aecb5e823881c539a1e12 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1837892Reviewed-by:David Bokan <bokan@chromium.org> Reviewed-by:
Ken Buchanan <kenrb@chromium.org> Commit-Queue: Ken Buchanan <kenrb@chromium.org> Cr-Commit-Position: refs/heads/master@{#707141}
Showing
Please register or sign in to comment