Skip to content

Conversation

@swiatekm
Copy link
Contributor

@swiatekm swiatekm commented Oct 22, 2025

What does this PR do?

Makes the remaining beats receiver integration tests install agent using the standard test fixture, rather than running the command directly.

Why is it important?

This way, the fixture takes care of stopping and uninstalling agent if the test fails, as well as collecting diagnostics.

Checklist

  • I have read and understood the pull request guidelines of this project.
  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • [ ] I have made corresponding changes to the documentation
  • [ ] I have made corresponding change to the default configuration files
  • [ ] I have added tests that prove my fix is effective or that my feature works
  • [ ] I have added an entry in ./changelog/fragments using the changelog tool
  • [ ] I have added an integration test or an E2E test

Related issues

This way, the tests generate diagnostics and ensure agent is not running
after test failure.
@swiatekm swiatekm requested a review from a team as a code owner October 22, 2025 16:35
@swiatekm swiatekm added Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team flaky-test Unstable or unreliable test cases. skip-changelog backport-8.19 Automated backport to the 8.19 branch labels Oct 22, 2025
@swiatekm swiatekm added backport-9.1 Automated backport to the 9.1 branch backport-9.2 Automated backport to the 9.2 branch labels Oct 22, 2025
@elasticmachine
Copy link
Collaborator

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

@elasticmachine
Copy link
Collaborator

elasticmachine commented Oct 22, 2025

💛 Build succeeded, but was flaky

Failed CI Steps

History

cc @swiatekm

@swiatekm swiatekm enabled auto-merge (squash) October 22, 2025 19:35
@swiatekm swiatekm merged commit 020adf8 into main Oct 22, 2025
34 checks passed
@swiatekm swiatekm deleted the test/improve-metrics-integration-test branch October 22, 2025 19:50
mergify bot pushed a commit that referenced this pull request Oct 22, 2025
This way, the tests generate diagnostics and ensure agent is not running
after test failure.

(cherry picked from commit 020adf8)
mergify bot pushed a commit that referenced this pull request Oct 22, 2025
This way, the tests generate diagnostics and ensure agent is not running
after test failure.

(cherry picked from commit 020adf8)
mergify bot pushed a commit that referenced this pull request Oct 22, 2025
This way, the tests generate diagnostics and ensure agent is not running
after test failure.

(cherry picked from commit 020adf8)

# Conflicts:
#	testing/integration/ess/beat_receivers_test.go
swiatekm added a commit that referenced this pull request Oct 23, 2025
…#10721)

This way, the tests generate diagnostics and ensure agent is not running
after test failure.

(cherry picked from commit 020adf8)

Co-authored-by: Mikołaj Świątek <mail@mikolajswiatek.com>
swiatekm added a commit that referenced this pull request Oct 23, 2025
…#10719)

This way, the tests generate diagnostics and ensure agent is not running
after test failure.

(cherry picked from commit 020adf8)

Co-authored-by: Mikołaj Świątek <mail@mikolajswiatek.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport-8.19 Automated backport to the 8.19 branch backport-9.1 Automated backport to the 9.1 branch backport-9.2 Automated backport to the 9.2 branch flaky-test Unstable or unreliable test cases. skip-changelog Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants