Cherry-pick #17147 to 7.x: Add support for MODULE in mage goIntegTest for metricbeat #17409
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
) Add support for `MODULE` environment variable in `mage goIntegTest` for Metricbeat to run integration tests for an specific module. For example, to run integration tests for sql module only: MODULE=sql mage goIntegTest (cherry picked from commit 13592b0)
jsoriano
force-pushed
the
backport_17147_7.x
branch
from
3b99323 to
ad2e419
Compare
kaiyan-sheng
approved these changes
Apr 1, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 #17147 to 7.x branch. Original message:
What does this PR do?
Add support for
MODULEenvironment variable inmage goIntegTestfor Metricbeat to run integration tests for an specific module. For example, to run integration tests for sql module only:Why is it important?
Metricbeat integration tests are slow, running them as they are run in CI requires to run all tests, but when running them locally you are usually interested in running a single module.
Checklist
I 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
Use
MODULEenvironment variable to run integration tests of a single module, for example: