[Security Solution] Include only @serverlessQA
Cypress tests to the 2nd quality gate
#182600
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes a bug introduced in #181371 that included all Cypress tests tagged as
@serverless
to the 2nd quality gate (the QA stage in the release pipeline).Current behavior: all tests tagged as
@serverless
run in the 2nd quality gate as part of the Kibana Serverless release process. Many of them are not ready for this and are not supposed to run there.Correct behavior: include only those that were explicitly tagged as
@serverlessQA
.Context
Tests that run in the 2nd quality gate can be found in https://buildkite.com/elastic?filter=security%20solution
For example, in this build we have a script:
that runs
yarn cypress:qa:serverless
which in turn uses thex-pack/test/security_solution_cypress/cypress/cypress_ci_serverless_qa.config.ts
config which used incorrect tags to select Cypress tests.