Skip to content
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

Failing test: X-Pack Accessibility Tests - Group 3.x-pack/test/accessibility/apps/group3/security_solution·ts - X-Pack Accessibility Tests - Group 3 Security Solution Accessibility Detections Create Rule Flow Custom Query Rule Define Step preview section meets a11y requirements #179353

Open
kibanamachine opened this issue Mar 25, 2024 · 16 comments
Labels
blocker failed-test A test failure on a tracked branch, potentially flaky-test skipped-test Team:Detection Engine Security Solution Detection Engine Area Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. triage_needed v9.0.0

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Mar 25, 2024

A test failed on a tracked branch

Error: retry.try reached timeout 120000 ms
ElementClickInterceptedError: element click intercepted: Element <button disabled="" type="button" class="euiButton euiSuperUpdateButton css-fq595v-euiButtonDisplay-m-isDisabled-fill-disabled" data-test-subj="previewSubmitButton" style="min-inline-size: 118px;">...</button> is not clickable at point (1485, 295). Other element would receive the click: <span class="euiToolTipAnchor css-jcaat8-euiToolTipAnchor-inlineBlock">...</span>
  (Session info: chrome=123.0.6312.58)
    at Object.throwDecodedError (node_modules/selenium-webdriver/lib/error.js:521:15)
    at parseHttpResponse (node_modules/selenium-webdriver/lib/http.js:510:13)
    at Executor.execute (node_modules/selenium-webdriver/lib/http.js:443:28)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at Task.exec (prevent_parallel_calls.ts:28:20)
    at onFailure (retry_for_success.ts:17:9)
    at retryForSuccess (retry_for_success.ts:84:7)
    at RetryService.try (retry.ts:51:12)
    at Proxy.clickByCssSelector (find.ts:419:5)
    at TestSubjects.click (test_subjects.ts:164:5)
    at CommonPageObject.clickAndValidate (common_page.ts:553:5)
    at DetectionsPageObject.preview (index.ts:123:5)
    at Context.<anonymous> (security_solution.ts:57:15)
    at Object.apply (wrap_function.js:73:16)

First failure: CI Build - main

@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Mar 25, 2024
@botelastic botelastic bot added the needs-team Issues missing a team label label Mar 25, 2024
@mistic mistic added the Team:Detection Engine Security Solution Detection Engine Area label Mar 25, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-detection-engine (Team:Detection Engine)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Mar 25, 2024
@banderror banderror added triage_needed Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. labels Mar 26, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-solution (Team: SecuritySolution)

@elasticmachine
Copy link
Contributor

Pinging @elastic/security-detections-response (Team:Detections and Resp)

@banderror
Copy link
Contributor

banderror commented Mar 26, 2024

@yctercero Do you know who originally created this test file and who currently maintains it? All tests inside of it open the Rule Creation page and run some accessibility checks. The file is not mapped in CODEOWNERS to any team.

@yctercero
Copy link
Contributor

@banderror I don't know. I think these were added by the accessibility team for us to maintain, but I'm not certain.

@peluja1012 do you remember the origin of these tests?

@yctercero yctercero removed their assignment Apr 11, 2024
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

mistic added a commit that referenced this issue May 31, 2024
mistic added a commit that referenced this issue May 31, 2024
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@yctercero
Copy link
Contributor

/skip

@kibanamachine
Copy link
Contributor Author

Skipped

main: 7d9e7de

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - 8.x

viduni94 pushed a commit to viduni94/kibana that referenced this issue Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocker failed-test A test failure on a tracked branch, potentially flaky-test skipped-test Team:Detection Engine Security Solution Detection Engine Area Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. triage_needed v9.0.0
Projects
None yet
Development

No branches or pull requests

5 participants