Make Index Management functional and API integration tests robust against side effects introduced by Ingest Manager.#70533
Conversation
…inst side effects introduced by Ingest Manager.
|
Pinging @elastic/es-ui (Team:Elasticsearch UI) |
spalger
left a comment
There was a problem hiding this comment.
LGTM, but would you mind reverting 0f418bb in this PR and running against the latest snapshots (instructions)
x-pack/test/api_integration/apis/management/index_management/templates.js
Outdated
Show resolved
Hide resolved
sebelga
left a comment
There was a problem hiding this comment.
LGTM! Although as I commented I would even remove the functional test that could potentially break in the future and does not bring more confidence that our component integration tests provide.
| expect(componentTemplateEmptyPrompt).to.be(true); | ||
| // Verify content. Component templates may have been created by other apps, e.g. Ingest Manager, | ||
| // so we don't make any assertion about the presence or absence of component templates. | ||
| const componentTemplateList = await testSubjects.exists('componentTemplateList'); |
There was a problem hiding this comment.
If no components are created automatically then this test would fail, right? I am not sure that we need this test, as this use case is covered by our component integration tests (mocked empty list = empty prompt, results = template list).
This reverts commit fecd11f.
|
Thanks @sebelga! The entire content area has that data test subject selector applied to it, so it will pass even if the list is empty and displays an empty prompt (or if it's showing the loading state or if there's an error with the request). I agree with you that it might not add any value beyond our component integration tests but I'd like to uncouple that change from the other changes in this PR. @cuff-links I'd like to hear your thoughts on this at some point. |
|
@sebelga Actually you're right, I overlooked the fact that the empty state will return early, so the selector isn't present. I'm going to fix this in another PR. |
💔 Build Failed
Failed CI StepsTest FailuresKibana Pipeline / kibana-xpack-agent / X-Pack Endpoint API Integration Without Ingest Tests.x-pack/test/endpoint_api_integration_no_ingest/apis/metadata·ts.Endpoint plugin test metadata api when ingest manager is not initialized "before all" hook for "metadata api should not return results"Standard OutStack TraceKibana Pipeline / kibana-xpack-agent / X-Pack Endpoint API Integration Without Ingest Tests.x-pack/test/endpoint_api_integration_no_ingest/apis/metadata·ts.Endpoint plugin test metadata api when ingest manager is not initialized "before all" hook for "metadata api should not return results"Standard OutStack TraceKibana Pipeline / x-pack-intake-agent / X-Pack Jest Tests.x-pack/plugins/security_solution/public/timelines/store/timeline.epicLocalStorage persist adding / reordering of a column correctlyStandard OutStack TraceBuild metrics
History
To update your PR or re-run it, just comment with: |
…st against side effects introduced by Ingest Manager. (#70533) (#70612) * Make Index Management functional and API integration tests robust against side effects introduced by Ingest Manager. (#70533) * Update component templates list to render empty prompt inside of content container. Show detail panel when deep-linked, even if there are no component templates. (#70633) Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
Fixes #70532
Addresses failures that were occurring in CI due to entities created by Ingest Manager: