Repository navigation
test(spring-boot): [Sample Tests 6] Move the Boot 3 Person test into the module - #6292
Draft
runningcode wants to merge 1 commit into
Draft
runningcode wants to merge 1 commit into
runningcode wants to merge 1 commit into
Conversation
Adds an integrationTest suite to sentry-spring-boot-jakarta that runs a Spring Boot app in the test's JVM against MockSentryServer, and ports the jakarta sample's PersonSystemTest to it: errors with feature flags, the server transaction and its spans, logs, the JDBC query span and the profile linked to the transaction. It is a suite of its own because the unit tests' classpath carries the OpenTelemetry agent, which switches Sentry into agent mode. Test classes share one application context and one server, so the app starts once per suite. The Spring Boot 3 matrix now runs both of the module's integration suites against every Boot version it covers. 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
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 an
integrationTestsuite tosentry-spring-boot-jakarta. It runs a Spring Boot app in the test's own JVM, sends Sentry data toMockSentryServer, and ports the jakarta sample'sPersonSystemTest:http.servertransaction and a span created through the Sentry API, each with its flag;@SentrySpanspan around the service method and thedb.queryspan for the insert (P6Spy over in-memory HSQLDB).profilerId.How the suite is set up:
IntegrationTeststarts one application context and oneMockSentryServerfor the whole suite.@DynamicPropertySourcepointssentry.dsnat the server. Tests match envelopes on values only they produce, because a late envelope can arrive after the server is reset.io.sentry.spring.boot.jakarta.integrationtest, so component scanning doesn't pick up the module's own auto-configuration classes.integrationTestOtelAgenton every Boot version it covers. Both suites are also part ofcheckfor now.The sample's
PersonSystemTestis deleted. Its other system tests stay until they're ported.💡 Motivation and Context
This is the pilot for moving the Spring Boot sample tests into their modules. The sample's Person test needed the Python runner, a packaged app and the mock server, and its waits sleep 10s at a time. In-module, the whole class runs in about 3s, Spring startup included, with each test taking 30–470ms. The remaining Boot 3 sample tests follow in the next PRs; after that, the suite's CI cost settles whether these suites stay in
check.💚 How did you test it?
:sentry-spring-boot-jakarta:checkpasses.📝 Checklist
sendDefaultPIIis enabled.🔮 Next steps
Port the rest of the jakarta sample's tests into this suite:
EmbeddedKafka#skip-changelog