-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
System test for beat module, xpack code path #12646
System test for beat module, xpack code path #12646
Conversation
Co-Authored-By: Nicolas Ruflin <spam@ruflin.com>
Co-Authored-By: Nicolas Ruflin <spam@ruflin.com>
Co-Authored-By: Nicolas Ruflin <spam@ruflin.com>
Pinging @elastic/stack-monitoring |
I receive an error when attempting to test this per the instructions:
|
The full output also includes some Docker errors. I have included all of stdout and stderror below:
|
Apologies, @cachedout, I was missing some test steps in the PR description. I've added them now. Would you mind re-testing? |
Standby, @cachedout, there seems to be something else going on here. I'm not able to get my tests to pass consistently locally even with the updated steps. Let me investigate further. |
@cachedout Okay, I figured it out. Apparently there's a file called Sorry about the noise. This should be ready to test now. |
jenkins, test this |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can confirm that with the latest instructions this works as-intended and tests pass!
Similar to #12506 but for the
beat
module.This PR introduces a system test to exercise the xpack code path (
xpack.enabled: true
) of the Beat Metricbeat module.Testing this PR
Build and activate the virtual env for system tests.
Make sure
fields.yml
is present.Build the test binary.
Run the integration tests
Assert that there are no errors.