Open mgiota opened 1 month ago
Part of https://github.com/elastic/kibana/issues/183263
As part of this PR we introduce a way to write deployment agnostic tests using Mocha tagging. Tests should be written in the new observability_solution_api_integration folder and should be tagged with the @ess and @serverless tags.
observability_solution_api_integration
@ess and @serverless
describe('@ess @serverless Metric threshold rule, () => { describe('Create rule', () => { }); }
x-pack/test/alerting_api_integration/observability/metric_threshold_rule.ts
metric_threshold
serverless.config.ts
ess.config.ts
.buildkite/ftr_configs.yml
@ess @serverless
package.json
alerting_metric_threshold:server:ess
alerting_metric_threshold:runner:ess
alerting_metric_threshold:server:serverless
alerting_metric_threshold:runner:serverless
Pinging @elastic/obs-ux-management-team (Team:obs-ux-management)
Moved to backlog until the related Meta ticket is prioritized.
Part of https://github.com/elastic/kibana/issues/183263
🍒 Summary
As part of this PR we introduce a way to write deployment agnostic tests using Mocha tagging. Tests should be written in the new
observability_solution_api_integration
folder and should be tagged with the@ess and @serverless
tags.Existing tests
x-pack/test/alerting_api_integration/observability/metric_threshold_rule.ts
New folder structure
How to migrate
metric_threshold
folder within alerting folderserverless.config.ts
andess.config.ts
files similar to the burn_rate rule in this PR.buildkite/ftr_configs.yml
@ess @serverless
tagspackage.json
of the observability_solution_api_integration folder similar to the burn_rate commands.alerting_metric_threshold:server:ess
alerting_metric_threshold:runner:ess
alerting_metric_threshold:server:serverless
alerting_metric_threshold:runner:serverless