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

[Rule Management] Audit clean-up of data in Cypress #175098

Open
Tracked by #153633 ...
MadameSheema opened this issue Jan 18, 2024 · 3 comments
Open
Tracked by #153633 ...

[Rule Management] Audit clean-up of data in Cypress #175098

MadameSheema opened this issue Jan 18, 2024 · 3 comments
Labels
Team:Detection Rule Management Security Detection Rule Management Team Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. test

Comments

@MadameSheema
Copy link
Member

Relates to:

#173327
#174247

Each spec file is executed on a clean environment, but, retries are not. Retries are executed on the same environment the execution was initiated, this is why is pretty important to make sure that the data the test may generate is cleaned at the beginning.

We need to make sure that the data the test might generate during its execution is properly cleaned. The best way to clean data is to make sure that all the data the test might generate or create is deleted at the beginning of it in a beforeEach hook.

Making this exercise is beneficial as well to end-up having tests that are independent of each other.

@botelastic botelastic bot added the needs-team Issues missing a team label label Jan 18, 2024
@MadameSheema MadameSheema added Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Detection Rule Management Security Detection Rule Management Team labels Jan 18, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-detection-rule-management (Team:Detection Rule Management)

@elasticmachine
Copy link
Contributor

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

@elasticmachine
Copy link
Contributor

Pinging @elastic/security-detections-response (Team:Detections and Resp)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Detection Rule Management Security Detection Rule Management Team Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. test
Projects
None yet
Development

No branches or pull requests

3 participants