Repository navigation
test(spring-boot): [Sample Tests 24] Port the rest of the Boot 3 OTel agent sample's tests - #6316
Draft
runningcode wants to merge 3 commits into
Draft
runningcode wants to merge 3 commits into
runningcode wants to merge 3 commits into
Conversation
The agent fixture gains the Cache, Metrics, GraphQL and Kafka endpoints, and the agent suite ports the sample's remaining tests in both init modes. The agent traces each GraphQL operation as one span named after it, so the queries are named. Kafka uses an in-JVM KRaft broker that the test JVM starts next to the app. The sample has no system tests left, so it comes off the system-test runner, the backend workflow and the Spring Boot 3 matrix. The matrix no longer builds the agent separately, because the suites build the jar they attach. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This was referenced Oct 20, 2026
Draft
Draft
Draft
📲 Install BuildsAndroid
|
This was referenced Oct 20, 2026
Draft
This was referenced Oct 20, 2026
Draft
Draft
Draft
Draft
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…ee and creator ids 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
Ports the rest of
sentry-samples-spring-boot-jakarta-opentelemetry's tests into the agent suite from #6315. They run in both init modes:query GreetingQuery). So the queries are named. Errors are still tied to their transaction by trace ID.SpringKafkaintegration stays out, as in test(spring-boot): [Sample Tests 20] Move the Boot 3 OTel no-agent sample's tests #6312. The test JVM starts an in-JVM KRaft broker next to the app and passes its address to the app.With no system tests left, the sample comes off the runner, the backend workflow and the Spring Boot 3 matrix. The matrix no longer builds the agent separately, because the suites build the jar they attach. The sample's
bootRunWithAgenttask stays.Both agent tasks now run 25 tests each, about 132s per mode, and Gradle runs the two modes in parallel. As in #6315, the time comes from waiting for the agent's 5-second span batches.
After a coverage audit against the sample's tests:
assigneeIdandcreatorIdchecks from test(spring-boot): [Sample Tests 9] Move the Boot 3 GraphQL tests into the module #6295.💡 Motivation and Context
The Boot 3 agent flavor is now fully in the module, in both init modes. The sample's
auto-init=falserun was likely never running in CI, because itssystemTestrestored from cache.💚 How did you test it?
:sentry-spring-boot-jakarta:checkpasses, and the sample still builds.📝 Checklist
sendDefaultPIIis enabled.🔮 Next steps
The Boot 4 and Boot 2 OTel agent samples.
#skip-changelog
🤖 Generated with Claude Code