[Security Solution] Skip all Detection & Response Cypress tests in Serverless#165966
Conversation
|
Pinging @elastic/security-detections-response (Team:Detections and Resp) |
|
Pinging @elastic/security-solution (Team: SecuritySolution) |
b385328 to
0c7d76b
Compare
90c3bfc to
ef8562a
Compare
ef8562a to
c181eef
Compare
.github/CODEOWNERS
Outdated
There was a problem hiding this comment.
FYI @MadameSheema @patrykkopycinski @oatkiller @maximpn
See the PR description for motivation.
There was a problem hiding this comment.
I also changed the pattern because it doesn't seem we need to support any nested subfolder structures which could be supported by **
|
@elasticmachine merge upstream |
There was a problem hiding this comment.
Should we add @skipInEss? If we need to skip for ESS right now we have to skip for all right?
There was a problem hiding this comment.
@yctercero This is a good point. I think we will need this tag eventually. And yes, if we need to skip for ESS right now we have to skip for all.
I'm not sure about adding it now because I think that "now we have to skip for all" is exactly what we should be doing now. Until we basically eliminate flakiness in our tests, we should treat a flaky test in ESS as being in general not yet fixed. Then, when we can say something like "ok, the rule creation Cypress tests have been all fixed and not flaky anymore in ESS and Serverless", then we could start skipping them in either environment if flakiness ever occurs again.
MadameSheema
left a comment
There was a problem hiding this comment.
security-engineering-productivity changes LGTM!!
Lots of thanks for doing this effort 🙏
yctercero
left a comment
There was a problem hiding this comment.
LGTM - thanks for the changes! Ready to help with the next step of re-enabling these for DE.
|
Most of the tests passed in https://buildkite.com/elastic/kibana-pull-request/builds/157714. The failed ones look like flaky tests. Also, the I also tested locally that if I enable at least one test using Cypress tags, the job will run it. I will remove the "all cypress tests" label and restart the build - hope it takes less time after that. |
e1f4fa2 to
22c2ab1
Compare
spong
left a comment
There was a problem hiding this comment.
Thank you for the detailed description, updated docs, and providing context/next steps -- appreciate it @banderror! LGTM 👍
maximpn
left a comment
There was a problem hiding this comment.
Cool! This PR also fixes Threat Intelligence Cypress Tests cc @PhilippeOberti
22c2ab1 to
9be0ae5
Compare
9be0ae5 to
23ed5fc
Compare
💔 Build FailedFailed CI Steps
Test Failures
Metrics [docs]Unknown metric groupsESLint disabled line counts
Total ESLint disabled count
History
To update your PR or re-run it, just comment with: cc @banderror |
|
Hey folks, this PR introduced a SKIP for all tests that do not contain tags yet. Please take a look eg. at this https://buildkite.com/elastic/kibana-pull-request/builds/157814#018a769b-185b-4d22-bb6d-e2bf155745c6 We have some false passes around :P |
Resolves: #164441
Summary
Skips all Cypress tests owned by @elastic/security-detection-rule-management and @elastic/security-detection-engine teams in Serverless using the new
@skipInServerlesstag.@skipInServerlesstagx-pack/test/security_solution_cypress/cypress/README.mdto explain when to use what tags// TODO:comments to tests with links to follow-up ticketsx-pack/plugins/security_solution/scripts/run_cypress/parallel.tsscript (see below)Follow-up work:
Context
Fixing
parallel.tsThere were two problems with the
x-pack/plugins/security_solution/scripts/run_cypress/parallel.tsscript we use for running Cypress tests:./cypress/e2e/!(investigations|explore)/**/*.cy.ts) end up being skipped via Cypress tags (such as@skipInServerless)Both the issues are fixed in this PR.
Code owners are added for this script in the CODEOWNERS file to prevent breaking this script in future PRs.