Repository navigation
build: [Sample Tests 15] Add an integrationTests task that runs every module's suites - #6303
Draft
runningcode wants to merge 2 commits into
Draft
runningcode wants to merge 2 commits into
runningcode wants to merge 2 commits into
Conversation
The Spring Boot 2, 3 and 4 integration suites live in separate modules, so they are separate tasks. integrationTests runs all of them, the jakarta agent suite included, in one invocation. Each suite starts its own servers on free ports, so Gradle runs them in parallel. The suites also stay part of check. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This was referenced Oct 20, 2026
📲 Install BuildsAndroid
|
This was referenced Oct 20, 2026
Draft
Draft
Draft
Draft
Draft
This was referenced Oct 20, 2026
Draft
Draft
Draft
Draft
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This branch has not been deployed
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
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.
PR Stack (Sample Tests)
main)📜 Description
Adds a root
integrationTeststask that runs every module's integration test suites in one invocation::sentry-spring-boot:integrationTest(Boot 2):sentry-spring-boot-jakarta:integrationTest(Boot 3):sentry-spring-boot-jakarta:integrationTestOtelAgent(Boot 3 with the agent):sentry-spring-boot-4:integrationTest(Boot 4)The suites live in separate modules, so they're separate tasks. Each one starts its own mock Sentry server, Spring app and Kafka broker on free ports, so they share nothing and Gradle (with
org.gradle.paralleland the configuration cache) runs them all at once.The tasks are listed explicitly rather than discovered, because the build uses configure-on-demand, and an explicit list also shows exactly what runs. New suites need adding here.
The suites also stay part of each module's
check.💡 Motivation and Context
This gives you one command,
./gradlew integrationTests, for every Spring Boot line's integration tests. Plain./gradlew integrationTestalready matches the threeintegrationTesttasks by name, but it misses the agent suite.💚 How did you test it?
./gradlew integrationTests --dry-runselects the four suites.--rerun: 80 tests pass in 24.6s of wall time.📝 Checklist
sendDefaultPIIis enabled.🔮 Next steps
Add new suites to the list as more samples move into modules: WebFlux, OTel without the agent, and the Boot 2 and 4 agent suites.
#skip-changelog