-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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] Improve Cypress burn logic #165130
[security_solution] Improve Cypress burn logic #165130
Conversation
💔 Build FailedFailed CI StepsMetrics [docs]Unknown metric groupsESLint disabled line counts
Total ESLint disabled count
History
To update your PR or re-run it, just comment with: |
acc.push(existing); | ||
} | ||
return acc; | ||
}, [] as string[]); | ||
|
||
// to avoid running too many tests, we limit the number of files to 3 | ||
// we may extend this in the future | ||
files = files.slice(0, 3); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will it always pick up the same 3 on a grep if there are more than 3 changed files?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
correct, until we reach the point where all our tests will be burn-ready
I have limited it to just 3 files to avoid tests timeout
## Summary Add `burn` scripts to `package.json` to simplify the process of testing spec files locally
Summary
Add
burn
scripts topackage.json
to simplify the process of testing spec files locally