-
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
[Stack Monitoring] Fix Kibana rules and actions integration test #138090
Conversation
e11ed98
to
95efcd3
Compare
const { body } = await supertest | ||
.post('/api/monitoring/v1/clusters/SvjwrFv6Rvuqjm9-cSSVEg') | ||
.set('kbn-xsrf', 'xxx') | ||
.send({ timeRange, codePaths: ['all'] }) | ||
.expect(200); | ||
expect(body).to.eql(fixture); | ||
|
||
expect(body[0].kibana.rules).to.eql(fixture[0].kibana.rules); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
rules
is the most important things to be validated by this test, based on the documents that are created by the archiver.
Pinging @elastic/infra-monitoring-ui (Team:Infra Monitoring UI) |
@elasticmachine merge upstream |
💚 Build Succeeded
Metrics [docs]
History
To update your PR or re-run it, just comment with: |
…stic#138090) * Skip rules and actions integration tests for esft test runs * Change what is validated in the kibana rules unit test Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> (cherry picked from commit 9cc5037)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
…stic#138090) (elastic#138269) * Skip rules and actions integration tests for esft test runs * Change what is validated in the kibana rules unit test Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> (cherry picked from commit 9cc5037) Co-authored-by: Carlos Crespo <crespocarlos@users.noreply.github.com>
Summary
According to #136912, the test fails when running on cloud, because:
Since there are some tests in the
monitoring
test suite already validating theapm.config.container
attribute and the entire cluster, we could keep this test by changing the assertion to validate only what's necessaryFixes: #137739