-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Security Solution] Restructure API integration tests based on their required license type #151877
Open
2 of 5 tasks
Tracked by
#153633
Labels
8.13 candidate
refactoring
Team:Detection Rule Management
Security Detection Rule Management Team
Team:Detections and Resp
Security Detection Response Team
Team: SecuritySolution
Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.
technical debt
Improvement of the software architecture and operational architecture
test
test-api-integration
Comments
xcrzx
added
technical debt
Improvement of the software architecture and operational architecture
Team:Detections and Resp
Security Detection Response Team
Team: SecuritySolution
Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.
Team:Detection Rule Management
Security Detection Rule Management Team
8.8 candidate
labels
Feb 22, 2023
Pinging @elastic/security-detections-response (Team:Detections and Resp) |
Pinging @elastic/security-solution (Team: SecuritySolution) |
3 tasks
banderror
changed the title
[Security Solution] Regroup integrational tests based on their required license type
[Security Solution] Regroup API integration tests based on their required license type
Mar 23, 2023
banderror
changed the title
[Security Solution] Regroup API integration tests based on their required license type
[Security Solution] Restructure API integration tests based on their required license type
Mar 23, 2023
banderror
added
test
refactoring
test-api-integration
and removed
test-coverage
issues & PRs for improving code test coverage
labels
Mar 24, 2023
yctercero
added a commit
that referenced
this issue
Mar 28, 2024
## Summary Begins work on #169185 and #151877 . Related to #151877 this PR: - Moves FTR tests under the `/alerts` folder that do not require Platinum license into the basics folder. Tests in `/alerts/trial_license_complete_tier` folder should now relate to functionality that requires the higher license tier. - Rearranged some of the folder structure so that it was clear what the intent of the tests is - Makes note of any issues in tickets that we will need to follow up on Related to #169185 this PR: - Ensures that tests are properly tagged for ESS & serverless - Ensures none of the tests that are critical contain the `@skipInQA` tag
This was referenced Mar 29, 2024
yctercero
added a commit
that referenced
this issue
Apr 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
8.13 candidate
refactoring
Team:Detection Rule Management
Security Detection Rule Management Team
Team:Detections and Resp
Security Detection Response Team
Team: SecuritySolution
Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.
technical debt
Improvement of the software architecture and operational architecture
test
test-api-integration
Summary
Currently, the integration tests in the Security Solution are divided into two groups based on the license type:
x-pack/test/detection_engine_api_integration/basic
- These tests are executed against a Kibana set-up with the Basic license.x-pack/test/detection_engine_api_integration/security_and_spaces
- These tests are executed against a Kibana set-up with the trial (Platinum) license.Most of the tests are included in the
security_and_spaces
group, but some tests are also copied to thebasic
group. There is no clear distinction between the two groups, so developers generally add tests to the second group by default.To improve the organization of the tests, we need to take the following actions:
basic
group (which should be the case for most Security Solution features).basic
group, and we should test that they work correctly in thesecurity_and_spaces
group.For reference, features by license: https://www.elastic.co/subscriptions
Detection Engine
Rule Management
The text was updated successfully, but these errors were encountered: