-
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
Migrate Metric threshold rule tests to deployment agnostic solution #183401
Labels
Team:obs-ux-management
Observability Management User Experience Team
Comments
Pinging @elastic/obs-ux-management-team (Team:obs-ux-management) |
Moved to backlog until the related Meta ticket is prioritized. |
I think we need to update these instructions so they are up to date with the latest on deployment agnostic testing before this issue is "Ready", but then we need to pull this in ASAP. |
Example PR: #187924 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Part of #183263
🍒 Summary
As part of this PR we introduced a way to write deployment agnostic tests using the deployment agnostic framework from Appex QA team. We want to migrate the existing metric threshold rule tests to the new agnostic framework.
Existing tests
x-pack/test/alerting_api_integration/observability/metric_threshold_rule.ts
File structure
How to migrate
In this PR
oblt.stateful.config.ts
andoblt.serverless.config.ts
were added, so no need to create any config file.Existing metric threshold rule tests use a few alerting helpers. In the SLO burn rate rule PR the alerting API was migrated to the deployment agnostic folder. As part of the migration we should use the migrating alerting api.
Here's what you have to do:
x-pack/test/alerting_api_integration/observability/metric_threshold_rule.ts
withinx-pack/test/api_integration/deployment_agnostic/apis/observability/alerting
folderloadTestFile(require.resolve('./metric_threshold_rule'));
DeploymentAgnosticFtrProviderContext
supertestWithoutAuth
andsamlAuth
to generate an API key for user roles and make API callsexpected consumer
How to run
To run serverless
To run stateful
The text was updated successfully, but these errors were encountered: