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

Allow testing of specific filesets #10443

Merged
merged 2 commits into from
Jan 31, 2019

Conversation

ycombinator
Copy link
Contributor

Currently, Filebeat system tests can be filtered to run only on specific modules by specifying the TESTING_FILEBEAT_MODULES environment variable. This PR teaches the system tests to also understand an optional TESTING_FILEBEAT_FILESETS environment variable, that can be used to run system tests only on specific filesets.

@ycombinator ycombinator added review needs_backport PR is waiting to be backported to other branches. labels Jan 31, 2019
@ycombinator ycombinator merged commit 97eb460 into elastic:master Jan 31, 2019
@ycombinator ycombinator deleted the fb-test-filesets branch January 31, 2019 10:24
@ycombinator ycombinator removed the needs_backport PR is waiting to be backported to other branches. label Jan 31, 2019
ycombinator added a commit that referenced this pull request Feb 1, 2019
Cherry-pick of PR #10443 to 6.x branch. Original message: 

Currently, Filebeat system tests can be filtered to run only on specific modules by specifying the `TESTING_FILEBEAT_MODULES` environment variable. This PR teaches the system tests to also understand an optional `TESTING_FILEBEAT_FILESETS` environment variable, that can be used to run system tests only on specific filesets.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants