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.

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

[Security Solution] Identify Explore Cypress tests ownership #153659

Closed
Tracked by #153661
MadameSheema opened this issue Mar 24, 2023 · 2 comments
Closed
Tracked by #153661

[Security Solution] Identify Explore Cypress tests ownership #153659

MadameSheema opened this issue Mar 24, 2023 · 2 comments

Comments

@MadameSheema
Copy link
Member

As part of the https://github.com/elastic/security-team/issues/6250 effort, we need to identify which test scenarios are owned by Threat Hunting team.

In order to make this effort more granular and to have an up-to-date codeowners file, the task is going to be divided between the different area teams.

As an output, we are expecting to have the lists of Cypress tests owned by the Explore team.

Please add a comment to this ticket with the tests your teams owns using the following formats:

If you own the whole file:

/x-pack/plugins/security_solution/cypress/e2e/detection_rules/bulk_edit_rules.cy.ts

If you own just some test(s) of the file:

/x-pack/plugins/security_solution/cypress/e2e/detection_rules/bulk_edit_rules.cy.ts
  Only prebuilt rules selected
  Prebuilt and custom rules selected: user proceeds with custom rules editing
@stephmilovic
Copy link
Contributor

follow up here: #153661

@oatkiller
Copy link
Contributor

This PR adds a new config #158747

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants