[Inference UI] Add scout tests for feature settings page#261790
Conversation
ApprovabilityVerdict: Needs human review CODEOWNERS file was modified by a non-owner — requires human review You can customize Macroscope's approvability policy. Learn more. |
Flaky Test Runner Stats🎉 All tests passed! - kibana-flaky-test-suite-runner#11437[✅] x-pack/platform/plugins/shared/search_inference_endpoints/test/scout/ui/playwright.config.ts: 15/15 tests passed. |
Flaky Test Runner Stats🟠 Some tests failed. - kibana-flaky-test-suite-runner#11530[❌] x-pack/platform/plugins/shared/search_inference_endpoints/test/scout_inference_test/ui/playwright.config.ts: 14/15 tests passed. |
Flaky Test Runner Stats🎉 All tests passed! - kibana-flaky-test-suite-runner#11534[✅] x-pack/platform/plugins/shared/search_inference_endpoints/test/scout_inference_test/ui/playwright.config.ts: 20/20 tests passed. |
csr
left a comment
There was a problem hiding this comment.
Overall LGTM, I've added a few suggestions. Feel free to re-request my review anytime.
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]Async chunks
History
|
) ## Summary Adds Scout tests for the Feature Settings (Model Settings) page under Stack Management. This page allows users to configure default AI models and manage per-feature inference endpoint assignments. ### How to run the tests ``` node scripts/scout.js start-server --arch stateful --domain classic npx playwright test --config .../test/scout/ui/playwright.config.ts --project local --headed feature_settings.spec ``` ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [x] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [x] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ...
Summary
Adds Scout tests for the Feature Settings (Model Settings) page under Stack Management. This page allows users to configure default AI models and manage per-feature inference endpoint assignments.
How to run the tests
Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:breakinglabel should be applied in these situations.release_note:*label is applied per the guidelinesbackport:*labels.Identify risks
Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.
Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.