[ML] Add functional tests for Field stats flyout in Transforms & DFA creation wizard

[qn895]

Summary

Part of #147170. This PR adds functional tests for the Field stats flyout to the Transforms creation wizards.

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
• 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

[elasticmachine]

Pinging @elastic/ml-ui (:ml)

[alvarezmelissa87]

LGTM ⚡

[qn895]

Started flaky test suite runner...

[pheyos]

Also, the flaky test runner has some failures, looking into these...

[qn895]

Started flaky test suite runner...

[pheyos]

Code LGTM
Let's hope that the initial flakiness has been fixed by the changes 🤞

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 69d124f

Failed CI Steps

• FTR Configs #30

Test Failures

• [job] [logs] FTR Configs #30 / Actions and Triggers app Connectors Opsgenie connector page should disable the run button when the message field is not filled

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
ml	3.5MB	3.5MB	+35.0B

History

• 💔 Build #107978 failed 10d9917
• 💚 Build #107705 succeeded 0718d0a
• 💔 Build #107641 failed 7db3a72
• 💔 Build #107421 failed b2304ca
• 💚 Build #107358 succeeded 5e2cb1b

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

cc @qn895

[pheyos]

The flaky test runner failed and from the log it looks like steps are done in a wrong order:

debg Find.existsByDisplayedByCssSelector('[data-test-subj="mlFieldStatsFlyout"]') with timeout=120000
debg TestSubjects.exists(mlFieldStatsFlyoutContent airline-title)
debg Find.existsByDisplayedByCssSelector('[data-test-subj="mlFieldStatsFlyoutContent airline-title"]') with timeout=120000
debg TestSubjects.exists(mlFieldStatsFlyoutContent airline-topValues)
debg Find.existsByDisplayedByCssSelector('[data-test-subj="mlFieldStatsFlyoutContent airline-topValues"]') with timeout=120000
debg TestSubjects.exists(mlFieldStatsFlyout)
debg Find.existsByDisplayedByCssSelector('[data-test-subj="mlFieldStatsFlyout"]') with timeout=2500
debg TestSubjects.click(mlFieldStatsFlyout > euiFlyoutCloseButton)
debg Find.clickByCssSelector('[data-test-subj="mlFieldStatsFlyout"] [data-test-subj="euiFlyoutCloseButton"]') with timeout=10000
debg Find.findByCssSelector('[data-test-subj="mlFieldStatsFlyout"] [data-test-subj="euiFlyoutCloseButton"]') with timeout=10000
debg TestSubjects.missingOrFail(mlFieldStatsFlyout)
debg Find.waitForDeletedByCssSelector('[data-test-subj="mlFieldStatsFlyout"]') with timeout=2500
debg TestSubjects.exists(mlFieldStatsFlyoutContent airline-topValues)
debg Find.existsByDisplayedByCssSelector('[data-test-subj="mlFieldStatsFlyoutContent airline-topValues"]') with timeout=120000
debg --- retry.tryForTime error: [data-test-subj="mlFieldStatsFlyoutContent airline-topValues"] is not displayed

So the test actually closes the flyout and then tries to validate the top values, which obviously can't work. The code for this bit clearly defines a different order: first check the top values then close the flyout:

await this.assertFieldStatContentByType(parentComboBoxSelector, fieldName, fieldType);

if (Array.isArray(expectedTopValuesContent)) {
    await this.assertTopValuesContent(fieldName, fieldType, expectedTopValuesContent);
}
await this.ensureFieldStatsFlyoutClosed();

So I'm not exactly sure what's going wrong here. Also, it doesn't reproduce on my local and the PR CI run also didn't show that error. Maybe the flaky test runner had an issue or was running from a different commit level? Might be worth to give it another run.

[qn895]

Ran the Flaky test suite runner again and it was successful after 50 tries ✅

[kibanamachine]

💚 All backports created successfully

Status	Branch	Result
✅	8.7

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation