Failing test: Chrome X-Pack UI Functional Tests.x-pack/test/functional/apps/index_management/index_template_wizard·ts - Index Management app Index template wizard Mappings step clearing up the Numeric subtype dropdown doesn't break the page

[kibanamachine]

A test failed on a tracked branch

Error: retry.try timeout: TimeoutError: Waiting for element to be located By(css selector, [data-test-subj="addFieldButton"])
Wait timed out after 10004ms
    at /var/lib/buildkite-agent/builds/kb-n2-4-spot-020c47d26e68bf92/elastic/kibana-on-merge/kibana/node_modules/selenium-webdriver/lib/webdriver.js:929:17
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at onFailure (retry_for_success.ts:17:9)
    at retryForSuccess (retry_for_success.ts:59:13)
    at RetryService.try (retry.ts:31:12)
    at Proxy.clickByCssSelector (find.ts:407:5)
    at TestSubjects.click (test_subjects.ts:164:5)
    at Context.<anonymous> (index_template_wizard.ts:128:9)
    at Object.apply (wrap_function.js:73:16)

First failure: CI Build - main

[kibanamachine]

New failure: CI Build - main

[elasticmachine]

Pinging @elastic/platform-deployment-management (Team:Deployment Management)

[kibanamachine]

New failure: CI Build - main

[kibanamachine]

New failure: CI Build - main

[mistic]

Skipped.

main: ee56461

[alisonelizabeth]

I verified manually the the UI is working as expected. It looks like this test is fairly new and added via #158912. @ElenaStoeva when you have time, can you take a look?

[ElenaStoeva]

I ran the flaky test runner (https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2433) and, out of 50 runs, the test failed 3 times so it seems that it is indeed flaky.

From the artefacts and the logs of the failed tests, it seems the test cannot navigate the "Add field" button because it's still on the previous step of the index template wizard (it's on the "Index settings" step while it should already be at the "Mappings" step). I imagine that this is because the page hasn't loaded so I plan to try adding checks on each step of the wizard to make sure we are on the right page before proceeding to the next one.