-
Notifications
You must be signed in to change notification settings - Fork 8.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[8.x] [ResponseOps][NewRuleForm] Update functional tests to use new r…
…ule form for stack management (#198915) (#202212) # Backport This will backport the following commits from `main` to `8.x`: - [[ResponseOps][NewRuleForm] Update functional tests to use new rule form for stack management (#198915)](#198915) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Janki Salvi","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-11-28T16:50:07Z","message":"[ResponseOps][NewRuleForm] Update functional tests to use new rule form for stack management (#198915)\n\n## Summary\r\n\r\nMeta issue https://github.com/elastic/kibana/issues/196235\r\n\r\nThis PR updates existing e2e tests to use the new rule form instead of\r\nold rule flyout for `stack management > rules`\r\n\r\n### Flaky test runner\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7488\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7530\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"a89698712b77fd6d4745e82123dccb2758b42e63","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","v9.0.0","Feature:Alerting/RulesManagement","backport:prev-minor","v8.18.0"],"title":"[ResponseOps][NewRuleForm] Update functional tests to use new rule form for stack management","number":198915,"url":"https://github.com/elastic/kibana/pull/198915","mergeCommit":{"message":"[ResponseOps][NewRuleForm] Update functional tests to use new rule form for stack management (#198915)\n\n## Summary\r\n\r\nMeta issue https://github.com/elastic/kibana/issues/196235\r\n\r\nThis PR updates existing e2e tests to use the new rule form instead of\r\nold rule flyout for `stack management > rules`\r\n\r\n### Flaky test runner\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7488\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7530\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"a89698712b77fd6d4745e82123dccb2758b42e63"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/198915","number":198915,"mergeCommit":{"message":"[ResponseOps][NewRuleForm] Update functional tests to use new rule form for stack management (#198915)\n\n## Summary\r\n\r\nMeta issue https://github.com/elastic/kibana/issues/196235\r\n\r\nThis PR updates existing e2e tests to use the new rule form instead of\r\nold rule flyout for `stack management > rules`\r\n\r\n### Flaky test runner\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7488\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7530\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"a89698712b77fd6d4745e82123dccb2758b42e63"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Janki Salvi <[email protected]>
- Loading branch information
1 parent
c171c0e
commit 4581688
Showing
15 changed files
with
290 additions
and
352 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.