-
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
[Defend Workflow] Add Cypress tests to the Kibana release quality gate #187243
Labels
Comments
Pinging @elastic/security-defend-workflows (Team:Defend Workflows) |
Tests currently enabled in the MKI environment without agent enrollment (agentless) and stable over the past seven days (buildkite builds). All Osquery Cypress tests involve agent enrollment by default and are therefore not included here. Cypress DW:
API DW:
|
szwarckonrad
added a commit
that referenced
this issue
Nov 13, 2024
…99742) This PR enables tests in the release pipeline that are 1) agentless (do not involve agent enrollment) and 2) have been stable over the past week. These tests are already running in the periodic pipeline, with addition of `@serverlessQA` tag they will be promoted to be executed in the release pipeline. Test eligibility breakdown - #187243 (comment) CC @MadameSheema
CAWilson94
pushed a commit
to CAWilson94/kibana
that referenced
this issue
Nov 18, 2024
…astic#199742) This PR enables tests in the release pipeline that are 1) agentless (do not involve agent enrollment) and 2) have been stable over the past week. These tests are already running in the periodic pipeline, with addition of `@serverlessQA` tag they will be promoted to be executed in the release pipeline. Test eligibility breakdown - elastic#187243 (comment) CC @MadameSheema
CAWilson94
pushed a commit
to CAWilson94/kibana
that referenced
this issue
Nov 18, 2024
…astic#199742) This PR enables tests in the release pipeline that are 1) agentless (do not involve agent enrollment) and 2) have been stable over the past week. These tests are already running in the periodic pipeline, with addition of `@serverlessQA` tag they will be promoted to be executed in the release pipeline. Test eligibility breakdown - elastic#187243 (comment) CC @MadameSheema
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Add the
@serverlessQA
to all the tests you want to have executed in the second quality gate as part the Kibana serverless release.Please make sure that the tests you are adding are stable in MKI environments (remember that any failure at this stage will block a release to production). The tests should be covering critical paths, behaviours that if are broken or not working properly an SDH or blocker issue might be reported by our customers.
The text was updated successfully, but these errors were encountered: