Repository navigation
[index management] Move tests from FTR to scout - #242825
Merged
Merged
Conversation
…to index_mgmnt_playwright
mattkime
commented
Nov 14, 2025
Contributor
Flaky Test Runner Stats🎉 All tests passed! - kibana-flaky-test-suite-runner#9964[✅] x-pack/platform/plugins/shared/index_management/test/scout/ui/playwright.config.ts: 25/25 tests passed. |
Contributor
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]Async chunks
Unknown metric groupsESLint disabled in files
ESLint disabled line counts
Total ESLint disabled count
History
|
dmlemeshko
approved these changes
Dec 3, 2025
Contributor
|
Starting backport for target branches: 8.19, 9.1, 9.2 |
Contributor
💔 All backports failed
Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation |
kapral18
pushed a commit
to kapral18/kibana
that referenced
this pull request
Dec 3, 2025
## Summary Moving index management tests from FTR to scout. Scout hates it when the data-test-subj value has been used more than once so there are some changes to address that. --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Karen Grigoryan <karen.grigoryan@elastic.co> (cherry picked from commit 7423325) # Conflicts: # x-pack/platform/plugins/shared/index_management/__jest__/client_integration/helpers/test_subjects.ts # x-pack/platform/plugins/shared/index_management/moon.yml # x-pack/platform/plugins/shared/index_management/tsconfig.json
kapral18
pushed a commit
to kapral18/kibana
that referenced
this pull request
Dec 3, 2025
## Summary Moving index management tests from FTR to scout. Scout hates it when the data-test-subj value has been used more than once so there are some changes to address that. --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Karen Grigoryan <karen.grigoryan@elastic.co> (cherry picked from commit 7423325) # Conflicts: # x-pack/platform/plugins/shared/index_management/__jest__/client_integration/helpers/test_subjects.ts # x-pack/platform/plugins/shared/index_management/moon.yml # x-pack/platform/plugins/shared/index_management/tsconfig.json # x-pack/platform/test/functional/apps/index_management/home_page.ts # x-pack/platform/test/functional/apps/index_management/index_details_page.ts # x-pack/platform/test/functional/apps/index_management/index_template_wizard.ts
Contributor
💔 Some backports could not be created
Note: Successful backport PRs will be merged automatically after passing CI. Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation |
Contributor
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
kapral18
pushed a commit
to kapral18/kibana
that referenced
this pull request
Dec 3, 2025
## Summary Moving index management tests from FTR to scout. Scout hates it when the data-test-subj value has been used more than once so there are some changes to address that. --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Karen Grigoryan <karen.grigoryan@elastic.co> (cherry picked from commit 7423325) # Conflicts: # x-pack/platform/plugins/shared/index_management/__jest__/client_integration/helpers/test_subjects.ts # x-pack/platform/plugins/shared/index_management/moon.yml # x-pack/platform/plugins/shared/index_management/tsconfig.json # x-pack/platform/test/functional/apps/index_management/home_page.ts # x-pack/platform/test/functional/apps/index_management/index_details_page.ts # x-pack/platform/test/functional/apps/index_management/index_template_wizard.ts
kapral18
added a commit
that referenced
this pull request
Dec 3, 2025
) # Backport This will backport the following commits from `main` to `9.2`: - [[index management] Move tests from FTR to scout (#242825)](#242825) <!--- Backport version: 10.2.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Matthew Kime","email":"matt@mattki.me"},"sourceCommit":{"committedDate":"2025-12-03T07:31:36Z","message":"[index management] Move tests from FTR to scout (#242825)\n\n## Summary\n\nMoving index management tests from FTR to scout. Scout hates it when the\ndata-test-subj value has been used more than once so there are some\nchanges to address that.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Karen Grigoryan <karen.grigoryan@elastic.co>","sha":"74233253898ba714584572dceabb404738047e4e","branchLabelMapping":{"^v9.3.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Index Management","Team:Kibana Management","release_note:skip","backport:all-open","v9.3.0"],"title":"[index management] Move tests from FTR to scout","number":242825,"url":"https://github.com/elastic/kibana/pull/242825","mergeCommit":{"message":"[index management] Move tests from FTR to scout (#242825)\n\n## Summary\n\nMoving index management tests from FTR to scout. Scout hates it when the\ndata-test-subj value has been used more than once so there are some\nchanges to address that.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Karen Grigoryan <karen.grigoryan@elastic.co>","sha":"74233253898ba714584572dceabb404738047e4e"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.3.0","branchLabelMappingKey":"^v9.3.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/242825","number":242825,"mergeCommit":{"message":"[index management] Move tests from FTR to scout (#242825)\n\n## Summary\n\nMoving index management tests from FTR to scout. Scout hates it when the\ndata-test-subj value has been used more than once so there are some\nchanges to address that.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Karen Grigoryan <karen.grigoryan@elastic.co>","sha":"74233253898ba714584572dceabb404738047e4e"}}]}] BACKPORT--> Co-authored-by: Matthew Kime <matt@mattki.me>
kapral18
added a commit
that referenced
this pull request
Dec 3, 2025
) # Backport This will backport the following commits from `main` to `9.1`: - [[index management] Move tests from FTR to scout (#242825)](#242825) <!--- Backport version: 10.2.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Matthew Kime","email":"matt@mattki.me"},"sourceCommit":{"committedDate":"2025-12-03T07:31:36Z","message":"[index management] Move tests from FTR to scout (#242825)\n\n## Summary\n\nMoving index management tests from FTR to scout. Scout hates it when the\ndata-test-subj value has been used more than once so there are some\nchanges to address that.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Karen Grigoryan <karen.grigoryan@elastic.co>","sha":"74233253898ba714584572dceabb404738047e4e","branchLabelMapping":{"^v9.3.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Index Management","Team:Kibana Management","release_note:skip","backport:all-open","v9.3.0"],"title":"[index management] Move tests from FTR to scout","number":242825,"url":"https://github.com/elastic/kibana/pull/242825","mergeCommit":{"message":"[index management] Move tests from FTR to scout (#242825)\n\n## Summary\n\nMoving index management tests from FTR to scout. Scout hates it when the\ndata-test-subj value has been used more than once so there are some\nchanges to address that.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Karen Grigoryan <karen.grigoryan@elastic.co>","sha":"74233253898ba714584572dceabb404738047e4e"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.3.0","branchLabelMappingKey":"^v9.3.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/242825","number":242825,"mergeCommit":{"message":"[index management] Move tests from FTR to scout (#242825)\n\n## Summary\n\nMoving index management tests from FTR to scout. Scout hates it when the\ndata-test-subj value has been used more than once so there are some\nchanges to address that.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Karen Grigoryan <karen.grigoryan@elastic.co>","sha":"74233253898ba714584572dceabb404738047e4e"}}]}] BACKPORT--> Co-authored-by: Matthew Kime <matt@mattki.me>
kapral18
added a commit
that referenced
this pull request
Dec 3, 2025
…5179) # Backport This will backport the following commits from `main` to `8.19`: - [[index management] Move tests from FTR to scout (#242825)](#242825) <!--- Backport version: 10.2.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Matthew Kime","email":"matt@mattki.me"},"sourceCommit":{"committedDate":"2025-12-03T07:31:36Z","message":"[index management] Move tests from FTR to scout (#242825)\n\n## Summary\n\nMoving index management tests from FTR to scout. Scout hates it when the\ndata-test-subj value has been used more than once so there are some\nchanges to address that.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Karen Grigoryan <karen.grigoryan@elastic.co>","sha":"74233253898ba714584572dceabb404738047e4e","branchLabelMapping":{"^v9.3.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Index Management","Team:Kibana Management","release_note:skip","backport:all-open","v9.3.0"],"title":"[index management] Move tests from FTR to scout","number":242825,"url":"https://github.com/elastic/kibana/pull/242825","mergeCommit":{"message":"[index management] Move tests from FTR to scout (#242825)\n\n## Summary\n\nMoving index management tests from FTR to scout. Scout hates it when the\ndata-test-subj value has been used more than once so there are some\nchanges to address that.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Karen Grigoryan <karen.grigoryan@elastic.co>","sha":"74233253898ba714584572dceabb404738047e4e"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.3.0","branchLabelMappingKey":"^v9.3.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/242825","number":242825,"mergeCommit":{"message":"[index management] Move tests from FTR to scout (#242825)\n\n## Summary\n\nMoving index management tests from FTR to scout. Scout hates it when the\ndata-test-subj value has been used more than once so there are some\nchanges to address that.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Karen Grigoryan <karen.grigoryan@elastic.co>","sha":"74233253898ba714584572dceabb404738047e4e"}},{"url":"https://github.com/elastic/kibana/pull/245141","number":245141,"branch":"9.2","state":"OPEN"},{"url":"https://github.com/elastic/kibana/pull/245175","number":245175,"branch":"9.1","state":"OPEN"}]}] BACKPORT--> Co-authored-by: Matthew Kime <matt@mattki.me>
JordanSh
pushed a commit
to JordanSh/kibana
that referenced
this pull request
Dec 9, 2025
## Summary Moving index management tests from FTR to scout. Scout hates it when the data-test-subj value has been used more than once so there are some changes to address that. --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Karen Grigoryan <karen.grigoryan@elastic.co>
10 tasks done
kibanamachine
added a commit
that referenced
this pull request
Aug 5, 2026
…82869) Fixes #279682 - likely introduced by #242825 (cc @mattkime) ### Summary - The shared `navigateToIndexManagementTab` helper did `goto()` (default **Indices** page) then immediately clicked the requested tab, so the tab-click's 10s actionability budget was the only window covering Kibana app bootstrap — on a slow CI lane it expired (`locator.click: Timeout 10000ms exceeded` on `templatesTab`). - This patch deep-links straight to the section route (`gotoApp('management/data/index_management/<tab>')`) and asserts the tab rendered, removing both the tab-click race and the dependency on the Indices list loading. ### Context - Follows the failed-test investigator's preferred fix ([comment](#279682 (comment))): deep-link to the tab route rather than loading `/indices` and clicking. Their screenshot showed the tab bar rendered while the default Indices content was still "Loading indices...", i.e. the app was mid-bootstrap when the click's wait expired. - I re-investigated because that comment was >2 weeks old (posted 2026-07-21). The helper is unchanged since then, and all three sibling `index_template_wizard*` specs still issue the identical `navigateToIndexManagementTab('templates')` call and passed in the same run — confirming a timing flake intrinsic to the helper, not a product/selector defect. - The `Section` enum values (`indices`, `templates`, ...) exactly match the `/:section(...)` route, so deep-linking lands on the same end state the tab click reached — just without the intermediate Indices load. - Single recorded failure so far: `appex-qa-stateful-kibana-scout-tests` on `main` (cloud-stateful-classic), during a 00:00 scheduled run where two unrelated tests also timed out (lane under resource pressure). <details> <summary>Verification</summary> #### Verified locally - ✅ Passed: `node scripts/eslint x-pack/platform/plugins/shared/index_management/test/scout/ui/fixtures/page_objects/index_management_page.ts` -⚠️ `node scripts/type_check --project x-pack/platform/plugins/shared/index_management/tsconfig.json` — could not complete: tsgo was OOM-killed (SIGKILL) in the sandbox regardless of heap size, an environment limit rather than a type error. The change is type-safe by inspection — `gotoApp(appName: string)` is used identically by the adjacent `goto()`, and `expect(locator).toBeVisible()` matches the pattern used throughout this file (`expect` is already imported). #### Not verified locally - The Scout spec itself cannot run here (needs a live Elasticsearch + Kibana); behavior under CI parallel load is covered by this suite's CI lane once merged. </details> <details> <summary>Backporting guidance</summary> Applied `backport:all-open`. The `navigateToIndexManagementTab` helper is byte-identical on every open release branch (`9.5`, `9.4`, `9.3`, `8.19`) with the same racy `goto()`-then-click pattern; the `templatesTab` `data-test-subj` and the `/:section` route exist on all of them (the old helper already clicks that subject), and the patch applies unchanged — so fixing it everywhere is safe and prevents the same flake on those branches. </details> > [!NOTE] > Requested by @mattkime. Share feedback in #kibana-qa. Mention `@copilot` to make quick changes. > Generated by [Flaky Test Fixer](https://github.com/elastic/kibana/actions/runs/30963211959) for #279682 · 71.5 AIC · ⌖ 1.84 AIC · [◷](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: 30963211959, workflow_id: flaky-test-fixer, run: https://github.com/elastic/kibana/actions/runs/30963211959 --> <!-- 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: Tyler Smalley <tyler.smalley@elastic.co>
kibanamachine
added a commit
that referenced
this pull request
Aug 5, 2026
…on (#282869) (#283091) # Backport This will backport the following commits from `main` to `9.5`: - [[Index Management] Fix flaky index template wizard tab navigation (#282869)](#282869) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Kibana Machine","email":"42973632+kibanamachine@users.noreply.github.com"},"sourceCommit":{"committedDate":"2026-08-05T14:00:45Z","message":"[Index Management] Fix flaky index template wizard tab navigation (#282869)\n\nFixes #279682 - likely introduced by #242825 (cc @mattkime)\n\n### Summary\n- The shared `navigateToIndexManagementTab` helper did `goto()` (default\n**Indices** page) then immediately clicked the requested tab, so the\ntab-click's 10s actionability budget was the only window covering Kibana\napp bootstrap — on a slow CI lane it expired (`locator.click: Timeout\n10000ms exceeded` on `templatesTab`).\n- This patch deep-links straight to the section route\n(`gotoApp('management/data/index_management/<tab>')`) and asserts the\ntab rendered, removing both the tab-click race and the dependency on the\nIndices list loading.\n\n### Context\n- Follows the failed-test investigator's preferred fix\n([comment](https://github.com/elastic/kibana/issues/279682#issuecomment-5029148383)):\ndeep-link to the tab route rather than loading `/indices` and clicking.\nTheir screenshot showed the tab bar rendered while the default Indices\ncontent was still \"Loading indices...\", i.e. the app was mid-bootstrap\nwhen the click's wait expired.\n- I re-investigated because that comment was >2 weeks old (posted\n2026-07-21). The helper is unchanged since then, and all three sibling\n`index_template_wizard*` specs still issue the identical\n`navigateToIndexManagementTab('templates')` call and passed in the same\nrun — confirming a timing flake intrinsic to the helper, not a\nproduct/selector defect.\n- The `Section` enum values (`indices`, `templates`, ...) exactly match\nthe `/:section(...)` route, so deep-linking lands on the same end state\nthe tab click reached — just without the intermediate Indices load.\n- Single recorded failure so far: `appex-qa-stateful-kibana-scout-tests`\non `main` (cloud-stateful-classic), during a 00:00 scheduled run where\ntwo unrelated tests also timed out (lane under resource pressure).\n\n<details>\n<summary>Verification</summary>\n\n#### Verified locally\n\n- ✅ Passed: `node scripts/eslint\nx-pack/platform/plugins/shared/index_management/test/scout/ui/fixtures/page_objects/index_management_page.ts`\n-⚠️ `node scripts/type_check --project\nx-pack/platform/plugins/shared/index_management/tsconfig.json` — could\nnot complete: tsgo was OOM-killed (SIGKILL) in the sandbox regardless of\nheap size, an environment limit rather than a type error. The change is\ntype-safe by inspection — `gotoApp(appName: string)` is used identically\nby the adjacent `goto()`, and `expect(locator).toBeVisible()` matches\nthe pattern used throughout this file (`expect` is already imported).\n\n#### Not verified locally\n\n- The Scout spec itself cannot run here (needs a live Elasticsearch +\nKibana); behavior under CI parallel load is covered by this suite's CI\nlane once merged.\n\n</details>\n\n<details>\n<summary>Backporting guidance</summary>\n\nApplied `backport:all-open`. The `navigateToIndexManagementTab` helper\nis byte-identical on every open release branch (`9.5`, `9.4`, `9.3`,\n`8.19`) with the same racy `goto()`-then-click pattern; the\n`templatesTab` `data-test-subj` and the `/:section` route exist on all\nof them (the old helper already clicks that subject), and the patch\napplies unchanged — so fixing it everywhere is safe and prevents the\nsame flake on those branches.\n\n</details>\n\n> [!NOTE]\n> Requested by @mattkime. Share feedback in #kibana-qa. Mention\n`@copilot` to make quick changes.\n\n\n\n\n> Generated by [Flaky Test\nFixer](https://github.com/elastic/kibana/actions/runs/30963211959) for\n#279682 · 71.5 AIC · ⌖ 1.84 AIC ·\n[◷](https://github.com/search?q=repo%3Aelastic%2Fkibana+%22gh-aw-workflow-id%3A+flaky-test-fixer%22&type=pullrequests)\n\n\n\n\n\n\nCo-authored-by: Claude Opus 4 (1M context) <noreply@anthropic.com>\nCo-authored-by: Tyler Smalley <tyler.smalley@elastic.co>","sha":"bbb7d1c951fa036844efaff08420b3012ad0342f","branchLabelMapping":{"^v9.6.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","flaky-test-fixer","reviewer:scout","flaky-fix-check:passed","v9.6.0"],"title":"[Index Management] Fix flaky index template wizard tab navigation","number":282869,"url":"https://github.com/elastic/kibana/pull/282869","mergeCommit":{"message":"[Index Management] Fix flaky index template wizard tab navigation (#282869)\n\nFixes #279682 - likely introduced by #242825 (cc @mattkime)\n\n### Summary\n- The shared `navigateToIndexManagementTab` helper did `goto()` (default\n**Indices** page) then immediately clicked the requested tab, so the\ntab-click's 10s actionability budget was the only window covering Kibana\napp bootstrap — on a slow CI lane it expired (`locator.click: Timeout\n10000ms exceeded` on `templatesTab`).\n- This patch deep-links straight to the section route\n(`gotoApp('management/data/index_management/<tab>')`) and asserts the\ntab rendered, removing both the tab-click race and the dependency on the\nIndices list loading.\n\n### Context\n- Follows the failed-test investigator's preferred fix\n([comment](https://github.com/elastic/kibana/issues/279682#issuecomment-5029148383)):\ndeep-link to the tab route rather than loading `/indices` and clicking.\nTheir screenshot showed the tab bar rendered while the default Indices\ncontent was still \"Loading indices...\", i.e. the app was mid-bootstrap\nwhen the click's wait expired.\n- I re-investigated because that comment was >2 weeks old (posted\n2026-07-21). The helper is unchanged since then, and all three sibling\n`index_template_wizard*` specs still issue the identical\n`navigateToIndexManagementTab('templates')` call and passed in the same\nrun — confirming a timing flake intrinsic to the helper, not a\nproduct/selector defect.\n- The `Section` enum values (`indices`, `templates`, ...) exactly match\nthe `/:section(...)` route, so deep-linking lands on the same end state\nthe tab click reached — just without the intermediate Indices load.\n- Single recorded failure so far: `appex-qa-stateful-kibana-scout-tests`\non `main` (cloud-stateful-classic), during a 00:00 scheduled run where\ntwo unrelated tests also timed out (lane under resource pressure).\n\n<details>\n<summary>Verification</summary>\n\n#### Verified locally\n\n- ✅ Passed: `node scripts/eslint\nx-pack/platform/plugins/shared/index_management/test/scout/ui/fixtures/page_objects/index_management_page.ts`\n-⚠️ `node scripts/type_check --project\nx-pack/platform/plugins/shared/index_management/tsconfig.json` — could\nnot complete: tsgo was OOM-killed (SIGKILL) in the sandbox regardless of\nheap size, an environment limit rather than a type error. The change is\ntype-safe by inspection — `gotoApp(appName: string)` is used identically\nby the adjacent `goto()`, and `expect(locator).toBeVisible()` matches\nthe pattern used throughout this file (`expect` is already imported).\n\n#### Not verified locally\n\n- The Scout spec itself cannot run here (needs a live Elasticsearch +\nKibana); behavior under CI parallel load is covered by this suite's CI\nlane once merged.\n\n</details>\n\n<details>\n<summary>Backporting guidance</summary>\n\nApplied `backport:all-open`. The `navigateToIndexManagementTab` helper\nis byte-identical on every open release branch (`9.5`, `9.4`, `9.3`,\n`8.19`) with the same racy `goto()`-then-click pattern; the\n`templatesTab` `data-test-subj` and the `/:section` route exist on all\nof them (the old helper already clicks that subject), and the patch\napplies unchanged — so fixing it everywhere is safe and prevents the\nsame flake on those branches.\n\n</details>\n\n> [!NOTE]\n> Requested by @mattkime. Share feedback in #kibana-qa. Mention\n`@copilot` to make quick changes.\n\n\n\n\n> Generated by [Flaky Test\nFixer](https://github.com/elastic/kibana/actions/runs/30963211959) for\n#279682 · 71.5 AIC · ⌖ 1.84 AIC ·\n[◷](https://github.com/search?q=repo%3Aelastic%2Fkibana+%22gh-aw-workflow-id%3A+flaky-test-fixer%22&type=pullrequests)\n\n\n\n\n\n\nCo-authored-by: Claude Opus 4 (1M context) <noreply@anthropic.com>\nCo-authored-by: Tyler Smalley <tyler.smalley@elastic.co>","sha":"bbb7d1c951fa036844efaff08420b3012ad0342f"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.6.0","branchLabelMappingKey":"^v9.6.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/282869","number":282869,"mergeCommit":{"message":"[Index Management] Fix flaky index template wizard tab navigation (#282869)\n\nFixes #279682 - likely introduced by #242825 (cc @mattkime)\n\n### Summary\n- The shared `navigateToIndexManagementTab` helper did `goto()` (default\n**Indices** page) then immediately clicked the requested tab, so the\ntab-click's 10s actionability budget was the only window covering Kibana\napp bootstrap — on a slow CI lane it expired (`locator.click: Timeout\n10000ms exceeded` on `templatesTab`).\n- This patch deep-links straight to the section route\n(`gotoApp('management/data/index_management/<tab>')`) and asserts the\ntab rendered, removing both the tab-click race and the dependency on the\nIndices list loading.\n\n### Context\n- Follows the failed-test investigator's preferred fix\n([comment](https://github.com/elastic/kibana/issues/279682#issuecomment-5029148383)):\ndeep-link to the tab route rather than loading `/indices` and clicking.\nTheir screenshot showed the tab bar rendered while the default Indices\ncontent was still \"Loading indices...\", i.e. the app was mid-bootstrap\nwhen the click's wait expired.\n- I re-investigated because that comment was >2 weeks old (posted\n2026-07-21). The helper is unchanged since then, and all three sibling\n`index_template_wizard*` specs still issue the identical\n`navigateToIndexManagementTab('templates')` call and passed in the same\nrun — confirming a timing flake intrinsic to the helper, not a\nproduct/selector defect.\n- The `Section` enum values (`indices`, `templates`, ...) exactly match\nthe `/:section(...)` route, so deep-linking lands on the same end state\nthe tab click reached — just without the intermediate Indices load.\n- Single recorded failure so far: `appex-qa-stateful-kibana-scout-tests`\non `main` (cloud-stateful-classic), during a 00:00 scheduled run where\ntwo unrelated tests also timed out (lane under resource pressure).\n\n<details>\n<summary>Verification</summary>\n\n#### Verified locally\n\n- ✅ Passed: `node scripts/eslint\nx-pack/platform/plugins/shared/index_management/test/scout/ui/fixtures/page_objects/index_management_page.ts`\n-⚠️ `node scripts/type_check --project\nx-pack/platform/plugins/shared/index_management/tsconfig.json` — could\nnot complete: tsgo was OOM-killed (SIGKILL) in the sandbox regardless of\nheap size, an environment limit rather than a type error. The change is\ntype-safe by inspection — `gotoApp(appName: string)` is used identically\nby the adjacent `goto()`, and `expect(locator).toBeVisible()` matches\nthe pattern used throughout this file (`expect` is already imported).\n\n#### Not verified locally\n\n- The Scout spec itself cannot run here (needs a live Elasticsearch +\nKibana); behavior under CI parallel load is covered by this suite's CI\nlane once merged.\n\n</details>\n\n<details>\n<summary>Backporting guidance</summary>\n\nApplied `backport:all-open`. The `navigateToIndexManagementTab` helper\nis byte-identical on every open release branch (`9.5`, `9.4`, `9.3`,\n`8.19`) with the same racy `goto()`-then-click pattern; the\n`templatesTab` `data-test-subj` and the `/:section` route exist on all\nof them (the old helper already clicks that subject), and the patch\napplies unchanged — so fixing it everywhere is safe and prevents the\nsame flake on those branches.\n\n</details>\n\n> [!NOTE]\n> Requested by @mattkime. Share feedback in #kibana-qa. Mention\n`@copilot` to make quick changes.\n\n\n\n\n> Generated by [Flaky Test\nFixer](https://github.com/elastic/kibana/actions/runs/30963211959) for\n#279682 · 71.5 AIC · ⌖ 1.84 AIC ·\n[◷](https://github.com/search?q=repo%3Aelastic%2Fkibana+%22gh-aw-workflow-id%3A+flaky-test-fixer%22&type=pullrequests)\n\n\n\n\n\n\nCo-authored-by: Claude Opus 4 (1M context) <noreply@anthropic.com>\nCo-authored-by: Tyler Smalley <tyler.smalley@elastic.co>","sha":"bbb7d1c951fa036844efaff08420b3012ad0342f"}}]}] BACKPORT--> Co-authored-by: Claude Opus 4 (1M context) <noreply@anthropic.com> Co-authored-by: Tyler Smalley <tyler.smalley@elastic.co>
kibanamachine
added a commit
that referenced
this pull request
Aug 5, 2026
…on (#282869) (#283088) # Backport This will backport the following commits from `main` to `9.3`: - [[Index Management] Fix flaky index template wizard tab navigation (#282869)](#282869) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Kibana Machine","email":"42973632+kibanamachine@users.noreply.github.com"},"sourceCommit":{"committedDate":"2026-08-05T14:00:45Z","message":"[Index Management] Fix flaky index template wizard tab navigation (#282869)\n\nFixes #279682 - likely introduced by #242825 (cc @mattkime)\n\n### Summary\n- The shared `navigateToIndexManagementTab` helper did `goto()` (default\n**Indices** page) then immediately clicked the requested tab, so the\ntab-click's 10s actionability budget was the only window covering Kibana\napp bootstrap — on a slow CI lane it expired (`locator.click: Timeout\n10000ms exceeded` on `templatesTab`).\n- This patch deep-links straight to the section route\n(`gotoApp('management/data/index_management/<tab>')`) and asserts the\ntab rendered, removing both the tab-click race and the dependency on the\nIndices list loading.\n\n### Context\n- Follows the failed-test investigator's preferred fix\n([comment](https://github.com/elastic/kibana/issues/279682#issuecomment-5029148383)):\ndeep-link to the tab route rather than loading `/indices` and clicking.\nTheir screenshot showed the tab bar rendered while the default Indices\ncontent was still \"Loading indices...\", i.e. the app was mid-bootstrap\nwhen the click's wait expired.\n- I re-investigated because that comment was >2 weeks old (posted\n2026-07-21). The helper is unchanged since then, and all three sibling\n`index_template_wizard*` specs still issue the identical\n`navigateToIndexManagementTab('templates')` call and passed in the same\nrun — confirming a timing flake intrinsic to the helper, not a\nproduct/selector defect.\n- The `Section` enum values (`indices`, `templates`, ...) exactly match\nthe `/:section(...)` route, so deep-linking lands on the same end state\nthe tab click reached — just without the intermediate Indices load.\n- Single recorded failure so far: `appex-qa-stateful-kibana-scout-tests`\non `main` (cloud-stateful-classic), during a 00:00 scheduled run where\ntwo unrelated tests also timed out (lane under resource pressure).\n\n<details>\n<summary>Verification</summary>\n\n#### Verified locally\n\n- ✅ Passed: `node scripts/eslint\nx-pack/platform/plugins/shared/index_management/test/scout/ui/fixtures/page_objects/index_management_page.ts`\n-⚠️ `node scripts/type_check --project\nx-pack/platform/plugins/shared/index_management/tsconfig.json` — could\nnot complete: tsgo was OOM-killed (SIGKILL) in the sandbox regardless of\nheap size, an environment limit rather than a type error. The change is\ntype-safe by inspection — `gotoApp(appName: string)` is used identically\nby the adjacent `goto()`, and `expect(locator).toBeVisible()` matches\nthe pattern used throughout this file (`expect` is already imported).\n\n#### Not verified locally\n\n- The Scout spec itself cannot run here (needs a live Elasticsearch +\nKibana); behavior under CI parallel load is covered by this suite's CI\nlane once merged.\n\n</details>\n\n<details>\n<summary>Backporting guidance</summary>\n\nApplied `backport:all-open`. The `navigateToIndexManagementTab` helper\nis byte-identical on every open release branch (`9.5`, `9.4`, `9.3`,\n`8.19`) with the same racy `goto()`-then-click pattern; the\n`templatesTab` `data-test-subj` and the `/:section` route exist on all\nof them (the old helper already clicks that subject), and the patch\napplies unchanged — so fixing it everywhere is safe and prevents the\nsame flake on those branches.\n\n</details>\n\n> [!NOTE]\n> Requested by @mattkime. Share feedback in #kibana-qa. Mention\n`@copilot` to make quick changes.\n\n\n\n\n> Generated by [Flaky Test\nFixer](https://github.com/elastic/kibana/actions/runs/30963211959) for\n#279682 · 71.5 AIC · ⌖ 1.84 AIC ·\n[◷](https://github.com/search?q=repo%3Aelastic%2Fkibana+%22gh-aw-workflow-id%3A+flaky-test-fixer%22&type=pullrequests)\n\n\n\n\n\n\nCo-authored-by: Claude Opus 4 (1M context) <noreply@anthropic.com>\nCo-authored-by: Tyler Smalley <tyler.smalley@elastic.co>","sha":"bbb7d1c951fa036844efaff08420b3012ad0342f","branchLabelMapping":{"^v9.6.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","flaky-test-fixer","reviewer:scout","flaky-fix-check:passed","v9.6.0"],"title":"[Index Management] Fix flaky index template wizard tab navigation","number":282869,"url":"https://github.com/elastic/kibana/pull/282869","mergeCommit":{"message":"[Index Management] Fix flaky index template wizard tab navigation (#282869)\n\nFixes #279682 - likely introduced by #242825 (cc @mattkime)\n\n### Summary\n- The shared `navigateToIndexManagementTab` helper did `goto()` (default\n**Indices** page) then immediately clicked the requested tab, so the\ntab-click's 10s actionability budget was the only window covering Kibana\napp bootstrap — on a slow CI lane it expired (`locator.click: Timeout\n10000ms exceeded` on `templatesTab`).\n- This patch deep-links straight to the section route\n(`gotoApp('management/data/index_management/<tab>')`) and asserts the\ntab rendered, removing both the tab-click race and the dependency on the\nIndices list loading.\n\n### Context\n- Follows the failed-test investigator's preferred fix\n([comment](https://github.com/elastic/kibana/issues/279682#issuecomment-5029148383)):\ndeep-link to the tab route rather than loading `/indices` and clicking.\nTheir screenshot showed the tab bar rendered while the default Indices\ncontent was still \"Loading indices...\", i.e. the app was mid-bootstrap\nwhen the click's wait expired.\n- I re-investigated because that comment was >2 weeks old (posted\n2026-07-21). The helper is unchanged since then, and all three sibling\n`index_template_wizard*` specs still issue the identical\n`navigateToIndexManagementTab('templates')` call and passed in the same\nrun — confirming a timing flake intrinsic to the helper, not a\nproduct/selector defect.\n- The `Section` enum values (`indices`, `templates`, ...) exactly match\nthe `/:section(...)` route, so deep-linking lands on the same end state\nthe tab click reached — just without the intermediate Indices load.\n- Single recorded failure so far: `appex-qa-stateful-kibana-scout-tests`\non `main` (cloud-stateful-classic), during a 00:00 scheduled run where\ntwo unrelated tests also timed out (lane under resource pressure).\n\n<details>\n<summary>Verification</summary>\n\n#### Verified locally\n\n- ✅ Passed: `node scripts/eslint\nx-pack/platform/plugins/shared/index_management/test/scout/ui/fixtures/page_objects/index_management_page.ts`\n-⚠️ `node scripts/type_check --project\nx-pack/platform/plugins/shared/index_management/tsconfig.json` — could\nnot complete: tsgo was OOM-killed (SIGKILL) in the sandbox regardless of\nheap size, an environment limit rather than a type error. The change is\ntype-safe by inspection — `gotoApp(appName: string)` is used identically\nby the adjacent `goto()`, and `expect(locator).toBeVisible()` matches\nthe pattern used throughout this file (`expect` is already imported).\n\n#### Not verified locally\n\n- The Scout spec itself cannot run here (needs a live Elasticsearch +\nKibana); behavior under CI parallel load is covered by this suite's CI\nlane once merged.\n\n</details>\n\n<details>\n<summary>Backporting guidance</summary>\n\nApplied `backport:all-open`. The `navigateToIndexManagementTab` helper\nis byte-identical on every open release branch (`9.5`, `9.4`, `9.3`,\n`8.19`) with the same racy `goto()`-then-click pattern; the\n`templatesTab` `data-test-subj` and the `/:section` route exist on all\nof them (the old helper already clicks that subject), and the patch\napplies unchanged — so fixing it everywhere is safe and prevents the\nsame flake on those branches.\n\n</details>\n\n> [!NOTE]\n> Requested by @mattkime. Share feedback in #kibana-qa. Mention\n`@copilot` to make quick changes.\n\n\n\n\n> Generated by [Flaky Test\nFixer](https://github.com/elastic/kibana/actions/runs/30963211959) for\n#279682 · 71.5 AIC · ⌖ 1.84 AIC ·\n[◷](https://github.com/search?q=repo%3Aelastic%2Fkibana+%22gh-aw-workflow-id%3A+flaky-test-fixer%22&type=pullrequests)\n\n\n\n\n\n\nCo-authored-by: Claude Opus 4 (1M context) <noreply@anthropic.com>\nCo-authored-by: Tyler Smalley <tyler.smalley@elastic.co>","sha":"bbb7d1c951fa036844efaff08420b3012ad0342f"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.6.0","branchLabelMappingKey":"^v9.6.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/282869","number":282869,"mergeCommit":{"message":"[Index Management] Fix flaky index template wizard tab navigation (#282869)\n\nFixes #279682 - likely introduced by #242825 (cc @mattkime)\n\n### Summary\n- The shared `navigateToIndexManagementTab` helper did `goto()` (default\n**Indices** page) then immediately clicked the requested tab, so the\ntab-click's 10s actionability budget was the only window covering Kibana\napp bootstrap — on a slow CI lane it expired (`locator.click: Timeout\n10000ms exceeded` on `templatesTab`).\n- This patch deep-links straight to the section route\n(`gotoApp('management/data/index_management/<tab>')`) and asserts the\ntab rendered, removing both the tab-click race and the dependency on the\nIndices list loading.\n\n### Context\n- Follows the failed-test investigator's preferred fix\n([comment](https://github.com/elastic/kibana/issues/279682#issuecomment-5029148383)):\ndeep-link to the tab route rather than loading `/indices` and clicking.\nTheir screenshot showed the tab bar rendered while the default Indices\ncontent was still \"Loading indices...\", i.e. the app was mid-bootstrap\nwhen the click's wait expired.\n- I re-investigated because that comment was >2 weeks old (posted\n2026-07-21). The helper is unchanged since then, and all three sibling\n`index_template_wizard*` specs still issue the identical\n`navigateToIndexManagementTab('templates')` call and passed in the same\nrun — confirming a timing flake intrinsic to the helper, not a\nproduct/selector defect.\n- The `Section` enum values (`indices`, `templates`, ...) exactly match\nthe `/:section(...)` route, so deep-linking lands on the same end state\nthe tab click reached — just without the intermediate Indices load.\n- Single recorded failure so far: `appex-qa-stateful-kibana-scout-tests`\non `main` (cloud-stateful-classic), during a 00:00 scheduled run where\ntwo unrelated tests also timed out (lane under resource pressure).\n\n<details>\n<summary>Verification</summary>\n\n#### Verified locally\n\n- ✅ Passed: `node scripts/eslint\nx-pack/platform/plugins/shared/index_management/test/scout/ui/fixtures/page_objects/index_management_page.ts`\n-⚠️ `node scripts/type_check --project\nx-pack/platform/plugins/shared/index_management/tsconfig.json` — could\nnot complete: tsgo was OOM-killed (SIGKILL) in the sandbox regardless of\nheap size, an environment limit rather than a type error. The change is\ntype-safe by inspection — `gotoApp(appName: string)` is used identically\nby the adjacent `goto()`, and `expect(locator).toBeVisible()` matches\nthe pattern used throughout this file (`expect` is already imported).\n\n#### Not verified locally\n\n- The Scout spec itself cannot run here (needs a live Elasticsearch +\nKibana); behavior under CI parallel load is covered by this suite's CI\nlane once merged.\n\n</details>\n\n<details>\n<summary>Backporting guidance</summary>\n\nApplied `backport:all-open`. The `navigateToIndexManagementTab` helper\nis byte-identical on every open release branch (`9.5`, `9.4`, `9.3`,\n`8.19`) with the same racy `goto()`-then-click pattern; the\n`templatesTab` `data-test-subj` and the `/:section` route exist on all\nof them (the old helper already clicks that subject), and the patch\napplies unchanged — so fixing it everywhere is safe and prevents the\nsame flake on those branches.\n\n</details>\n\n> [!NOTE]\n> Requested by @mattkime. Share feedback in #kibana-qa. Mention\n`@copilot` to make quick changes.\n\n\n\n\n> Generated by [Flaky Test\nFixer](https://github.com/elastic/kibana/actions/runs/30963211959) for\n#279682 · 71.5 AIC · ⌖ 1.84 AIC ·\n[◷](https://github.com/search?q=repo%3Aelastic%2Fkibana+%22gh-aw-workflow-id%3A+flaky-test-fixer%22&type=pullrequests)\n\n\n\n\n\n\nCo-authored-by: Claude Opus 4 (1M context) <noreply@anthropic.com>\nCo-authored-by: Tyler Smalley <tyler.smalley@elastic.co>","sha":"bbb7d1c951fa036844efaff08420b3012ad0342f"}}]}] BACKPORT--> Co-authored-by: Claude Opus 4 (1M context) <noreply@anthropic.com> Co-authored-by: Tyler Smalley <tyler.smalley@elastic.co>
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
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.
Summary
Moving index management tests from FTR to scout. Scout hates it when the data-test-subj value has been used more than once so there are some changes to address that.