Skip to content

[Inference UI] Add scout tests for feature settings page#261790

Merged
saikatsarkar056 merged 48 commits into
elastic:mainfrom
saikatsarkar056:scout-feature-settings-tests
Apr 13, 2026
Merged

[Inference UI] Add scout tests for feature settings page#261790
saikatsarkar056 merged 48 commits into
elastic:mainfrom
saikatsarkar056:scout-feature-settings-tests

Conversation

@saikatsarkar056
Copy link
Copy Markdown
Contributor

@saikatsarkar056 saikatsarkar056 commented Apr 7, 2026

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, uses sentence case text and includes i18n support
  • Documentation was added for features that require explanation or tutorials
  • Unit or functional tests 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
  • 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.
  • Flaky Test Runner was used on any tests changed
  • The PR description includes the appropriate Release Notes section, and the correct release_note:* label is applied per the guidelines
  • Review the backport guidelines 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.

@saikatsarkar056 saikatsarkar056 requested review from a team as code owners April 7, 2026 16:31
@saikatsarkar056 saikatsarkar056 marked this pull request as draft April 7, 2026 16:31
@saikatsarkar056 saikatsarkar056 self-assigned this Apr 7, 2026
@saikatsarkar056 saikatsarkar056 added release_note:skip Skip the PR/issue when compiling release notes v9.4.0 backport:skip This PR does not require backporting labels Apr 7, 2026
@saikatsarkar056 saikatsarkar056 changed the title Scout feature settings tests [Inference UI] Add scout tests for feature settings page Apr 7, 2026
@saikatsarkar056 saikatsarkar056 marked this pull request as ready for review April 7, 2026 18:26
@macroscopeapp
Copy link
Copy Markdown
Contributor

macroscopeapp Bot commented Apr 7, 2026

Approvability

Verdict: Needs human review

CODEOWNERS file was modified by a non-owner — requires human review

You can customize Macroscope's approvability policy. Learn more.

@elastic elastic deleted a comment from kibanamachine Apr 7, 2026
@elastic elastic deleted a comment from kibanamachine Apr 7, 2026
@kibanamachine
Copy link
Copy Markdown
Contributor

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.

see run history

Comment thread .agents/skills/scout-ui-testing/SKILL.md
@kibanamachine
Copy link
Copy Markdown
Contributor

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.

see run history

@kibanamachine
Copy link
Copy Markdown
Contributor

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.

see run history

@saikatsarkar056 saikatsarkar056 enabled auto-merge (squash) April 10, 2026 17:53
Comment thread .agents/skills/scout-ui-testing/SKILL.md
Comment thread yarn.lock
Copy link
Copy Markdown
Member

@csr csr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall LGTM, I've added a few suggestions. Feel free to re-request my review anytime.

@saikatsarkar056 saikatsarkar056 merged commit 52c0a54 into elastic:main Apr 13, 2026
22 checks passed
@elasticmachine
Copy link
Copy Markdown
Contributor

💛 Build succeeded, but was flaky

Failed CI Steps

Test Failures

  • [job] [logs] FTR Configs #210 / console app console autocomplete feature ESQL queries does not suggest ESQL when inside non-query triple quotes

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
searchInferenceEndpoints 216.2KB 216.2KB +40.0B

History

cc @saikatsarkar056

tfcmarques pushed a commit to tfcmarques/kibana that referenced this pull request Apr 14, 2026
)

## 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)
- [ ] ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport:skip This PR does not require backporting release_note:skip Skip the PR/issue when compiling release notes Team:Search v9.4.0 v9.5.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants