-
Notifications
You must be signed in to change notification settings - Fork 780
Latest versions jun2025 #1944
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
Latest versions jun2025 #1944
Conversation
Also reveted back from expressive matrix options as I need to learn how to use key-value pairs within gh actions.
Also reduce test matrix for now and set setup-chrome action to v1 (as compared to @latest)
Looks like the system has Chrome 1.37 already installed. This will setup chrome 137 somewhere but more importantly add the driver. Realizing I may need to rework how we setup the machine ..
…oss many versions
@@ -43,6 +43,7 @@ Handle Alert returns message | |||
|
|||
Handle Alert with custom timeout | |||
Click Button Slow alert | |||
Sleep 0.1s |
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.
Doesn’t this indicate problem in the library, instead of doing sleep, should library be fixed?
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.
Updated this. I removed the sleep but also extended the given timeout. For this test the alert was delayed 500ms and it appears that timing out at 1sec (or 500ms later) is too short to reasonable expect for alert triggered and then detected. This extension gives it a reasonable amount of time after triggering.
Previously the timeout was 1 sec and the alert was delayed 500ms. With a normal execution it seems that that 500ms diference is just not long enough to reasonably expect the alert to appear. In reviewing this test it was shown any delay was useful and the needed time for an alert to triggered and then recognized would need more than 500ms.
Various cleanup work on the internal test suite and bringing up the versions of parts of the tech stack.