-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wait after clicking button to open window #1033
Conversation
Signed-off-by: Paul Gooderham <[email protected]>
Signed-off-by: Paul Gooderham <[email protected]>
Signed-off-by: Paul Gooderham <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look good. I think it would be beneficial to add some comments next to the sleep lines to explain why we need to sleep at those points.
Signed-off-by: Paul Gooderham <[email protected]>
Signed-off-by: Paul Gooderham <[email protected]>
Check out the comments. |
@turkeylurkey all 3 builds are failing - is it all known failures? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Another step towards making the UI tests more reliable. Looks good. Thanks!
Linux: error starting server. |
First we try to find the window and then if it is closed we click on the button to open it. But if the window does not open right away on a slow machine then the next time we repeat this action we will click a second time and end up closing the window we want open. So add a short delay after we click. Also added is a slightly longer delay before we try to look for the window in case a previous operation is still running.
I believe one of the exceptions listed in the issue is caused by the problem of the first exception:
Exceeded timeout ... Failed to find 'Welcome Frame'
Fixes #971