limc5462 opened a new pull request, #4337:
URL: https://github.com/apache/streampark/pull/4337

   …source pages
   
   <!--
   Thank you for contributing to StreamPark! Please make sure that your code 
changes
   are covered with tests. And in case of new features or big changes
   remember to adjust the documentation.
   
   ## Contribution Checklist
   
     - If this is your first time, please read our contributor guidelines: 
[Submit Code](https://streampark.apache.org/community/submit_guide/submit_code).
   
     - Make sure that the pull request corresponds to a [GITHUB 
issue](https://github.com/apache/streampark/issues).
   
     - Name the pull request in the form "[Feature] Title of the pull request", 
where *Feature* can be replaced by `Hotfix`, `Bug`, etc.
   
     - Fill out the template below to describe the changes contributed by the 
pull request. That will give reviewers the context they need to do the review.
   
     - If the PR is unfinished, add `[WIP]` in your PR title, e.g., 
`[WIP][Feature] Title of the pull request`.
   
   -->
   
   ## What changes were proposed in this pull request
   This PR addresses a critical stability issue (flaky tests) in the E2E 
testing pipeline for StreamPark.
   **Fix Flaky UI Tests (`ElementClickInterceptedException`)**: 
   A race condition frequently occurred in `UserManagementTest` and 
`UploadManagementTest` where the Selenium webdriver clicked on child menu items 
while the parent menu's CSS expanding animation was still in progress. This 
caused clicks to be intercepted by the animated mask or parent container. 
   
   
   <!--(For example: This pull request proposed to add checkstyle plugin).-->
   
   ## Brief change log
   
   `SystemPage.java` & `ResourcePage.java`: Added `Thread.sleep()` before all 
`menu.click()` actions with `@SneakyThrows` to fix 
`ElementClickInterceptedException` caused by CSS animations.
   <!--*(for example:)*
   - *Add maven-checkstyle-plugin to root pom.xml*
   -->
   
   ## Verifying this change
   This is the last E2E issue I've found. From now on, the pipeline is highly 
likely to run successfully every time.
   
   <!--*(example:)*
   - *Added integration tests for end-to-end.*
   - *Added *Test to verify the change.*
   - *Manually verified the change by testing locally.* -->
   
   ## Does this pull request potentially affect one of the following parts
    no
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to