Skip to content

[scout] discover tests with custom server configs#251297

Merged
dmlemeshko merged 17 commits intoelastic:mainfrom
dmlemeshko:scout/discover-tests-with-custom-server-configs
Feb 4, 2026
Merged

[scout] discover tests with custom server configs#251297
dmlemeshko merged 17 commits intoelastic:mainfrom
dmlemeshko:scout/discover-tests-with-custom-server-configs

Conversation

@dmlemeshko
Copy link
Copy Markdown
Contributor

@dmlemeshko dmlemeshko commented Feb 2, 2026

Summary

This PR update Scout discovery command to optionally include configs associated with custom servers directories (located under test/scout_*/ path):

node scripts/scout.js discover-playwright-configs --include-custom-servers

Since some Teams may decide not to run their config in the unified Scout CI execution, I added excluded_configs in .buildkite/scout_ci_config.yml to list them explicitly:

plugins:
  enabled:
    - apm
    - console
    ...
  disabled:

packages:
    ...

# Define test configs to be excluded from automatic discovery & execution in CI environment (process.env.CI=true)
excluded_configs:
  - x-pack/solutions/security/plugins/cloud_security_posture/test/scout_cspm_agentless/ui/parallel.playwright.config.ts

While running on CI environment node scripts/scout.js discover-playwright-configs will exclude those configs and they won't be run.

This PR also removed uiam tests custom CI script/step definition as it is no longer needed.

@dmlemeshko dmlemeshko changed the title Scout/discover tests with custom server configs [scout] discover tests with custom server configs Feb 3, 2026
Comment on lines +258 to +260
const filteredModulesWithExcludedConfigs = process.env.CI
? filterModulesByExcludedConfigPaths(filteredModules, getScoutCiExcludedConfigs())
: filteredModules;
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Locally we still discover all the existing configs, but for CI we will exclude ones listed in .buildkite/scout_ci_config.yml under excluded_configs

@dmlemeshko dmlemeshko marked this pull request as ready for review February 3, 2026 17:32
@dmlemeshko dmlemeshko requested review from a team as code owners February 3, 2026 17:32
@dmlemeshko dmlemeshko self-assigned this Feb 3, 2026
@dmlemeshko dmlemeshko added release_note:skip Skip the PR/issue when compiling release notes backport:version Backport to applied version labels v9.3.0 v9.4.0 test:scout labels Feb 3, 2026
Copy link
Copy Markdown
Contributor

@jbudz jbudz left a comment

Choose a reason for hiding this comment

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

.buildkite LGTM

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251297 locally
cc: @dmlemeshko

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251297 locally
cc: @dmlemeshko

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251297 locally
cc: @dmlemeshko

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251297 locally
cc: @dmlemeshko

2 similar comments
@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251297 locally
cc: @dmlemeshko

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251297 locally
cc: @dmlemeshko

@dmlemeshko
Copy link
Copy Markdown
Contributor Author

💚 All backports created successfully

Status Branch Result
9.3

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

Questions ?

Please refer to the Backport tool documentation

dmlemeshko added a commit to dmlemeshko/kibana that referenced this pull request Feb 17, 2026
## Summary

This PR update Scout discovery command to optionally include configs
associated with custom servers directories (located under
`test/scout_*/` path):

```bash
node scripts/scout.js discover-playwright-configs --include-custom-servers
```

Since some Teams may decide not to run their config in the unified Scout
CI execution, I added `excluded_configs` in
`.buildkite/scout_ci_config.yml` to list them explicitly:

```
plugins:
  enabled:
    - apm
    - console
    ...
  disabled:

packages:
    ...

# Define test configs to be excluded from automatic discovery & execution in CI environment (process.env.CI=true)
excluded_configs:
  - x-pack/solutions/security/plugins/cloud_security_posture/test/scout_cspm_agentless/ui/parallel.playwright.config.ts
```

While running on CI environment `node scripts/scout.js
discover-playwright-configs` will exclude those configs and they won't
be run.

This PR also removed uiam tests custom CI script/step definition as it
is no longer needed.

---------

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

# Conflicts:
#	.buildkite/pipelines/on_merge.yml
#	.buildkite/pipelines/pull_request/scout_uiam_tests.yml
#	.buildkite/scout_ci_config.yml
#	.buildkite/scripts/pipelines/pull_request/pipeline.ts
#	.buildkite/scripts/steps/test/scout_test_run_builder.sh
#	src/platform/packages/shared/kbn-scout/src/cli/config_discovery.test.ts
dmlemeshko added a commit to dmlemeshko/kibana that referenced this pull request Feb 17, 2026
## Summary

This PR update Scout discovery command to optionally include configs
associated with custom servers directories (located under
`test/scout_*/` path):

```bash
node scripts/scout.js discover-playwright-configs --include-custom-servers
```

Since some Teams may decide not to run their config in the unified Scout
CI execution, I added `excluded_configs` in
`.buildkite/scout_ci_config.yml` to list them explicitly:

```
plugins:
  enabled:
    - apm
    - console
    ...
  disabled:

packages:
    ...

# Define test configs to be excluded from automatic discovery & execution in CI environment (process.env.CI=true)
excluded_configs:
  - x-pack/solutions/security/plugins/cloud_security_posture/test/scout_cspm_agentless/ui/parallel.playwright.config.ts
```

While running on CI environment `node scripts/scout.js
discover-playwright-configs` will exclude those configs and they won't
be run.

This PR also removed uiam tests custom CI script/step definition as it
is no longer needed.

---------

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

# Conflicts:
#	.buildkite/pipelines/es_serverless/verify_es_serverless_image.yml
#	.buildkite/pipelines/on_merge.yml
#	.buildkite/pipelines/pull_request/profiling_cypress.yml
#	.buildkite/scout_ci_config.yml
#	.buildkite/scripts/pipelines/pull_request/pipeline.ts
#	.buildkite/scripts/steps/test/scout_test_run_builder.sh
#	src/platform/packages/shared/kbn-scout/src/cli/config_discovery.test.ts
@dmlemeshko
Copy link
Copy Markdown
Contributor Author

💚 All backports created successfully

Status Branch Result
9.2

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

Questions ?

Please refer to the Backport tool documentation

@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: @dmlemeshko

dmlemeshko added a commit that referenced this pull request Feb 18, 2026
…53495)

# Backport

This will backport the following commits from `main` to `9.2`:
- [[scout] discover tests with custom server configs
(#251297)](#251297)

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

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

<!--BACKPORT [{"author":{"name":"Dzmitry
Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2026-02-04T21:21:32Z","message":"[scout]
discover tests with custom server configs (#251297)\n\n##
Summary\n\nThis PR update Scout discovery command to optionally include
configs\nassociated with custom servers directories (located
under\n`test/scout_*/` path):\n\n```bash\nnode scripts/scout.js
discover-playwright-configs --include-custom-servers\n```\n\nSince some
Teams may decide not to run their config in the unified Scout\nCI
execution, I added `excluded_configs`
in\n`.buildkite/scout_ci_config.yml` to list them
explicitly:\n\n```\nplugins:\n enabled:\n - apm\n - console\n ...\n
disabled:\n\npackages:\n ...\n\n# Define test configs to be excluded
from automatic discovery & execution in CI environment
(process.env.CI=true)\nexcluded_configs:\n -
x-pack/solutions/security/plugins/cloud_security_posture/test/scout_cspm_agentless/ui/parallel.playwright.config.ts\n```\n\nWhile
running on CI environment `node
scripts/scout.js\ndiscover-playwright-configs` will exclude those
configs and they won't\nbe run.\n\nThis PR also removed uiam tests
custom CI script/step definition as it\nis no longer
needed.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"7b13120890ee62c2dd3de2cf86d99e967fdcd06f","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport
missing","backport:version","test:scout","v9.3.0","v9.4.0"],"title":"[scout]
discover tests with custom server
configs","number":251297,"url":"https://github.com/elastic/kibana/pull/251297","mergeCommit":{"message":"[scout]
discover tests with custom server configs (#251297)\n\n##
Summary\n\nThis PR update Scout discovery command to optionally include
configs\nassociated with custom servers directories (located
under\n`test/scout_*/` path):\n\n```bash\nnode scripts/scout.js
discover-playwright-configs --include-custom-servers\n```\n\nSince some
Teams may decide not to run their config in the unified Scout\nCI
execution, I added `excluded_configs`
in\n`.buildkite/scout_ci_config.yml` to list them
explicitly:\n\n```\nplugins:\n enabled:\n - apm\n - console\n ...\n
disabled:\n\npackages:\n ...\n\n# Define test configs to be excluded
from automatic discovery & execution in CI environment
(process.env.CI=true)\nexcluded_configs:\n -
x-pack/solutions/security/plugins/cloud_security_posture/test/scout_cspm_agentless/ui/parallel.playwright.config.ts\n```\n\nWhile
running on CI environment `node
scripts/scout.js\ndiscover-playwright-configs` will exclude those
configs and they won't\nbe run.\n\nThis PR also removed uiam tests
custom CI script/step definition as it\nis no longer
needed.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"7b13120890ee62c2dd3de2cf86d99e967fdcd06f"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"9.3","label":"v9.3.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/253483","number":253483,"state":"OPEN"},{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/251297","number":251297,"mergeCommit":{"message":"[scout]
discover tests with custom server configs (#251297)\n\n##
Summary\n\nThis PR update Scout discovery command to optionally include
configs\nassociated with custom servers directories (located
under\n`test/scout_*/` path):\n\n```bash\nnode scripts/scout.js
discover-playwright-configs --include-custom-servers\n```\n\nSince some
Teams may decide not to run their config in the unified Scout\nCI
execution, I added `excluded_configs`
in\n`.buildkite/scout_ci_config.yml` to list them
explicitly:\n\n```\nplugins:\n enabled:\n - apm\n - console\n ...\n
disabled:\n\npackages:\n ...\n\n# Define test configs to be excluded
from automatic discovery & execution in CI environment
(process.env.CI=true)\nexcluded_configs:\n -
x-pack/solutions/security/plugins/cloud_security_posture/test/scout_cspm_agentless/ui/parallel.playwright.config.ts\n```\n\nWhile
running on CI environment `node
scripts/scout.js\ndiscover-playwright-configs` will exclude those
configs and they won't\nbe run.\n\nThis PR also removed uiam tests
custom CI script/step definition as it\nis no longer
needed.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"7b13120890ee62c2dd3de2cf86d99e967fdcd06f"}}]}]
BACKPORT-->

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
@kibanamachine kibanamachine added v9.2.6 v9.3.1 and removed backport missing Added to PRs automatically when the are determined to be missing a backport. labels Feb 18, 2026
dmlemeshko added a commit that referenced this pull request Feb 18, 2026
…53483)

# Backport

This will backport the following commits from `main` to `9.3`:
- [[scout] discover tests with custom server configs
(#251297)](#251297)

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

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

<!--BACKPORT [{"author":{"name":"Dzmitry
Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2026-02-04T21:21:32Z","message":"[scout]
discover tests with custom server configs (#251297)\n\n##
Summary\n\nThis PR update Scout discovery command to optionally include
configs\nassociated with custom servers directories (located
under\n`test/scout_*/` path):\n\n```bash\nnode scripts/scout.js
discover-playwright-configs --include-custom-servers\n```\n\nSince some
Teams may decide not to run their config in the unified Scout\nCI
execution, I added `excluded_configs`
in\n`.buildkite/scout_ci_config.yml` to list them
explicitly:\n\n```\nplugins:\n enabled:\n - apm\n - console\n ...\n
disabled:\n\npackages:\n ...\n\n# Define test configs to be excluded
from automatic discovery & execution in CI environment
(process.env.CI=true)\nexcluded_configs:\n -
x-pack/solutions/security/plugins/cloud_security_posture/test/scout_cspm_agentless/ui/parallel.playwright.config.ts\n```\n\nWhile
running on CI environment `node
scripts/scout.js\ndiscover-playwright-configs` will exclude those
configs and they won't\nbe run.\n\nThis PR also removed uiam tests
custom CI script/step definition as it\nis no longer
needed.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"7b13120890ee62c2dd3de2cf86d99e967fdcd06f","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport
missing","backport:version","test:scout","v9.3.0","v9.4.0"],"title":"[scout]
discover tests with custom server
configs","number":251297,"url":"https://github.com/elastic/kibana/pull/251297","mergeCommit":{"message":"[scout]
discover tests with custom server configs (#251297)\n\n##
Summary\n\nThis PR update Scout discovery command to optionally include
configs\nassociated with custom servers directories (located
under\n`test/scout_*/` path):\n\n```bash\nnode scripts/scout.js
discover-playwright-configs --include-custom-servers\n```\n\nSince some
Teams may decide not to run their config in the unified Scout\nCI
execution, I added `excluded_configs`
in\n`.buildkite/scout_ci_config.yml` to list them
explicitly:\n\n```\nplugins:\n enabled:\n - apm\n - console\n ...\n
disabled:\n\npackages:\n ...\n\n# Define test configs to be excluded
from automatic discovery & execution in CI environment
(process.env.CI=true)\nexcluded_configs:\n -
x-pack/solutions/security/plugins/cloud_security_posture/test/scout_cspm_agentless/ui/parallel.playwright.config.ts\n```\n\nWhile
running on CI environment `node
scripts/scout.js\ndiscover-playwright-configs` will exclude those
configs and they won't\nbe run.\n\nThis PR also removed uiam tests
custom CI script/step definition as it\nis no longer
needed.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"7b13120890ee62c2dd3de2cf86d99e967fdcd06f"}},"sourceBranch":"main","suggestedTargetBranches":["9.3"],"targetPullRequestStates":[{"branch":"9.3","label":"v9.3.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/251297","number":251297,"mergeCommit":{"message":"[scout]
discover tests with custom server configs (#251297)\n\n##
Summary\n\nThis PR update Scout discovery command to optionally include
configs\nassociated with custom servers directories (located
under\n`test/scout_*/` path):\n\n```bash\nnode scripts/scout.js
discover-playwright-configs --include-custom-servers\n```\n\nSince some
Teams may decide not to run their config in the unified Scout\nCI
execution, I added `excluded_configs`
in\n`.buildkite/scout_ci_config.yml` to list them
explicitly:\n\n```\nplugins:\n enabled:\n - apm\n - console\n ...\n
disabled:\n\npackages:\n ...\n\n# Define test configs to be excluded
from automatic discovery & execution in CI environment
(process.env.CI=true)\nexcluded_configs:\n -
x-pack/solutions/security/plugins/cloud_security_posture/test/scout_cspm_agentless/ui/parallel.playwright.config.ts\n```\n\nWhile
running on CI environment `node
scripts/scout.js\ndiscover-playwright-configs` will exclude those
configs and they won't\nbe run.\n\nThis PR also removed uiam tests
custom CI script/step definition as it\nis no longer
needed.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"7b13120890ee62c2dd3de2cf86d99e967fdcd06f"}}]}]
BACKPORT-->

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
@dmlemeshko
Copy link
Copy Markdown
Contributor Author

💚 All backports created successfully

Status Branch Result
8.19

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

Questions ?

Please refer to the Backport tool documentation

dmlemeshko added a commit to dmlemeshko/kibana that referenced this pull request Feb 20, 2026
## Summary

This PR update Scout discovery command to optionally include configs
associated with custom servers directories (located under
`test/scout_*/` path):

```bash
node scripts/scout.js discover-playwright-configs --include-custom-servers
```

Since some Teams may decide not to run their config in the unified Scout
CI execution, I added `excluded_configs` in
`.buildkite/scout_ci_config.yml` to list them explicitly:

```
plugins:
  enabled:
    - apm
    - console
    ...
  disabled:

packages:
    ...

# Define test configs to be excluded from automatic discovery & execution in CI environment (process.env.CI=true)
excluded_configs:
  - x-pack/solutions/security/plugins/cloud_security_posture/test/scout_cspm_agentless/ui/parallel.playwright.config.ts
```

While running on CI environment `node scripts/scout.js
discover-playwright-configs` will exclude those configs and they won't
be run.

This PR also removed uiam tests custom CI script/step definition as it
is no longer needed.

---------

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

# Conflicts:
#	.buildkite/pipelines/es_serverless/verify_es_serverless_image.yml
#	.buildkite/pipelines/on_merge.yml
#	.buildkite/pipelines/pull_request/profiling_cypress.yml
#	.buildkite/scout_ci_config.yml
#	.buildkite/scripts/pipelines/pull_request/pipeline.ts
#	.buildkite/scripts/steps/test/scout_test_run_builder.sh
#	src/platform/packages/shared/kbn-scout/src/cli/config_discovery.test.ts
dmlemeshko added a commit that referenced this pull request Mar 3, 2026
…254155)

# Backport

This will backport the following commits from `main` to `8.19`:
- [[scout] discover tests with custom server configs
(#251297)](#251297)

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

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

<!--BACKPORT [{"author":{"name":"Dzmitry
Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2026-02-04T21:21:32Z","message":"[scout]
discover tests with custom server configs (#251297)\n\n##
Summary\n\nThis PR update Scout discovery command to optionally include
configs\nassociated with custom servers directories (located
under\n`test/scout_*/` path):\n\n```bash\nnode scripts/scout.js
discover-playwright-configs --include-custom-servers\n```\n\nSince some
Teams may decide not to run their config in the unified Scout\nCI
execution, I added `excluded_configs`
in\n`.buildkite/scout_ci_config.yml` to list them
explicitly:\n\n```\nplugins:\n enabled:\n - apm\n - console\n ...\n
disabled:\n\npackages:\n ...\n\n# Define test configs to be excluded
from automatic discovery & execution in CI environment
(process.env.CI=true)\nexcluded_configs:\n -
x-pack/solutions/security/plugins/cloud_security_posture/test/scout_cspm_agentless/ui/parallel.playwright.config.ts\n```\n\nWhile
running on CI environment `node
scripts/scout.js\ndiscover-playwright-configs` will exclude those
configs and they won't\nbe run.\n\nThis PR also removed uiam tests
custom CI script/step definition as it\nis no longer
needed.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"7b13120890ee62c2dd3de2cf86d99e967fdcd06f","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:version","test:scout","v9.3.0","v9.4.0","v9.3.1","v9.2.6"],"title":"[scout]
discover tests with custom server
configs","number":251297,"url":"https://github.com/elastic/kibana/pull/251297","mergeCommit":{"message":"[scout]
discover tests with custom server configs (#251297)\n\n##
Summary\n\nThis PR update Scout discovery command to optionally include
configs\nassociated with custom servers directories (located
under\n`test/scout_*/` path):\n\n```bash\nnode scripts/scout.js
discover-playwright-configs --include-custom-servers\n```\n\nSince some
Teams may decide not to run their config in the unified Scout\nCI
execution, I added `excluded_configs`
in\n`.buildkite/scout_ci_config.yml` to list them
explicitly:\n\n```\nplugins:\n enabled:\n - apm\n - console\n ...\n
disabled:\n\npackages:\n ...\n\n# Define test configs to be excluded
from automatic discovery & execution in CI environment
(process.env.CI=true)\nexcluded_configs:\n -
x-pack/solutions/security/plugins/cloud_security_posture/test/scout_cspm_agentless/ui/parallel.playwright.config.ts\n```\n\nWhile
running on CI environment `node
scripts/scout.js\ndiscover-playwright-configs` will exclude those
configs and they won't\nbe run.\n\nThis PR also removed uiam tests
custom CI script/step definition as it\nis no longer
needed.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"7b13120890ee62c2dd3de2cf86d99e967fdcd06f"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"9.3","label":"v9.3.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/253483","number":253483,"state":"MERGED","mergeCommit":{"sha":"928774cb771dd90e7d7b7f3b0a8b897f905a655f","message":"[9.3]
[scout] discover tests with custom server configs (#251297)
(#253483)\n\n# Backport\n\nThis will backport the following commits from
`main` to `9.3`:\n- [[scout] discover tests with custom server
configs\n(#251297)](https://github.com/elastic/kibana/pull/251297)\n\n\n\n###
Questions ?\nPlease refer to the [Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>"}},{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/251297","number":251297,"mergeCommit":{"message":"[scout]
discover tests with custom server configs (#251297)\n\n##
Summary\n\nThis PR update Scout discovery command to optionally include
configs\nassociated with custom servers directories (located
under\n`test/scout_*/` path):\n\n```bash\nnode scripts/scout.js
discover-playwright-configs --include-custom-servers\n```\n\nSince some
Teams may decide not to run their config in the unified Scout\nCI
execution, I added `excluded_configs`
in\n`.buildkite/scout_ci_config.yml` to list them
explicitly:\n\n```\nplugins:\n enabled:\n - apm\n - console\n ...\n
disabled:\n\npackages:\n ...\n\n# Define test configs to be excluded
from automatic discovery & execution in CI environment
(process.env.CI=true)\nexcluded_configs:\n -
x-pack/solutions/security/plugins/cloud_security_posture/test/scout_cspm_agentless/ui/parallel.playwright.config.ts\n```\n\nWhile
running on CI environment `node
scripts/scout.js\ndiscover-playwright-configs` will exclude those
configs and they won't\nbe run.\n\nThis PR also removed uiam tests
custom CI script/step definition as it\nis no longer
needed.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"7b13120890ee62c2dd3de2cf86d99e967fdcd06f"}},{"branch":"9.2","label":"v9.2.6","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/253495","number":253495,"state":"MERGED","mergeCommit":{"sha":"0e688a14fecb4f8d3e213543e439b82f440ec2fe","message":"[9.2]
[scout] discover tests with custom server configs (#251297)
(#253495)\n\n# Backport\n\nThis will backport the following commits from
`main` to `9.2`:\n- [[scout] discover tests with custom server
configs\n(#251297)](https://github.com/elastic/kibana/pull/251297)\n\n\n\n###
Questions ?\nPlease refer to the [Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\n---------\n\nCo-authored-by:
kibanamachine <42973632+kibanamachine@users.noreply.github.com>"}}]}]
BACKPORT-->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport:version Backport to applied version labels release_note:skip Skip the PR/issue when compiling release notes test:scout v8.19.13 v9.2.6 v9.3.0 v9.3.1 v9.4.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants