[9.5] [Triggers Actions UI] Wait for connectors list to filter in FTR searchConnectors helper (#286190) - #290642
Merged
Conversation
…hConnectors helper (elastic#286190) Fixes elastic#235623 ### Summary - The Opsgenie connector FTR test asserted the connectors list had narrowed to 1 row but read **6**, because the shared `searchConnectors` page-object helper returned before the client-side search filtered the table. - The helper waited on `.euiBasicTable[data-test-subj="actionsTable"]:not(.euiBasicTable-loading)`, whose loading class only tracks the initial data fetch — never EUI's debounced in-memory search — so it resolved instantly against the still-unfiltered table, and `getConnectorsList()` read all accumulated connectors. - Replaced that wait with a bounded `retry.waitFor` that re-reads the rendered rows until they have all settled to match the search text. The search action (type + ENTER) is still issued once; only the DOM read is polled, so no interaction is retried. ### Context - Follows the root cause and fix proposed by the Failed Test Investigator (see the [issue comment](elastic#235623 (comment))). - Long-standing timing race, not a product bug: ~11 failures over 11 months, all on `kibana-on-merge` (local, not Cloud/serverless), spanning 9.1 → 8.19; the latest failure was 2026-08-19 on `kibana-on-merge - 8.19`. - On `main` and `9.5` the Opsgenie FTR spec has been migrated/relocated to Scout, but the buggy shared helper still lives on `main` (used by `apps/rules/details.ts`) and on every open release branch — so the fix lands on `main` and backports to the branches where the Opsgenie FTR test still runs (9.4, 8.19). <details> <summary>Verification</summary> #### Verified locally ✅ Passed: `node scripts/eslint x-pack/platform/test/functional_with_es_ssl/page_objects/triggers_actions_ui_page.ts` #### Not verified locally - FTR tests need a live Elasticsearch + Kibana and cannot run on this runner. - The failing `opsgenie.ts` spec no longer exists on `main` (migrated to Scout), so it can only be exercised on the 9.4 / 8.19 release branches once this fix is backported; behavior under CI parallel load was not measured. </details> <details> <summary>Backporting guidance</summary> Applied `backport:all-open`. The shared `triggers_actions_ui_page.ts` helper exists byte-identically on every open release branch (`9.5`, `9.4`, `8.19` per `versions.json`) and the patch applies unchanged. On 9.4 and 8.19 this directly fixes the flaky Opsgenie FTR spec; on 9.5 the Opsgenie spec has been relocated to Scout but the shared helper is still used by other FTR connector/rules tests, so the fix is a safe improvement there too. </details> > [!NOTE] > Share feedback in #kibana-qa. Mention `@copilot` to make quick changes. > [!WARNING] > <details> > <summary>Firewall blocked 3 domains</summary> > > The following domains were blocked by the firewall during workflow execution: > > - `awmgmcpg` > - `iojs.org` > - `nodejs.org` >> To allow these domains, add them to the `network.allowed` list in your workflow frontmatter: > > ```yaml > network: > allowed: > - defaults > - "awmgmcpg" > - "iojs.org" > - "nodejs.org" > ``` > > See [Network Configuration](https://github.github.com/gh-aw/reference/network/) for more information. > > </details> > Generated by [Flaky Test Fixer](https://github.com/elastic/kibana/actions/runs/32313293293) for elastic#235623 · 285.6 AIC · ⌖ 21 AIC · ⊞ 10.7K · [◷](https://github.com/search?q=repo%3Aelastic%2Fkibana+%22gh-aw-workflow-id%3A+flaky-test-fixer%22&type=pullrequests) <!-- gh-aw-agentic-workflow: Flaky Test Fixer, engine: claude, version: 2.1.165, model: opus, id: 32313293293, workflow_id: flaky-test-fixer, run: https://github.com/elastic/kibana/actions/runs/32313293293 --> <!-- gh-aw-workflow-id: flaky-test-fixer --> <!-- gh-aw-workflow-call-id: elastic/kibana/flaky-test-fixer --> Co-authored-by: Claude Opus 4 (1M context) <noreply@anthropic.com> Co-authored-by: Cesare de Cal <cesare.decal@elastic.co> (cherry picked from commit ec6c7d8)
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Contributor
Author
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]
Test Failures |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backport
This will backport the following commits from
mainto9.5:Questions ?
Please refer to the Backport tool documentation