Cherry-pick #17075 to 7.x: Add support of TEST_TAGS in python tests #17122
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cherry-pick of PR #17075 to 7.x branch. Original message:
What does this PR do?
Add a
tag(tag)
decorator that skips a test if the tag is not includedin the comma-separated list of
TEST_TAGS
environment variable.This offers an initial support for the similar implementation added for
mage in #16937.
Why is it important?
#16937 was intended for cloud tests, where we only have go-based
integration tests. But we have found similar needings in some services
like oracle, where we need an image that we cannot distribute. In that
case we need a similar approach to run the test only in our Jenkins
instances, where the image is available.
Checklist
I have made corresponding changes to the documentationI have made corresponding change to the default configuration filesI have added tests that prove my fix is effective or that my feature worksHow to test this PR locally
@metricbeat.tag('sometag')
.TEST_TAGS
is not used.TEST_TAGS
environment variable includessometag
(e.g:TEST_TAGS=sometag
orTEST_TAGS=sometag,foo
.Related issues
Use cases