Recent timing related issues with screener (styling and rendering off by 1 frame failures)

[makopch-ms]

Within the last 3-4 weeks, we have encountered a number of timing related issues that were not present before. We have a PR pipeline that run against our master branch with new commits to validate the health of our systems and one of the two issues below consistently is failing.

First bucket of failures:
Some are in relation to Screener Step execution where we the screenshot is taken before the step is applied.

For example, in the follow sequence of steps:

1. Take default screenshot
2. add Step to hover over button
3. Take hover screenshot

The image taken in 3 is the same as that of 1 which means the screenshot was taken before the hover happens.

Second bucket of failures:
The other timing issue is where we have some components that render in multiple frame and the screenshot is taken before the last frame is allowed to be painted which make often the positioning of the UI appear off by a few pixels causing a failure.

These are happening across many components and no recent changes seem to have impacted styling/positioning.

Is there anything we can do to achieve greater consistency?

[loyalchow]

@makopch-ms just sent an email to you following up on this with some questions

[viditganpi]

Facing similar issues, hover screenshot been taken before actual hover

[luisVelasquezSauce]

Hi @viditganpi can you please open a support request describing your issue and useful links to your test results? https://support.saucelabs.com/hc/en-us/requests/new

[viditganpi]

@luisVelasquezSauce have already opened a ticket, no proper resolution yet.