Explicitly click to close actions menu in integration test for violations#2812
Conversation
|
Images are ready for the commit at dc1727a. To use with deploy scripts, first |
|
@pedrottimark: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
/test gke-ui-e2e-tests |
dvail
left a comment
There was a problem hiding this comment.
hard to say why it failed this time this way
True, but even if this was a fluke I agree that closing dropdowns like this should help the tests be more reliable in general.
Description
Test failure
1560369927628525568 from master build for #2715 on 2022-08-18
Indeed, the kabob button of the second row is covered by the action menu of the first row.

Although hard to say why it failed this time this way, it seems like a good habit to use most direct interaction to put UI back into a neutral state for each of the 2 sub-tests.
Changed files
Edit cypress/constants/ViolationsPage.js
Initial attempt to click button again to close the menu failed because the selector also matched the
buttonelements for action menu items.Edit cypress/integration/violations/violations.test.js
Checklist
Testing Performed