[8.18] (backport #8691) feat: singleTest mage target for each integration test package #8788
Conversation
This file contains hidden or 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
* feat: support running a single test for serverless and resource leak integration tests * doc: update test-framework-dev-guide.md to include the latest mage targets (cherry picked from commit 2ec9992)
mergify
bot
requested review from
michalpristas and
ycombinator
and removed request for
a team
8 tasks
github-actions
bot
added
Team:Elastic-Agent-Control-Plane
|
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
|
💛 Build succeeded, but was flaky
Failed CI StepsHistory |
pkoutsovasilis
approved these changes
Jul 2, 2025
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.
What does this PR do?
As request in previous PR reviews this PR introduces
Singlemage targets for theserverlessandleakintegration test packages, similar to the existingTestKubernetesSingletarget. It adds the following functions to themagefile.go:TestServerlessSingleTestForResourceLeaksSingleInternally, both new targets delegate to shared helper functions that support selecting a specific test by name. This unifies the way we run individual integration tests across packages and prepares the mage targets for further package splits.
Why is it important?
As part of the effort to split the increasingly large integration test suite into smaller dedicated packages (see parent issue), we also need to ensure that developers can run individual tests from each new package using a consistent interface.
Checklist
./changelog/fragmentsusing the changelog toolDisruptive User Impact
None. This PR only introduces new mage targets for developer convenience without affecting existing workflows.
How to test this PR locally
Invoke the new mage targets 🙂
Related issues
This is an automatic backport of pull request #8691 done by [Mergify](https://mergify.com).