Refactor WebUI to reduce flakiness with retry logic and better waits #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change improves the stability of the Selenium automation framework by addressing common causes of flaky tests.
Key changes:
waitForPageLoaded: Wrapped the initial JS check in a try-catch block to prevent unchecked exceptions from crashing the test flow when the driver is in an unstable state.clickElementandsetTextmethods. This automatically recovers fromStaleElementReferenceException(common in dynamic apps) andElementClickInterceptedException(common with overlays/spinners).sleep(3)calls withwaitForPageLoaded()or reduced sleep times where explicit waits weren't fully applicable but a shorter delay suffices.These changes aim to make the
WebUIutility class more resilient to timing issues and dynamic DOM updates.PR created automatically by Jules for task 14217734582414245073 started by @anhtester