Closed MadameSheema closed 9 months ago
Pinging @elastic/security-solution (Team: SecuritySolution)
Example of extracting Cypress tests into a separate FTR config: https://github.com/elastic/kibana/pull/158747 cc @yctercero
Example of extracting Cypress tests into a separate FTR config: #158747 cc @yctercero
I had started on this last week before the influx of SDH issues. Hopefully we can get to this this week!
@banderror @yctercero , @oatkiller or me cand help you to make it happen, so don't hesitate to ping us :)
@oatkiller may you please update this ticket with the work you have done so far? Thanks!
@MadameSheema mentioned this elsewhere:
As we are adding more and more automated tests, we sometimes need to increase the parallelism number of our executions in .buildkite/pipelines/pull_request/base.yml
in order to solve timeouts issues in our pipelines, when doing so, please don't forget to:
.buildkite/pipelines/on_merge.yml
.buildkite/pipelines/es_serverless/verify_es_serverless_image.yml
in case of being a serverless oneClosing this ticket since currently all the area teams inside D&R and TH have their own specific execution on Cypress :)
After the agreement arrived on the https://github.com/elastic/security-team/issues/6181 discussion, these are the next steps we need to follow:
[x] Identify tests ownership
[x] Split test execution: @MadameSheema
[x] Create execution for Explore
[x] Create execution for Investigations
[x] Create execution for Detection Engine
[x] Create execution for Rule Management
[x] Update CODEOWNERS file: @elastic/security-detections-response , @elastic/security-threat-hunting, @oatkiller