Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[8.9] [Security Solution] Flaky Cypress test: Detection rules, Prebui…
…lt Rules Installation and Update workflow - Installation of prebuilt rules package via Fleet should install package from Fleet in the background (#164566) **NOTE: This is a manual backport of #163468 to 8.9.** **Original PR description:** Fixes: #163447 Fixes: #163586 ## Summary - Fixes flaky test: `x-pack/plugins/security_solution/cypress/e2e/detection_response/prebuilt_rules/prebuilt_rules_install_update_workflows.cy.ts` - Test title: `Detection rules, Prebuilt Rules Installation and Update workflow - Installation of prebuilt rules package via Fleet should install package from Fleet in the background` ## Details - Initially ran the flaky test runner with multiple iterations and all gave succesful results, i.e. no flakiness or failed tests. - But: after checking the logs for the failed tests in the original failed build, discovered that the reason the test failed is because: - when checking Fleet's response for the installation of the `security_detection_engine`, the API response was not as expected from the API spec: ``` **Expected:** [{ name: 'security_detection_engine', installSource: 'registry' }] **Actual:** [{ name: 'security_detection_engine', installSource: undefined }] ``` Since we cannot rely 100% that the Fleet API will return the correct value for the installSource, this PR deletes this part of the test to prevent any type of flakiness caused by external factors such as this.
- Loading branch information