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] Reintroducing burn in Cypress #174902

Open
Tracked by #173508
MadameSheema opened this issue Jan 16, 2024 · 1 comment
Open
Tracked by #173508

[Security Solution] Reintroducing burn in Cypress #174902

MadameSheema opened this issue Jan 16, 2024 · 1 comment
Labels
Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.

Comments

@MadameSheema
Copy link
Member

The concept of "burning tests" in the context of Cypress refers to running tests repeatedly to ensure their reliability and stability. This practice is beneficial for identifying and addressing flakiness, statelessness, and order independence in tests. By burning tests, any new or modified tests are rerun multiple times to detect and prevent potential issues, ultimately contributing to the overall robustness of the testing suite. The burning test approach can help in achieving resilient test results and save buildkite time if we use it as a source of truth for flakiness instead of the flaky test suite runner.

More context:

@MadameSheema MadameSheema added the Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. label Jan 16, 2024
@elasticmachine
Copy link
Contributor

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

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

No branches or pull requests

2 participants