Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Investigations] Add API tests to the Kibana release quality gate #181687

Closed
Tracked by #181678
MadameSheema opened this issue Apr 25, 2024 · 4 comments
Closed
Tracked by #181678

[Investigations] Add API tests to the Kibana release quality gate #181687

MadameSheema opened this issue Apr 25, 2024 · 4 comments
Assignees
Labels
Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Threat Hunting:Investigations Security Solution Investigations Team Team:Threat Hunting Security Solution Threat Hunting Team
Milestone

Comments

@MadameSheema
Copy link
Member

Add the @serverlessQA to all the tests you want to have executed in the second quality gate as part the Kibana serverless release.

Please make sure that the tests you are adding are stable in MKI environments (remember that any failure at this stage will block a release to production). The tests should be covering critical paths, behaviours that if are broken or not working properly an SDH or blocker issue might be reported by our customers.

@MadameSheema MadameSheema added Team:Threat Hunting Security Solution Threat Hunting Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Threat Hunting:Investigations Security Solution Investigations Team labels Apr 25, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-threat-hunting (Team:Threat Hunting)

@elasticmachine
Copy link
Contributor

Pinging @elastic/security-solution (Team: SecuritySolution)

@elasticmachine
Copy link
Contributor

Pinging @elastic/security-threat-hunting-investigations (Team:Threat Hunting:Investigations)

@PhilippeOberti
Copy link
Contributor

implemented in #200820

kibanamachine pushed a commit to kibanamachine/kibana that referenced this issue Nov 20, 2024
…i integration tests in QA quality gate (elastic#200820)

## Summary

This PR enables the Threat Hunting Investigations api integration tests
to the release quality gate.

elastic#181687
(cherry picked from commit cb02853)
kibanamachine added a commit that referenced this issue Nov 20, 2024
…ons api integration tests in QA quality gate (#200820) (#201036)

# Backport

This will backport the following commits from `main` to `8.x`:
- [[Security Solution] - enable running threat hunting investigations
api integration tests in QA quality gate
(#200820)](#200820)

<!--- Backport version: 9.4.3 -->

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

<!--BACKPORT [{"author":{"name":"Philippe
Oberti","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-11-20T19:53:40Z","message":"[Security
Solution] - enable running threat hunting investigations api integration
tests in QA quality gate (#200820)\n\n## Summary\r\n\r\nThis PR enables
the Threat Hunting Investigations api integration tests\r\nto the
release quality
gate.\r\n\r\nhttps://github.com//issues/181687","sha":"cb02853d14bfbfb4946b2e725777290e56aac696","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat
Hunting:Investigations","backport:version","v8.17.0"],"title":"[Security
Solution] - enable running threat hunting investigations api integration
tests in QA quality
gate","number":200820,"url":"https://github.com/elastic/kibana/pull/200820","mergeCommit":{"message":"[Security
Solution] - enable running threat hunting investigations api integration
tests in QA quality gate (#200820)\n\n## Summary\r\n\r\nThis PR enables
the Threat Hunting Investigations api integration tests\r\nto the
release quality
gate.\r\n\r\nhttps://github.com//issues/181687","sha":"cb02853d14bfbfb4946b2e725777290e56aac696"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/200820","number":200820,"mergeCommit":{"message":"[Security
Solution] - enable running threat hunting investigations api integration
tests in QA quality gate (#200820)\n\n## Summary\r\n\r\nThis PR enables
the Threat Hunting Investigations api integration tests\r\nto the
release quality
gate.\r\n\r\nhttps://github.com//issues/181687","sha":"cb02853d14bfbfb4946b2e725777290e56aac696"}},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Philippe Oberti <[email protected]>
TattdCodeMonkey pushed a commit to TattdCodeMonkey/kibana that referenced this issue Nov 21, 2024
…i integration tests in QA quality gate (elastic#200820)

## Summary

This PR enables the Threat Hunting Investigations api integration tests
to the release quality gate.

elastic#181687
paulinashakirova pushed a commit to paulinashakirova/kibana that referenced this issue Nov 26, 2024
…i integration tests in QA quality gate (elastic#200820)

## Summary

This PR enables the Threat Hunting Investigations api integration tests
to the release quality gate.

elastic#181687
CAWilson94 pushed a commit to CAWilson94/kibana that referenced this issue Dec 12, 2024
…i integration tests in QA quality gate (elastic#200820)

## Summary

This PR enables the Threat Hunting Investigations api integration tests
to the release quality gate.

elastic#181687
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Threat Hunting:Investigations Security Solution Investigations Team Team:Threat Hunting Security Solution Threat Hunting Team
Projects
None yet
Development

No branches or pull requests

3 participants