[Security Solution] Unskip Cypress tests for related integrations#232022
Conversation
|
Pinging @elastic/security-detections-response (Team:Detections and Resp) |
|
Pinging @elastic/security-solution (Team: SecuritySolution) |
|
Pinging @elastic/security-detection-rule-management (Team:Detection Rule Management) |
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]
cc @banderror |
Flaky Test Runner Stats🎉 All tests passed! - kibana-flaky-test-suite-runner#9161[✅] Security Solution Rule Management - Cypress: 100/100 tests passed. |
|
Starting backport for target branches: 8.19, 9.1 https://github.com/elastic/kibana/actions/runs/17041984429 |
…astic#232022) **Partially addresses: elastic#229688 **Resolves: elastic#176027 ## Summary This PR unskips the following tests: - `x-pack/solutions/security/test/security_solution_cypress/cypress/e2e/detection_response/rule_management/related_integrations/related_integrations.cy.ts` No additional fixes have been made. The idea is that flakiness in these tests has been already fixed by all the prior efforts already done within the [parent epic](elastic#229688). ## Flaky test runs - [100x ESS + 100x Serverless](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/9161) 🟢 ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [x] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [x] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. (cherry picked from commit 4379c31)
💔 Some backports could not be created
Note: Successful backport PRs will be merged automatically after passing CI. Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation |
…astic#232022) **Partially addresses: elastic#229688 **Resolves: elastic#176027 ## Summary This PR unskips the following tests: - `x-pack/solutions/security/test/security_solution_cypress/cypress/e2e/detection_response/rule_management/related_integrations/related_integrations.cy.ts` No additional fixes have been made. The idea is that flakiness in these tests has been already fixed by all the prior efforts already done within the [parent epic](elastic#229688). ## Flaky test runs - [100x ESS + 100x Serverless](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/9161) 🟢 ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [x] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [x] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. (cherry picked from commit 4379c31) # Conflicts: # x-pack/solutions/security/test/security_solution_cypress/cypress/e2e/detection_response/rule_management/related_integrations/related_integrations.cy.ts
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
…ns (#232022) (#232084) # Backport This will backport the following commits from `main` to `9.1`: - [[Security Solution] Unskip Cypress tests for related integrations (#232022)](#232022) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Georgii Gorbachev","email":"georgii.gorbachev@elastic.co"},"sourceCommit":{"committedDate":"2025-08-18T13:26:56Z","message":"[Security Solution] Unskip Cypress tests for related integrations (#232022)\n\n**Partially addresses: https://github.com/elastic/kibana/issues/229688**\n**Resolves: https://github.com/elastic/kibana/issues/176027**\n\n## Summary\n\nThis PR unskips the following tests:\n\n-\n`x-pack/solutions/security/test/security_solution_cypress/cypress/e2e/detection_response/rule_management/related_integrations/related_integrations.cy.ts`\n\nNo additional fixes have been made. The idea is that flakiness in these\ntests has been already fixed by all the prior efforts already done\nwithin the [parent\nepic](https://github.com/elastic/kibana/issues/229688).\n\n## Flaky test runs\n\n- [100x ESS + 100x\nServerless](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/9161)\n🟢\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [x] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"4379c31117d0cff37b5d278e14ed97b13ef78b7f","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["test","release_note:skip","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Related Integrations","backport:version","v9.2.0","v9.1.3","v8.19.3"],"title":"[Security Solution] Unskip Cypress tests for related integrations","number":232022,"url":"https://github.com/elastic/kibana/pull/232022","mergeCommit":{"message":"[Security Solution] Unskip Cypress tests for related integrations (#232022)\n\n**Partially addresses: https://github.com/elastic/kibana/issues/229688**\n**Resolves: https://github.com/elastic/kibana/issues/176027**\n\n## Summary\n\nThis PR unskips the following tests:\n\n-\n`x-pack/solutions/security/test/security_solution_cypress/cypress/e2e/detection_response/rule_management/related_integrations/related_integrations.cy.ts`\n\nNo additional fixes have been made. The idea is that flakiness in these\ntests has been already fixed by all the prior efforts already done\nwithin the [parent\nepic](https://github.com/elastic/kibana/issues/229688).\n\n## Flaky test runs\n\n- [100x ESS + 100x\nServerless](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/9161)\n🟢\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [x] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"4379c31117d0cff37b5d278e14ed97b13ef78b7f"}},"sourceBranch":"main","suggestedTargetBranches":["9.1","8.19"],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/232022","number":232022,"mergeCommit":{"message":"[Security Solution] Unskip Cypress tests for related integrations (#232022)\n\n**Partially addresses: https://github.com/elastic/kibana/issues/229688**\n**Resolves: https://github.com/elastic/kibana/issues/176027**\n\n## Summary\n\nThis PR unskips the following tests:\n\n-\n`x-pack/solutions/security/test/security_solution_cypress/cypress/e2e/detection_response/rule_management/related_integrations/related_integrations.cy.ts`\n\nNo additional fixes have been made. The idea is that flakiness in these\ntests has been already fixed by all the prior efforts already done\nwithin the [parent\nepic](https://github.com/elastic/kibana/issues/229688).\n\n## Flaky test runs\n\n- [100x ESS + 100x\nServerless](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/9161)\n🟢\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [x] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"4379c31117d0cff37b5d278e14ed97b13ef78b7f"}},{"branch":"9.1","label":"v9.1.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co>
…astic#232022) **Partially addresses: elastic#229688 **Resolves: elastic#176027 ## Summary This PR unskips the following tests: - `x-pack/solutions/security/test/security_solution_cypress/cypress/e2e/detection_response/rule_management/related_integrations/related_integrations.cy.ts` No additional fixes have been made. The idea is that flakiness in these tests has been already fixed by all the prior efforts already done within the [parent epic](elastic#229688). ## Flaky test runs - [100x ESS + 100x Serverless](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/9161) 🟢 ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [x] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [x] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels.
…ons (#232022) (#232092) # Backport This will backport the following commits from `main` to `8.19`: - [[Security Solution] Unskip Cypress tests for related integrations (#232022)](#232022) <!--- Backport version: 10.0.1 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Georgii Gorbachev","email":"georgii.gorbachev@elastic.co"},"sourceCommit":{"committedDate":"2025-08-18T13:26:56Z","message":"[Security Solution] Unskip Cypress tests for related integrations (#232022)\n\n**Partially addresses: https://github.com/elastic/kibana/issues/229688**\n**Resolves: https://github.com/elastic/kibana/issues/176027**\n\n## Summary\n\nThis PR unskips the following tests:\n\n-\n`x-pack/solutions/security/test/security_solution_cypress/cypress/e2e/detection_response/rule_management/related_integrations/related_integrations.cy.ts`\n\nNo additional fixes have been made. The idea is that flakiness in these\ntests has been already fixed by all the prior efforts already done\nwithin the [parent\nepic](https://github.com/elastic/kibana/issues/229688).\n\n## Flaky test runs\n\n- [100x ESS + 100x\nServerless](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/9161)\n🟢\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [x] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"4379c31117d0cff37b5d278e14ed97b13ef78b7f","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["test","release_note:skip","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Related Integrations","backport:version","v9.2.0","v9.1.3","v8.19.3"],"title":"[Security Solution] Unskip Cypress tests for related integrations","number":232022,"url":"https://github.com/elastic/kibana/pull/232022","mergeCommit":{"message":"[Security Solution] Unskip Cypress tests for related integrations (#232022)\n\n**Partially addresses: https://github.com/elastic/kibana/issues/229688**\n**Resolves: https://github.com/elastic/kibana/issues/176027**\n\n## Summary\n\nThis PR unskips the following tests:\n\n-\n`x-pack/solutions/security/test/security_solution_cypress/cypress/e2e/detection_response/rule_management/related_integrations/related_integrations.cy.ts`\n\nNo additional fixes have been made. The idea is that flakiness in these\ntests has been already fixed by all the prior efforts already done\nwithin the [parent\nepic](https://github.com/elastic/kibana/issues/229688).\n\n## Flaky test runs\n\n- [100x ESS + 100x\nServerless](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/9161)\n🟢\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [x] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"4379c31117d0cff37b5d278e14ed97b13ef78b7f"}},"sourceBranch":"main","suggestedTargetBranches":["8.19"],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/232022","number":232022,"mergeCommit":{"message":"[Security Solution] Unskip Cypress tests for related integrations (#232022)\n\n**Partially addresses: https://github.com/elastic/kibana/issues/229688**\n**Resolves: https://github.com/elastic/kibana/issues/176027**\n\n## Summary\n\nThis PR unskips the following tests:\n\n-\n`x-pack/solutions/security/test/security_solution_cypress/cypress/e2e/detection_response/rule_management/related_integrations/related_integrations.cy.ts`\n\nNo additional fixes have been made. The idea is that flakiness in these\ntests has been already fixed by all the prior efforts already done\nwithin the [parent\nepic](https://github.com/elastic/kibana/issues/229688).\n\n## Flaky test runs\n\n- [100x ESS + 100x\nServerless](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/9161)\n🟢\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [x] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"4379c31117d0cff37b5d278e14ed97b13ef78b7f"}},{"branch":"9.1","label":"v9.1.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/232084","number":232084,"state":"OPEN"},{"branch":"8.19","label":"v8.19.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->
…astic#232022) **Partially addresses: elastic#229688 **Resolves: elastic#176027 ## Summary This PR unskips the following tests: - `x-pack/solutions/security/test/security_solution_cypress/cypress/e2e/detection_response/rule_management/related_integrations/related_integrations.cy.ts` No additional fixes have been made. The idea is that flakiness in these tests has been already fixed by all the prior efforts already done within the [parent epic](elastic#229688). ## Flaky test runs - [100x ESS + 100x Serverless](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/9161) 🟢 ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [x] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [x] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels.
Partially addresses: #229688
Resolves: #176027
Summary
This PR unskips the following tests:
x-pack/solutions/security/test/security_solution_cypress/cypress/e2e/detection_response/rule_management/related_integrations/related_integrations.cy.tsNo additional fixes have been made. The idea is that flakiness in these tests has been already fixed by all the prior efforts already done within the parent epic.
Flaky test runs
Checklist
release_note:*label is applied per the guidelinesbackport:*labels.