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

[META] Increase test coverage for tests run during ./gradlew integTestRemote for release time tests against a Release Candidate #5090

Open
cwperks opened this issue Feb 5, 2025 · 0 comments
Labels
enhancement New feature or request untriaged Require the attention of the repository maintainers and may need to be prioritized

Comments

@cwperks
Copy link
Member

cwperks commented Feb 5, 2025

Is your feature request related to a problem?

The security plugin has a rich suite of integration tests in the integrationTest source set. The tests in this source set are run with every PR on the repo which gives a great deal of confidence that changes submitted do not cause any regressions or unintended side effects.

There is a problem that these tests are not run at release-time, they are only run as a PR check. At release time, the build team runs the scripts/integtest.sh which runs tests against a target remote cluster. In this case the remote cluster is a cluster running with a release candidate build.

Security runs very few tests with this task. Security applies a filter on org.opensearch.security.sanity.tests.*IT which matches very few tests

What solution would you like?

I'm filing a META issue to track increasing this coverage so that more scenarios are covered when testing against an RC build which includes all plugins in the default distribution.

@cwperks cwperks added enhancement New feature or request untriaged Require the attention of the repository maintainers and may need to be prioritized labels Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request untriaged Require the attention of the repository maintainers and may need to be prioritized
Projects
None yet
Development

No branches or pull requests

1 participant