Skip to content

[FTR to Scout] Migrate x-pack dashboard group2 tests#249233

Merged
jbudz merged 80 commits intoelastic:mainfrom
csr:migrate-dashboard-group2-tests-to-scout
Feb 5, 2026
Merged

[FTR to Scout] Migrate x-pack dashboard group2 tests#249233
jbudz merged 80 commits intoelastic:mainfrom
csr:migrate-dashboard-group2-tests-to-scout

Conversation

@csr
Copy link
Copy Markdown
Member

@csr csr commented Jan 15, 2026

This PR migrates the all FTR tests belonging to the x-pack/platform/test/functional/apps/dashboard/group2/config.ts config to Scout.

Migration

All tests were migrated and older tests deleted. We still maintain the same test coverage.

Results

  • Scout tests are over 4x faster tests than FTR 🚀 Total runtime: Scout (7 seconds) vs FTR (29 seconds)
  • Most of these tests are designed to run on both local deployments and Elastic Cloud ("deployment-agnostic"). The FTR tests only ran on local stateful. Scout makes this easy to achieve: we just need to write the test once and add the appropriate tags!

Why are Scout tests faster?

  • Scout uses two parallel workers to run the tests.
  • We ingest Elasticsearch archives just once, in the global setup hook, before test execution start.
  • FTR test cases that shared identical parts of the user flow were merged into a single Scout test case.
  • We keep Scout best practices in mind: we use Playwright auto-waiting, we design page objects to be performant, and more.

@csr csr self-assigned this Jan 15, 2026
@csr csr changed the title [FTR to Scout] Migrate dashboard group2 tests to Scout [FTR to Scout] Migrate dashboard group2 tests Jan 15, 2026
@kibanamachine

This comment was marked as outdated.

Comment on lines +13 to +16
LENS_BASIC_KIBANA_ARCHIVE,
LENS_BASIC_DATA_VIEW,
LENS_BASIC_TITLE,
LENS_BASIC_TIME_RANGE,
Copy link
Copy Markdown
Member Author

@csr csr Jan 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

New in Scout test: we're moving constants to a dedicated file to reuse them throughout the test (and make the test suite look cleaner).

csr added a commit to csr/kibana that referenced this pull request Feb 6, 2026
)

This PR migrates the all FTR tests belonging to the
`x-pack/platform/test/functional/apps/dashboard/group2/config.ts` config
to Scout.

## Migration

All tests were migrated and older tests deleted. We still maintain the
**same** test coverage.

## Results

* **Scout tests are over 4x faster** tests than FTR 🚀 Total runtime:
Scout (**7 seconds**) vs FTR (**29 seconds**)
* Most of these tests are designed to run on **both local deployments**
and **Elastic Cloud** ("deployment-agnostic"). The FTR tests only ran on
local stateful. Scout makes this easy to achieve: we just need to write
the test once and add the appropriate tags!

### Why are Scout tests faster?

* Scout uses two parallel workers to run the tests.
* We ingest Elasticsearch archives just once, in the [global setup
hook](https://docs.elastic.dev/appex-qa/scout/global-setup-hook), before
test execution start.
* FTR test cases that shared identical parts of the user flow were
merged into a single Scout test case.
* We keep [Scout best
practices](https://docs.elastic.dev/appex-qa/scout/best-practices) in
mind: we use Playwright auto-waiting, we design page objects to be
performant, and more.

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
(cherry picked from commit 50444e3)

# Conflicts:
#	.buildkite/scout_ci_config.yml
#	src/platform/packages/shared/kbn-apm-synthtrace-client/src/lib/serializable.ts
#	src/platform/packages/shared/kbn-scout/src/playwright/page_objects/dashboard_app.ts
#	src/platform/packages/shared/kbn-scout/src/playwright/page_objects/discover_app.ts
#	src/platform/plugins/shared/dashboard/moon.yml
#	src/platform/plugins/shared/dashboard/tsconfig.json
#	x-pack/platform/test/functional/apps/dashboard/group2/_async_dashboard.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/config.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/dashboard_lens_by_value.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/dashboard_maps_by_value.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/dashboard_panel_listing.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/dashboard_search_by_value.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/index.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/migration_smoke_tests/controls_migration_smoke_test.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/migration_smoke_tests/lens_migration_smoke_test.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/migration_smoke_tests/tsvb_migration_smoke_test.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/migration_smoke_tests/visualize_migration_smoke_test.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/panel_time_range.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/panel_titles.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/sync_colors.ts
@csr
Copy link
Copy Markdown
Member Author

csr commented Feb 6, 2026

💚 All backports created successfully

Status Branch Result
9.3
9.2
9.1
8.19

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

Questions ?

Please refer to the Backport tool documentation

csr added a commit to csr/kibana that referenced this pull request Feb 6, 2026
)

This PR migrates the all FTR tests belonging to the
`x-pack/platform/test/functional/apps/dashboard/group2/config.ts` config
to Scout.

## Migration

All tests were migrated and older tests deleted. We still maintain the
**same** test coverage.

## Results

* **Scout tests are over 4x faster** tests than FTR 🚀 Total runtime:
Scout (**7 seconds**) vs FTR (**29 seconds**)
* Most of these tests are designed to run on **both local deployments**
and **Elastic Cloud** ("deployment-agnostic"). The FTR tests only ran on
local stateful. Scout makes this easy to achieve: we just need to write
the test once and add the appropriate tags!

### Why are Scout tests faster?

* Scout uses two parallel workers to run the tests.
* We ingest Elasticsearch archives just once, in the [global setup
hook](https://docs.elastic.dev/appex-qa/scout/global-setup-hook), before
test execution start.
* FTR test cases that shared identical parts of the user flow were
merged into a single Scout test case.
* We keep [Scout best
practices](https://docs.elastic.dev/appex-qa/scout/best-practices) in
mind: we use Playwright auto-waiting, we design page objects to be
performant, and more.

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
(cherry picked from commit 50444e3)

# Conflicts:
#	.buildkite/scout_ci_config.yml
#	src/platform/packages/shared/kbn-apm-synthtrace-client/src/lib/serializable.ts
#	src/platform/packages/shared/kbn-scout/src/playwright/page_objects/dashboard_app.ts
#	src/platform/packages/shared/kbn-scout/src/playwright/page_objects/discover_app.ts
#	src/platform/plugins/shared/dashboard/moon.yml
#	src/platform/plugins/shared/dashboard/tsconfig.json
#	x-pack/platform/test/functional/apps/dashboard/group2/_async_dashboard.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/config.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/dashboard_lens_by_value.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/dashboard_maps_by_value.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/dashboard_panel_listing.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/dashboard_search_by_value.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/index.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/migration_smoke_tests/controls_migration_smoke_test.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/migration_smoke_tests/lens_migration_smoke_test.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/migration_smoke_tests/tsvb_migration_smoke_test.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/migration_smoke_tests/visualize_migration_smoke_test.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/panel_time_range.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/panel_titles.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/sync_colors.ts
csr added a commit to csr/kibana that referenced this pull request Feb 6, 2026
)

This PR migrates the all FTR tests belonging to the
`x-pack/platform/test/functional/apps/dashboard/group2/config.ts` config
to Scout.

## Migration

All tests were migrated and older tests deleted. We still maintain the
**same** test coverage.

## Results

* **Scout tests are over 4x faster** tests than FTR 🚀 Total runtime:
Scout (**7 seconds**) vs FTR (**29 seconds**)
* Most of these tests are designed to run on **both local deployments**
and **Elastic Cloud** ("deployment-agnostic"). The FTR tests only ran on
local stateful. Scout makes this easy to achieve: we just need to write
the test once and add the appropriate tags!

### Why are Scout tests faster?

* Scout uses two parallel workers to run the tests.
* We ingest Elasticsearch archives just once, in the [global setup
hook](https://docs.elastic.dev/appex-qa/scout/global-setup-hook), before
test execution start.
* FTR test cases that shared identical parts of the user flow were
merged into a single Scout test case.
* We keep [Scout best
practices](https://docs.elastic.dev/appex-qa/scout/best-practices) in
mind: we use Playwright auto-waiting, we design page objects to be
performant, and more.

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
(cherry picked from commit 50444e3)
Co-authored-by: Cursor <cursoragent@cursor.com>

# Conflicts:
#	.buildkite/scout_ci_config.yml
#	src/platform/packages/shared/kbn-scout/src/playwright/page_objects/dashboard_app.ts
#	src/platform/packages/shared/kbn-scout/src/playwright/page_objects/discover_app.ts
#	src/platform/packages/shared/response-ops/alerts-table/components/default_cell.tsx
#	src/platform/plugins/shared/dashboard/moon.yml
#	src/platform/plugins/shared/dashboard/tsconfig.json
#	x-pack/platform/test/functional/apps/dashboard/group2/dashboard_panel_listing.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/migration_smoke_tests/controls_migration_smoke_test.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/migration_smoke_tests/lens_migration_smoke_test.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/migration_smoke_tests/tsvb_migration_smoke_test.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/migration_smoke_tests/visualize_migration_smoke_test.ts
csr added a commit to csr/kibana that referenced this pull request Feb 6, 2026
)

This PR migrates the all FTR tests belonging to the
`x-pack/platform/test/functional/apps/dashboard/group2/config.ts` config
to Scout.

## Migration

All tests were migrated and older tests deleted. We still maintain the
**same** test coverage.

## Results

* **Scout tests are over 4x faster** tests than FTR 🚀 Total runtime:
Scout (**7 seconds**) vs FTR (**29 seconds**)
* Most of these tests are designed to run on **both local deployments**
and **Elastic Cloud** ("deployment-agnostic"). The FTR tests only ran on
local stateful. Scout makes this easy to achieve: we just need to write
the test once and add the appropriate tags!

### Why are Scout tests faster?

* Scout uses two parallel workers to run the tests.
* We ingest Elasticsearch archives just once, in the [global setup
hook](https://docs.elastic.dev/appex-qa/scout/global-setup-hook), before
test execution start.
* FTR test cases that shared identical parts of the user flow were
merged into a single Scout test case.
* We keep [Scout best
practices](https://docs.elastic.dev/appex-qa/scout/best-practices) in
mind: we use Playwright auto-waiting, we design page objects to be
performant, and more.

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
(cherry picked from commit 50444e3)
Co-authored-by: Cursor <cursoragent@cursor.com>

# Conflicts:
#	.buildkite/scout_ci_config.yml
#	src/platform/packages/shared/kbn-scout/src/playwright/page_objects/dashboard_app.ts
#	src/platform/packages/shared/kbn-scout/src/playwright/page_objects/discover_app.ts
#	src/platform/plugins/shared/dashboard/moon.yml
#	src/platform/plugins/shared/dashboard/tsconfig.json
#	src/platform/plugins/shared/data/public/search/session/sessions_mgmt/lib/documentation.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/_async_dashboard.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/dashboard_panel_listing.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/migration_smoke_tests/controls_migration_smoke_test.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/migration_smoke_tests/lens_migration_smoke_test.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/migration_smoke_tests/tsvb_migration_smoke_test.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/migration_smoke_tests/visualize_migration_smoke_test.ts
csr added a commit to csr/kibana that referenced this pull request Feb 6, 2026
)

This PR migrates the all FTR tests belonging to the
`x-pack/platform/test/functional/apps/dashboard/group2/config.ts` config
to Scout.

## Migration

All tests were migrated and older tests deleted. We still maintain the
**same** test coverage.

## Results

* **Scout tests are over 4x faster** tests than FTR 🚀 Total runtime:
Scout (**7 seconds**) vs FTR (**29 seconds**)
* Most of these tests are designed to run on **both local deployments**
and **Elastic Cloud** ("deployment-agnostic"). The FTR tests only ran on
local stateful. Scout makes this easy to achieve: we just need to write
the test once and add the appropriate tags!

### Why are Scout tests faster?

* Scout uses two parallel workers to run the tests.
* We ingest Elasticsearch archives just once, in the [global setup
hook](https://docs.elastic.dev/appex-qa/scout/global-setup-hook), before
test execution start.
* FTR test cases that shared identical parts of the user flow were
merged into a single Scout test case.
* We keep [Scout best
practices](https://docs.elastic.dev/appex-qa/scout/best-practices) in
mind: we use Playwright auto-waiting, we design page objects to be
performant, and more.

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
(cherry picked from commit 50444e3)
Co-authored-by: Cursor <cursoragent@cursor.com>

# Conflicts:
#	.buildkite/scout_ci_config.yml
#	src/platform/packages/shared/kbn-apm-synthtrace-client/src/lib/serializable.ts
#	src/platform/packages/shared/kbn-scout/src/playwright/page_objects/dashboard_app.ts
#	src/platform/packages/shared/kbn-scout/src/playwright/page_objects/discover_app.ts
#	src/platform/plugins/shared/dashboard/moon.yml
#	src/platform/plugins/shared/dashboard/tsconfig.json
#	x-pack/platform/test/functional/apps/dashboard/group2/_async_dashboard.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/config.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/dashboard_lens_by_value.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/dashboard_maps_by_value.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/dashboard_panel_listing.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/dashboard_search_by_value.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/index.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/migration_smoke_tests/controls_migration_smoke_test.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/migration_smoke_tests/lens_migration_smoke_test.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/migration_smoke_tests/tsvb_migration_smoke_test.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/migration_smoke_tests/visualize_migration_smoke_test.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/panel_time_range.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/panel_titles.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/sync_colors.ts
csr added a commit to csr/kibana that referenced this pull request Feb 6, 2026
)

This PR migrates the all FTR tests belonging to the
`x-pack/platform/test/functional/apps/dashboard/group2/config.ts` config
to Scout.

## Migration

All tests were migrated and older tests deleted. We still maintain the
**same** test coverage.

## Results

* **Scout tests are over 4x faster** tests than FTR 🚀 Total runtime:
Scout (**7 seconds**) vs FTR (**29 seconds**)
* Most of these tests are designed to run on **both local deployments**
and **Elastic Cloud** ("deployment-agnostic"). The FTR tests only ran on
local stateful. Scout makes this easy to achieve: we just need to write
the test once and add the appropriate tags!

### Why are Scout tests faster?

* Scout uses two parallel workers to run the tests.
* We ingest Elasticsearch archives just once, in the [global setup
hook](https://docs.elastic.dev/appex-qa/scout/global-setup-hook), before
test execution start.
* FTR test cases that shared identical parts of the user flow were
merged into a single Scout test case.
* We keep [Scout best
practices](https://docs.elastic.dev/appex-qa/scout/best-practices) in
mind: we use Playwright auto-waiting, we design page objects to be
performant, and more.

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
(cherry picked from commit 50444e3)
Co-authored-by: Cursor <cursoragent@cursor.com>

# Conflicts:
#	.buildkite/scout_ci_config.yml
#	src/platform/packages/shared/kbn-apm-synthtrace-client/src/lib/serializable.ts
#	src/platform/packages/shared/kbn-scout/src/playwright/page_objects/dashboard_app.ts
#	src/platform/packages/shared/kbn-scout/src/playwright/page_objects/discover_app.ts
#	src/platform/plugins/shared/dashboard/moon.yml
#	src/platform/plugins/shared/dashboard/tsconfig.json
#	x-pack/platform/test/functional/apps/dashboard/group2/_async_dashboard.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/config.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/dashboard_lens_by_value.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/dashboard_maps_by_value.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/dashboard_panel_listing.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/dashboard_search_by_value.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/index.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/migration_smoke_tests/controls_migration_smoke_test.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/migration_smoke_tests/lens_migration_smoke_test.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/migration_smoke_tests/tsvb_migration_smoke_test.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/migration_smoke_tests/visualize_migration_smoke_test.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/panel_time_range.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/panel_titles.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/sync_colors.ts
csr added a commit to csr/kibana that referenced this pull request Feb 6, 2026
)

This PR migrates the all FTR tests belonging to the
`x-pack/platform/test/functional/apps/dashboard/group2/config.ts` config
to Scout.

## Migration

All tests were migrated and older tests deleted. We still maintain the
**same** test coverage.

## Results

* **Scout tests are over 4x faster** tests than FTR 🚀 Total runtime:
Scout (**7 seconds**) vs FTR (**29 seconds**)
* Most of these tests are designed to run on **both local deployments**
and **Elastic Cloud** ("deployment-agnostic"). The FTR tests only ran on
local stateful. Scout makes this easy to achieve: we just need to write
the test once and add the appropriate tags!

### Why are Scout tests faster?

* Scout uses two parallel workers to run the tests.
* We ingest Elasticsearch archives just once, in the [global setup
hook](https://docs.elastic.dev/appex-qa/scout/global-setup-hook), before
test execution start.
* FTR test cases that shared identical parts of the user flow were
merged into a single Scout test case.
* We keep [Scout best
practices](https://docs.elastic.dev/appex-qa/scout/best-practices) in
mind: we use Playwright auto-waiting, we design page objects to be
performant, and more.

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
(cherry picked from commit 50444e3)
Co-authored-by: Cursor <cursoragent@cursor.com>

# Conflicts:
#	.buildkite/scout_ci_config.yml
#	src/platform/packages/shared/kbn-apm-synthtrace-client/src/lib/serializable.ts
#	src/platform/packages/shared/kbn-scout/src/playwright/page_objects/dashboard_app.ts
#	src/platform/packages/shared/kbn-scout/src/playwright/page_objects/discover_app.ts
#	src/platform/plugins/shared/dashboard/moon.yml
#	src/platform/plugins/shared/dashboard/tsconfig.json
#	x-pack/platform/test/functional/apps/dashboard/group2/_async_dashboard.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/config.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/dashboard_lens_by_value.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/dashboard_maps_by_value.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/dashboard_panel_listing.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/dashboard_search_by_value.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/index.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/migration_smoke_tests/controls_migration_smoke_test.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/migration_smoke_tests/lens_migration_smoke_test.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/migration_smoke_tests/tsvb_migration_smoke_test.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/migration_smoke_tests/visualize_migration_smoke_test.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/panel_time_range.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/panel_titles.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/sync_colors.ts
csr added a commit to csr/kibana that referenced this pull request Feb 6, 2026
)

This PR migrates the all FTR tests belonging to the
`x-pack/platform/test/functional/apps/dashboard/group2/config.ts` config
to Scout.

## Migration

All tests were migrated and older tests deleted. We still maintain the
**same** test coverage.

## Results

* **Scout tests are over 4x faster** tests than FTR 🚀 Total runtime:
Scout (**7 seconds**) vs FTR (**29 seconds**)
* Most of these tests are designed to run on **both local deployments**
and **Elastic Cloud** ("deployment-agnostic"). The FTR tests only ran on
local stateful. Scout makes this easy to achieve: we just need to write
the test once and add the appropriate tags!

### Why are Scout tests faster?

* Scout uses two parallel workers to run the tests.
* We ingest Elasticsearch archives just once, in the [global setup
hook](https://docs.elastic.dev/appex-qa/scout/global-setup-hook), before
test execution start.
* FTR test cases that shared identical parts of the user flow were
merged into a single Scout test case.
* We keep [Scout best
practices](https://docs.elastic.dev/appex-qa/scout/best-practices) in
mind: we use Playwright auto-waiting, we design page objects to be
performant, and more.

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
(cherry picked from commit 50444e3)
Co-authored-by: Cursor <cursoragent@cursor.com>

# Conflicts:
#	.buildkite/scout_ci_config.yml
#	src/platform/packages/shared/kbn-apm-synthtrace-client/src/lib/serializable.ts
#	src/platform/packages/shared/kbn-scout/src/playwright/page_objects/dashboard_app.ts
#	src/platform/packages/shared/kbn-scout/src/playwright/page_objects/discover_app.ts
#	src/platform/plugins/shared/dashboard/moon.yml
#	src/platform/plugins/shared/dashboard/tsconfig.json
#	x-pack/platform/test/functional/apps/dashboard/group2/_async_dashboard.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/config.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/dashboard_lens_by_value.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/dashboard_maps_by_value.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/dashboard_panel_listing.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/dashboard_search_by_value.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/index.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/migration_smoke_tests/controls_migration_smoke_test.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/migration_smoke_tests/lens_migration_smoke_test.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/migration_smoke_tests/tsvb_migration_smoke_test.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/migration_smoke_tests/visualize_migration_smoke_test.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/panel_time_range.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/panel_titles.ts
#	x-pack/platform/test/functional/apps/dashboard/group2/sync_colors.ts
csr added a commit that referenced this pull request Feb 6, 2026
…) (#252041)

# Backport

This will backport the following commits from `main` to `9.2`:
- [[FTR to Scout] Migrate `x-pack` dashboard `group2` tests
(#249233)](#249233)

<!--- Backport version: 10.2.0 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Cesare de
Cal","email":"cesare.decal@elastic.co"},"sourceCommit":{"committedDate":"2026-02-05T16:41:56Z","message":"[FTR
to Scout] Migrate `x-pack` dashboard `group2` tests (#249233)\n\nThis PR
migrates the all FTR tests belonging to
the\n`x-pack/platform/test/functional/apps/dashboard/group2/config.ts`
config\nto Scout.\n\n## Migration\n\nAll tests were migrated and older
tests deleted. We still maintain the\n**same** test coverage.\n\n##
Results\n\n* **Scout tests are over 4x faster** tests than FTR 🚀 Total
runtime:\nScout (**7 seconds**) vs FTR (**29 seconds**)\n* Most of these
tests are designed to run on **both local deployments**\nand **Elastic
Cloud** (\"deployment-agnostic\"). The FTR tests only ran on\nlocal
stateful. Scout makes this easy to achieve: we just need to write\nthe
test once and add the appropriate tags!\n\n### Why are Scout tests
faster?\n\n* Scout uses two parallel workers to run the tests.\n* We
ingest Elasticsearch archives just once, in the [global
setup\nhook](https://docs.elastic.dev/appex-qa/scout/global-setup-hook),
before\ntest execution start.\n* FTR test cases that shared identical
parts of the user flow were\nmerged into a single Scout test case.\n* We
keep [Scout
best\npractices](https://docs.elastic.dev/appex-qa/scout/best-practices)
in\nmind: we use Playwright auto-waiting, we design page objects to
be\nperformant, and more.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"50444e3cb36fb11251a31e8a34be877ab0938f80","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","v9.4.0"],"title":"[FTR
to Scout] Migrate `x-pack` dashboard `group2`
tests","number":249233,"url":"https://github.com/elastic/kibana/pull/249233","mergeCommit":{"message":"[FTR
to Scout] Migrate `x-pack` dashboard `group2` tests (#249233)\n\nThis PR
migrates the all FTR tests belonging to
the\n`x-pack/platform/test/functional/apps/dashboard/group2/config.ts`
config\nto Scout.\n\n## Migration\n\nAll tests were migrated and older
tests deleted. We still maintain the\n**same** test coverage.\n\n##
Results\n\n* **Scout tests are over 4x faster** tests than FTR 🚀 Total
runtime:\nScout (**7 seconds**) vs FTR (**29 seconds**)\n* Most of these
tests are designed to run on **both local deployments**\nand **Elastic
Cloud** (\"deployment-agnostic\"). The FTR tests only ran on\nlocal
stateful. Scout makes this easy to achieve: we just need to write\nthe
test once and add the appropriate tags!\n\n### Why are Scout tests
faster?\n\n* Scout uses two parallel workers to run the tests.\n* We
ingest Elasticsearch archives just once, in the [global
setup\nhook](https://docs.elastic.dev/appex-qa/scout/global-setup-hook),
before\ntest execution start.\n* FTR test cases that shared identical
parts of the user flow were\nmerged into a single Scout test case.\n* We
keep [Scout
best\npractices](https://docs.elastic.dev/appex-qa/scout/best-practices)
in\nmind: we use Playwright auto-waiting, we design page objects to
be\nperformant, and more.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"50444e3cb36fb11251a31e8a34be877ab0938f80"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/249233","number":249233,"mergeCommit":{"message":"[FTR
to Scout] Migrate `x-pack` dashboard `group2` tests (#249233)\n\nThis PR
migrates the all FTR tests belonging to
the\n`x-pack/platform/test/functional/apps/dashboard/group2/config.ts`
config\nto Scout.\n\n## Migration\n\nAll tests were migrated and older
tests deleted. We still maintain the\n**same** test coverage.\n\n##
Results\n\n* **Scout tests are over 4x faster** tests than FTR 🚀 Total
runtime:\nScout (**7 seconds**) vs FTR (**29 seconds**)\n* Most of these
tests are designed to run on **both local deployments**\nand **Elastic
Cloud** (\"deployment-agnostic\"). The FTR tests only ran on\nlocal
stateful. Scout makes this easy to achieve: we just need to write\nthe
test once and add the appropriate tags!\n\n### Why are Scout tests
faster?\n\n* Scout uses two parallel workers to run the tests.\n* We
ingest Elasticsearch archives just once, in the [global
setup\nhook](https://docs.elastic.dev/appex-qa/scout/global-setup-hook),
before\ntest execution start.\n* FTR test cases that shared identical
parts of the user flow were\nmerged into a single Scout test case.\n* We
keep [Scout
best\npractices](https://docs.elastic.dev/appex-qa/scout/best-practices)
in\nmind: we use Playwright auto-waiting, we design page objects to
be\nperformant, and more.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"50444e3cb36fb11251a31e8a34be877ab0938f80"}}]}]
BACKPORT-->
csr added a commit that referenced this pull request Feb 6, 2026
) (#252043)

# Backport

This will backport the following commits from `main` to `8.19`:
- [[FTR to Scout] Migrate `x-pack` dashboard `group2` tests
(#249233)](#249233)

<!--- Backport version: 10.2.0 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Cesare de
Cal","email":"cesare.decal@elastic.co"},"sourceCommit":{"committedDate":"2026-02-05T16:41:56Z","message":"[FTR
to Scout] Migrate `x-pack` dashboard `group2` tests (#249233)\n\nThis PR
migrates the all FTR tests belonging to
the\n`x-pack/platform/test/functional/apps/dashboard/group2/config.ts`
config\nto Scout.\n\n## Migration\n\nAll tests were migrated and older
tests deleted. We still maintain the\n**same** test coverage.\n\n##
Results\n\n* **Scout tests are over 4x faster** tests than FTR 🚀 Total
runtime:\nScout (**7 seconds**) vs FTR (**29 seconds**)\n* Most of these
tests are designed to run on **both local deployments**\nand **Elastic
Cloud** (\"deployment-agnostic\"). The FTR tests only ran on\nlocal
stateful. Scout makes this easy to achieve: we just need to write\nthe
test once and add the appropriate tags!\n\n### Why are Scout tests
faster?\n\n* Scout uses two parallel workers to run the tests.\n* We
ingest Elasticsearch archives just once, in the [global
setup\nhook](https://docs.elastic.dev/appex-qa/scout/global-setup-hook),
before\ntest execution start.\n* FTR test cases that shared identical
parts of the user flow were\nmerged into a single Scout test case.\n* We
keep [Scout
best\npractices](https://docs.elastic.dev/appex-qa/scout/best-practices)
in\nmind: we use Playwright auto-waiting, we design page objects to
be\nperformant, and more.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"50444e3cb36fb11251a31e8a34be877ab0938f80","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","v9.4.0"],"title":"[FTR
to Scout] Migrate `x-pack` dashboard `group2`
tests","number":249233,"url":"https://github.com/elastic/kibana/pull/249233","mergeCommit":{"message":"[FTR
to Scout] Migrate `x-pack` dashboard `group2` tests (#249233)\n\nThis PR
migrates the all FTR tests belonging to
the\n`x-pack/platform/test/functional/apps/dashboard/group2/config.ts`
config\nto Scout.\n\n## Migration\n\nAll tests were migrated and older
tests deleted. We still maintain the\n**same** test coverage.\n\n##
Results\n\n* **Scout tests are over 4x faster** tests than FTR 🚀 Total
runtime:\nScout (**7 seconds**) vs FTR (**29 seconds**)\n* Most of these
tests are designed to run on **both local deployments**\nand **Elastic
Cloud** (\"deployment-agnostic\"). The FTR tests only ran on\nlocal
stateful. Scout makes this easy to achieve: we just need to write\nthe
test once and add the appropriate tags!\n\n### Why are Scout tests
faster?\n\n* Scout uses two parallel workers to run the tests.\n* We
ingest Elasticsearch archives just once, in the [global
setup\nhook](https://docs.elastic.dev/appex-qa/scout/global-setup-hook),
before\ntest execution start.\n* FTR test cases that shared identical
parts of the user flow were\nmerged into a single Scout test case.\n* We
keep [Scout
best\npractices](https://docs.elastic.dev/appex-qa/scout/best-practices)
in\nmind: we use Playwright auto-waiting, we design page objects to
be\nperformant, and more.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"50444e3cb36fb11251a31e8a34be877ab0938f80"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/249233","number":249233,"mergeCommit":{"message":"[FTR
to Scout] Migrate `x-pack` dashboard `group2` tests (#249233)\n\nThis PR
migrates the all FTR tests belonging to
the\n`x-pack/platform/test/functional/apps/dashboard/group2/config.ts`
config\nto Scout.\n\n## Migration\n\nAll tests were migrated and older
tests deleted. We still maintain the\n**same** test coverage.\n\n##
Results\n\n* **Scout tests are over 4x faster** tests than FTR 🚀 Total
runtime:\nScout (**7 seconds**) vs FTR (**29 seconds**)\n* Most of these
tests are designed to run on **both local deployments**\nand **Elastic
Cloud** (\"deployment-agnostic\"). The FTR tests only ran on\nlocal
stateful. Scout makes this easy to achieve: we just need to write\nthe
test once and add the appropriate tags!\n\n### Why are Scout tests
faster?\n\n* Scout uses two parallel workers to run the tests.\n* We
ingest Elasticsearch archives just once, in the [global
setup\nhook](https://docs.elastic.dev/appex-qa/scout/global-setup-hook),
before\ntest execution start.\n* FTR test cases that shared identical
parts of the user flow were\nmerged into a single Scout test case.\n* We
keep [Scout
best\npractices](https://docs.elastic.dev/appex-qa/scout/best-practices)
in\nmind: we use Playwright auto-waiting, we design page objects to
be\nperformant, and more.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"50444e3cb36fb11251a31e8a34be877ab0938f80"}}]}]
BACKPORT-->
csr added a commit that referenced this pull request Feb 6, 2026
…) (#252042)

# Backport

This will backport the following commits from `main` to `9.1`:
- [[FTR to Scout] Migrate `x-pack` dashboard `group2` tests
(#249233)](#249233)

<!--- Backport version: 10.2.0 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Cesare de
Cal","email":"cesare.decal@elastic.co"},"sourceCommit":{"committedDate":"2026-02-05T16:41:56Z","message":"[FTR
to Scout] Migrate `x-pack` dashboard `group2` tests (#249233)\n\nThis PR
migrates the all FTR tests belonging to
the\n`x-pack/platform/test/functional/apps/dashboard/group2/config.ts`
config\nto Scout.\n\n## Migration\n\nAll tests were migrated and older
tests deleted. We still maintain the\n**same** test coverage.\n\n##
Results\n\n* **Scout tests are over 4x faster** tests than FTR 🚀 Total
runtime:\nScout (**7 seconds**) vs FTR (**29 seconds**)\n* Most of these
tests are designed to run on **both local deployments**\nand **Elastic
Cloud** (\"deployment-agnostic\"). The FTR tests only ran on\nlocal
stateful. Scout makes this easy to achieve: we just need to write\nthe
test once and add the appropriate tags!\n\n### Why are Scout tests
faster?\n\n* Scout uses two parallel workers to run the tests.\n* We
ingest Elasticsearch archives just once, in the [global
setup\nhook](https://docs.elastic.dev/appex-qa/scout/global-setup-hook),
before\ntest execution start.\n* FTR test cases that shared identical
parts of the user flow were\nmerged into a single Scout test case.\n* We
keep [Scout
best\npractices](https://docs.elastic.dev/appex-qa/scout/best-practices)
in\nmind: we use Playwright auto-waiting, we design page objects to
be\nperformant, and more.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"50444e3cb36fb11251a31e8a34be877ab0938f80","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","v9.4.0"],"title":"[FTR
to Scout] Migrate `x-pack` dashboard `group2`
tests","number":249233,"url":"https://github.com/elastic/kibana/pull/249233","mergeCommit":{"message":"[FTR
to Scout] Migrate `x-pack` dashboard `group2` tests (#249233)\n\nThis PR
migrates the all FTR tests belonging to
the\n`x-pack/platform/test/functional/apps/dashboard/group2/config.ts`
config\nto Scout.\n\n## Migration\n\nAll tests were migrated and older
tests deleted. We still maintain the\n**same** test coverage.\n\n##
Results\n\n* **Scout tests are over 4x faster** tests than FTR 🚀 Total
runtime:\nScout (**7 seconds**) vs FTR (**29 seconds**)\n* Most of these
tests are designed to run on **both local deployments**\nand **Elastic
Cloud** (\"deployment-agnostic\"). The FTR tests only ran on\nlocal
stateful. Scout makes this easy to achieve: we just need to write\nthe
test once and add the appropriate tags!\n\n### Why are Scout tests
faster?\n\n* Scout uses two parallel workers to run the tests.\n* We
ingest Elasticsearch archives just once, in the [global
setup\nhook](https://docs.elastic.dev/appex-qa/scout/global-setup-hook),
before\ntest execution start.\n* FTR test cases that shared identical
parts of the user flow were\nmerged into a single Scout test case.\n* We
keep [Scout
best\npractices](https://docs.elastic.dev/appex-qa/scout/best-practices)
in\nmind: we use Playwright auto-waiting, we design page objects to
be\nperformant, and more.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"50444e3cb36fb11251a31e8a34be877ab0938f80"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/249233","number":249233,"mergeCommit":{"message":"[FTR
to Scout] Migrate `x-pack` dashboard `group2` tests (#249233)\n\nThis PR
migrates the all FTR tests belonging to
the\n`x-pack/platform/test/functional/apps/dashboard/group2/config.ts`
config\nto Scout.\n\n## Migration\n\nAll tests were migrated and older
tests deleted. We still maintain the\n**same** test coverage.\n\n##
Results\n\n* **Scout tests are over 4x faster** tests than FTR 🚀 Total
runtime:\nScout (**7 seconds**) vs FTR (**29 seconds**)\n* Most of these
tests are designed to run on **both local deployments**\nand **Elastic
Cloud** (\"deployment-agnostic\"). The FTR tests only ran on\nlocal
stateful. Scout makes this easy to achieve: we just need to write\nthe
test once and add the appropriate tags!\n\n### Why are Scout tests
faster?\n\n* Scout uses two parallel workers to run the tests.\n* We
ingest Elasticsearch archives just once, in the [global
setup\nhook](https://docs.elastic.dev/appex-qa/scout/global-setup-hook),
before\ntest execution start.\n* FTR test cases that shared identical
parts of the user flow were\nmerged into a single Scout test case.\n* We
keep [Scout
best\npractices](https://docs.elastic.dev/appex-qa/scout/best-practices)
in\nmind: we use Playwright auto-waiting, we design page objects to
be\nperformant, and more.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"50444e3cb36fb11251a31e8a34be877ab0938f80"}}]}]
BACKPORT-->
@kibanamachine kibanamachine added the backport missing Added to PRs automatically when the are determined to be missing a backport. label Feb 9, 2026
@kibanamachine
Copy link
Copy Markdown
Contributor

Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync.
cc: @csr

2 similar comments
@kibanamachine
Copy link
Copy Markdown
Contributor

Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync.
cc: @csr

@kibanamachine
Copy link
Copy Markdown
Contributor

Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync.
cc: @csr

@kibanamachine
Copy link
Copy Markdown
Contributor

Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync.
cc: @csr

2 similar comments
@kibanamachine
Copy link
Copy Markdown
Contributor

Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync.
cc: @csr

@kibanamachine
Copy link
Copy Markdown
Contributor

Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync.
cc: @csr

csr added a commit that referenced this pull request Feb 17, 2026
…) (#252037)

# Backport

This will backport the following commits from `main` to `9.3`:
- [[FTR to Scout] Migrate `x-pack` dashboard `group2` tests
(#249233)](#249233)

<!--- Backport version: 10.2.0 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Cesare de
Cal","email":"cesare.decal@elastic.co"},"sourceCommit":{"committedDate":"2026-02-05T16:41:56Z","message":"[FTR
to Scout] Migrate `x-pack` dashboard `group2` tests (#249233)\n\nThis PR
migrates the all FTR tests belonging to
the\n`x-pack/platform/test/functional/apps/dashboard/group2/config.ts`
config\nto Scout.\n\n## Migration\n\nAll tests were migrated and older
tests deleted. We still maintain the\n**same** test coverage.\n\n##
Results\n\n* **Scout tests are over 4x faster** tests than FTR 🚀 Total
runtime:\nScout (**7 seconds**) vs FTR (**29 seconds**)\n* Most of these
tests are designed to run on **both local deployments**\nand **Elastic
Cloud** (\"deployment-agnostic\"). The FTR tests only ran on\nlocal
stateful. Scout makes this easy to achieve: we just need to write\nthe
test once and add the appropriate tags!\n\n### Why are Scout tests
faster?\n\n* Scout uses two parallel workers to run the tests.\n* We
ingest Elasticsearch archives just once, in the [global
setup\nhook](https://docs.elastic.dev/appex-qa/scout/global-setup-hook),
before\ntest execution start.\n* FTR test cases that shared identical
parts of the user flow were\nmerged into a single Scout test case.\n* We
keep [Scout
best\npractices](https://docs.elastic.dev/appex-qa/scout/best-practices)
in\nmind: we use Playwright auto-waiting, we design page objects to
be\nperformant, and more.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"50444e3cb36fb11251a31e8a34be877ab0938f80","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","v9.4.0"],"title":"[FTR
to Scout] Migrate `x-pack` dashboard `group2`
tests","number":249233,"url":"https://github.com/elastic/kibana/pull/249233","mergeCommit":{"message":"[FTR
to Scout] Migrate `x-pack` dashboard `group2` tests (#249233)\n\nThis PR
migrates the all FTR tests belonging to
the\n`x-pack/platform/test/functional/apps/dashboard/group2/config.ts`
config\nto Scout.\n\n## Migration\n\nAll tests were migrated and older
tests deleted. We still maintain the\n**same** test coverage.\n\n##
Results\n\n* **Scout tests are over 4x faster** tests than FTR 🚀 Total
runtime:\nScout (**7 seconds**) vs FTR (**29 seconds**)\n* Most of these
tests are designed to run on **both local deployments**\nand **Elastic
Cloud** (\"deployment-agnostic\"). The FTR tests only ran on\nlocal
stateful. Scout makes this easy to achieve: we just need to write\nthe
test once and add the appropriate tags!\n\n### Why are Scout tests
faster?\n\n* Scout uses two parallel workers to run the tests.\n* We
ingest Elasticsearch archives just once, in the [global
setup\nhook](https://docs.elastic.dev/appex-qa/scout/global-setup-hook),
before\ntest execution start.\n* FTR test cases that shared identical
parts of the user flow were\nmerged into a single Scout test case.\n* We
keep [Scout
best\npractices](https://docs.elastic.dev/appex-qa/scout/best-practices)
in\nmind: we use Playwright auto-waiting, we design page objects to
be\nperformant, and more.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"50444e3cb36fb11251a31e8a34be877ab0938f80"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/249233","number":249233,"mergeCommit":{"message":"[FTR
to Scout] Migrate `x-pack` dashboard `group2` tests (#249233)\n\nThis PR
migrates the all FTR tests belonging to
the\n`x-pack/platform/test/functional/apps/dashboard/group2/config.ts`
config\nto Scout.\n\n## Migration\n\nAll tests were migrated and older
tests deleted. We still maintain the\n**same** test coverage.\n\n##
Results\n\n* **Scout tests are over 4x faster** tests than FTR 🚀 Total
runtime:\nScout (**7 seconds**) vs FTR (**29 seconds**)\n* Most of these
tests are designed to run on **both local deployments**\nand **Elastic
Cloud** (\"deployment-agnostic\"). The FTR tests only ran on\nlocal
stateful. Scout makes this easy to achieve: we just need to write\nthe
test once and add the appropriate tags!\n\n### Why are Scout tests
faster?\n\n* Scout uses two parallel workers to run the tests.\n* We
ingest Elasticsearch archives just once, in the [global
setup\nhook](https://docs.elastic.dev/appex-qa/scout/global-setup-hook),
before\ntest execution start.\n* FTR test cases that shared identical
parts of the user flow were\nmerged into a single Scout test case.\n* We
keep [Scout
best\npractices](https://docs.elastic.dev/appex-qa/scout/best-practices)
in\nmind: we use Playwright auto-waiting, we design page objects to
be\nperformant, and more.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"50444e3cb36fb11251a31e8a34be877ab0938f80"}}]}]
BACKPORT-->

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
@kibanamachine kibanamachine added v9.3.1 and removed backport missing Added to PRs automatically when the are determined to be missing a backport. labels Feb 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport:all-open Backport to all branches that could still receive a release release_note:skip Skip the PR/issue when compiling release notes v8.19.12 v9.1.11 v9.2.6 v9.3.1 v9.4.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants