FTR for playground

[Samiul-TheSoccerFan]

Summary

This PR contains high-priority FTR tests for the playground in ESS.

Checklist

Delete any items that are not applicable to this PR.

• 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
• Flaky Test Runner was used on any tests changed
• Any UI touched in this PR is usable by keyboard only (learn more about keyboard accessibility)
• Any UI touched in this PR does not create any new axe failures (run axe in browser: FF, Chrome)
• If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)
• This was checked for cross-browser compatibility

Risk Matrix

Delete this section if it is not applicable to this PR.

Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release.

When forming the risk matrix, consider some of the following examples and how they may potentially impact the change:

Risk	Probability	Severity	Mitigation/Notes
Multiple Spaces—unexpected behavior in non-default Kibana Space.	Low	High	Integration tests will verify that all features are still supported in non-default Kibana Space and when user switches between spaces.
Multiple nodes—Elasticsearch polling might have race conditions when multiple Kibana nodes are polling for the same tasks.	High	Low	Tasks are idempotent, so executing them multiple times will not result in logical error, but will degrade performance. To test for this case we add plenty of unit tests around this logic and document manual testing procedure.
Code should gracefully handle cases when feature X or plugin Y are disabled.	Medium	High	Unit tests will verify that any feature flag or plugin combination still results in our service operational.
See more potential risk examples

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[yansavitski]

Need to create an api function for creating connector as we don't need to test third-party library. Because if they changed name of field it will broke our test.

[Samiul-TheSoccerFan]

Although a different team maintains it, the main reason to add this step in the test is to verify the flyout opens and the user can create a Gen AI connector and use it immediately.

[yansavitski]

Yeah I agree that we need to test how flyout is opening, because this is related to our code, but testing the flyout itself seems like an antipattern “Third-Party Code Testing.” Which can lead to:

• Unnecessary Maintenance: tests might fail if the third-party library updates or changes, leading to maintenance work unrelated to your actual code.
• Redundancy: Most third-party libraries come with their own tests. Testing them again in integration suite duplicates effort without additional value.
• False Confidence: Passing tests might give a false sense of security about the library’s behavior under all conditions, which isn’t practical to ensure comprehensively.

[kibanamachine]

Flaky Test Runner Stats

🎉 All tests passed! - kibana-flaky-test-suite-runner#6365

[✅] x-pack/test/functional/apps/search_playground/config.ts: 25/25 tests passed.

see run history

[yansavitski]

we don't need here promise.all. guess just forgot to remove it after reducing titleInterceptor

[yansavitski]

Really great job with making llmProxy works 😎

[Samiul-TheSoccerFan]

@elasticmachine merge upstream

[Samiul-TheSoccerFan]

@elasticmachine merge upstream

[kibanamachine]

Flaky Test Runner Stats

🎉 All tests passed! - kibana-flaky-test-suite-runner#6393

[✅] x-pack/test/functional/apps/search_playground/config.ts: 25/25 tests passed.

see run history

[kibanamachine]

Flaky Test Runner Stats

🎉 All tests passed! - kibana-flaky-test-suite-runner#6394

[✅] x-pack/test_serverless/functional/test_suites/search/config.ts: 25/25 tests passed.

see run history

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: c49db73

Failed CI Steps

• Jest Tests #12

Test Failures

• [job] [logs] Jest Tests #12 / Case View Page files tab should render the custom fields correctly

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
searchPlayground	167.7KB	167.9KB	+219.0B

History

• 💚 Build #217705 succeeded 155b6d008c565981897de032f5e03b82ea0c44b3
• 💔 Build #217550 failed d030432f129e74025c41bb1cdfc053d9c1d5736a
• 💔 Build #217541 failed a92f0cb4c6f6be740155e7d9a4a88659ed26f5be

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream