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.

Sign up for GitHub

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

Jump to bottom

[Security Solution] Split Cypress execution on CI between Detections and Response and Threat Hunting #153661

Closed
13 tasks done
Tracked by #153633
, #153664
...
MadameSheema opened this issue Mar 24, 2023 · 6 comments
Closed
13 tasks done
Tracked by #153633
, #153664
...

[Security Solution] Split Cypress execution on CI between Detections and Response and Threat Hunting #153661

MadameSheema opened this issue Mar 24, 2023 · 6 comments
Assignees
@MadameSheema
Labels
8.12 candidate Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Threat Hunting Security Solution Threat Hunting Team technical debt Improvement of the software architecture and operational architecture test_ui_functional test

Comments

@MadameSheema
Copy link
Member

MadameSheema commented Mar 24, 2023 •
edited
Loading

After the agreement arrived on the https://github.com/elastic/security-team/issues/6181 discussion, these are the next steps we need to follow:
@MadameSheema MadameSheema added Team:Detections and Resp Security Detection Response Team Team:Threat Hunting Security Solution Threat Hunting Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. labels Mar 24, 2023
@elasticmachine
Copy link
Contributor

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

@MadameSheema MadameSheema mentioned this issue Mar 24, 2023
Closed
12 tasks
@banderror banderror mentioned this issue Mar 24, 2023
Open
@banderror banderror added test test_ui_functional technical debt Improvement of the software architecture and operational architecture 8.8 candidate labels Mar 24, 2023
@stephmilovic stephmilovic mentioned this issue May 4, 2023
Closed
@MadameSheema MadameSheema mentioned this issue May 23, 2023
Merged
@oatkiller oatkiller mentioned this issue May 31, 2023
Merged
8 tasks
oatkiller pushed a commit that referenced this issue Jun 14, 2023
@kibanamachine
[Security Solution] Create new explore team cypress config (#158747)
048bbb5 
## Summary

[This PR copies off of this one which adds a config for Investigations,
but instead adds one for
Explore.](#158236)

In this PR following this issue:
#153661 we are creating a
Cypress execution just for the `Explore` team. That would help the teams
to improve their ownership of the tests.

- This PR moves one Explore test to the new directory. We plan to move
them all in a follow up PR.
- We are updating the codeowners file to reflect this new change.
- We are creating a new script that runs just the explore team.
- We are doing all the necessary changes to have all the tests inside
the new explore folder executed on the CI
- We are adding this new execution to the unsupported ftrs execution


### For maintainers

- [ ] This was checked for breaking API changes and was [labeled
appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)

---------

Co-authored-by: kibanamachine <[email protected]>
@banderror
Copy link
Contributor

Example of extracting Cypress tests into a separate FTR config: #158747
cc @yctercero

@yctercero
Copy link
Contributor

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!

@MadameSheema
Copy link
Member Author

@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!

@banderror banderror assigned maximpn and unassigned banderror and MadameSheema Aug 31, 2023
@banderror banderror assigned banderror and unassigned yctercero Sep 16, 2023
@banderror banderror assigned maximpn and unassigned banderror Oct 16, 2023
@banderror
Copy link
Contributor

@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:

  • Make sure the new number for your execution is set as well in .buildkite/pipelines/on_merge.yml
  • And in .buildkite/pipelines/es_serverless/verify_es_serverless_image.yml in case of being a serverless one

@banderror banderror assigned banderror and unassigned maximpn Nov 15, 2023
@banderror banderror mentioned this issue Nov 27, 2023
Merged
@banderror banderror assigned MadameSheema and unassigned banderror Nov 27, 2023
@MadameSheema MadameSheema mentioned this issue Dec 3, 2023
Merged
@MadameSheema
Copy link
Member Author

Closing this ticket since currently all the area teams inside D&R and TH have their own specific execution on Cypress :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@MadameSheema MadameSheema

Labels
8.12 candidate Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Threat Hunting Security Solution Threat Hunting Team technical debt Improvement of the software architecture and operational architecture test_ui_functional test
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@maximpn @banderror @yctercero @elasticmachine @MadameSheema