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

[Serverless][Kibana QA QG] exception_operators_date_numeric_types:essentials:qa:serverless:release tests optimization #192109

Closed
MadameSheema opened this issue Sep 4, 2024 · 5 comments
Assignees
Labels
8.16 candidate Project:Serverless Work as part of the Serverless project for its initial release Project:Serverless-GA Team:Detection Engine Security Solution Detection Engine Area Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.

Comments

@MadameSheema
Copy link
Member

Context

One of the requirements for keeping the overall Security Solution tests executed as part of the Kibana QA quality is gate, is for all the tests to be executed in less than 45 min.

Currently our Kibana QA quality gate takes more than 1h to be executed.

What is happening?

The API tests executed under exception_operators_date_numeric_types:essentials:qa:serverless:release takes more than 46 minues to be executed, if on top of that, we put the time we need to setup and terminate the pipeline, that might be one of the causes why we end up having more than the expected execution time.

What we expect?

For the tests to be refactored, regrouped or parallelized in a way that take less time to be executed. It can be revisited also if all of those tests needs to be executed as part of the Kibana QA quality gate.

To take into consideration

If this ticket is not prioritized and this tasks takes time to be targeted, we'll have to disable the tests in favor of not having the whole pipeline disabled.

@MadameSheema MadameSheema added Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Detection Engine Security Solution Detection Engine Area Team:Detections and Resp Security Detection Response Team labels Sep 4, 2024
@elasticmachine
Copy link
Contributor

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

@elasticmachine
Copy link
Contributor

Pinging @elastic/security-detection-engine (Team:Detection Engine)

@elasticmachine
Copy link
Contributor

Pinging @elastic/security-detections-response (Team:Detections and Resp)

@MadameSheema MadameSheema added the Project:Serverless Work as part of the Serverless project for its initial release label Sep 4, 2024
@yctercero
Copy link
Contributor

I think these are ok to skip in the QA pipeline - I had added them as these have been stable for years now and didn't see any harm, but they would not fall under our "must run" tests for QA pipeline.

yctercero added a commit that referenced this issue Oct 30, 2024
…hreshold preview bug (#197368)

## Summary

This PR breaks down long running FTR groups into smaller chunks that now
run in <~15 min.
- Addresses #192109
- There is no existing ticket but rule_execution group tests are taking
~55m to run and will soon be a bottle neck for us.
- No edits made to any existing tests.
- Purely just a reshuffle of the tests.

See #198209 for details on bug.
kibanamachine pushed a commit to kibanamachine/kibana that referenced this issue Oct 30, 2024
…hreshold preview bug (elastic#197368)

## Summary

This PR breaks down long running FTR groups into smaller chunks that now
run in <~15 min.
- Addresses elastic#192109
- There is no existing ticket but rule_execution group tests are taking
~55m to run and will soon be a bottle neck for us.
- No edits made to any existing tests.
- Purely just a reshuffle of the tests.

See elastic#198209 for details on bug.

(cherry picked from commit cd1fafe)
@yctercero
Copy link
Contributor

Addressed in #197368

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
8.16 candidate Project:Serverless Work as part of the Serverless project for its initial release Project:Serverless-GA Team:Detection Engine Security Solution Detection Engine Area Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.
Projects
None yet
Development

No branches or pull requests

3 participants