Skip to content

Comments

[8.19] [SecuritySolution][Endpoint][ResponseActions] Update tests to keep it consistent across 8.19/9.1 branches (#226541)#226674

Merged
kibanamachine merged 3 commits intoelastic:8.19from
kibanamachine:backport/8.19/pr-226541
Jul 24, 2025
Merged

[8.19] [SecuritySolution][Endpoint][ResponseActions] Update tests to keep it consistent across 8.19/9.1 branches (#226541)#226674
kibanamachine merged 3 commits intoelastic:8.19from
kibanamachine:backport/8.19/pr-226541

Conversation

@kibanamachine
Copy link
Contributor

Backport

This will backport the following commits from main to 8.19:

Questions ?

Please refer to the Backport tool documentation

… consistent across `8.19`/`9.1` branches (elastic#226541)

## Summary

Minor test update to clean up typo and ensure test setup for runscript
is consistent for 8.19 and 9.1 branches

refs changes in
elastic@92ee813

related: elastic#225916

### Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

- [ ] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [ ] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [ ] This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [ ] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
- [ ] Review the [backport
guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)
and apply applicable `backport:*` labels.

### Identify risks

Does this PR introduce any risks? For example, consider risks like hard
to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified
risk. Invite stakeholders and evaluate how to proceed before merging.

- [ ] [See some risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
- [ ] ...

(cherry picked from commit 9807cbf)
@kibanamachine kibanamachine force-pushed the backport/8.19/pr-226541 branch from c165b9c to 7ceed17 Compare July 5, 2025 13:36
@ashokaditya
Copy link
Member

/ci

@kibanamachine kibanamachine merged commit ca4a733 into elastic:8.19 Jul 24, 2025
8 checks passed
@elasticmachine
Copy link
Contributor

💛 Build succeeded, but was flaky

Failed CI Steps

Test Failures

  • [job] [logs] FTR Configs #66 / Rule execution logic API - Basic License/Essentials Tier @ess @serverless @serverlessQA timestamp tests alerts generated from events with timestamp override field KQL should generate 2 alerts with @timestamp

Metrics [docs]

✅ unchanged

History

cc @ashokaditya

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport This PR is a backport of another PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants