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] Create a knowledge base of common flake problems with tests #161516

Open
Tracked by #153633
banderror opened this issue Jul 9, 2023 · 4 comments
Open
Tracked by #153633
Labels
docs Team:Detection Engine Security Solution Detection Engine Area 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

@banderror
Copy link
Contributor

banderror commented Jul 9, 2023

Epic: #153633
Related to: #153655

Summary

Create a dev document similar to SDH Tips and Tricks, which will be a knowledge base of common flake problems and how to solve them for Cypress and API integration tests.

For each common problem, documentation should answer these questions:

  • How did you gather the information about the problem and were able to localize it?
  • How did you fix the problem?
@banderror banderror added test docs Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Detection Rule Management Security Detection Rule Management Team Team:Detection Engine Security Solution Detection Engine Area 8.10 candidate labels Jul 9, 2023
@elasticmachine
Copy link
Contributor

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

@elasticmachine
Copy link
Contributor

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

@MadameSheema
Copy link
Member

This is a great idea @banderror!! I believe the Threat Hunting team should be involved/collaborate with this as well since they may have common issues or they can find something that can help your team in the future. I would deeply appreciate if we (sec-eng-prod) can review the solutions to make sure we are not introducing bad testing practices. Thanks!!

@banderror
Copy link
Contributor Author

All thanks go to @marshallmain -- it's his idea 🙂

@MadameSheema We will share the doc with the teams working on Security Solution. It's likely going to be a living document - at some point, folks who will be working on reducing flakes in 8.10 will start adding common problems to it. I'd suggest we sync on the collaboration format once we have the doc created with some content in it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Team:Detection Engine Security Solution Detection Engine Area 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