Skip to content

build: [Sample Tests 15] Add an integrationTests task that runs every module's suites - #6303

Closed
runningcode wants to merge 1 commit into
no/boot2-graphql-kafka-testfrom
no/integration-tests-aggregate
Closed

runningcode wants to merge 1 commit into
no/boot2-graphql-kafka-testfrom
no/integration-tests-aggregate

Conversation

@runningcode

@runningcode runningcode commented Oct 20, 2026 •

Copy link
Copy Markdown
Contributor

PR Stack (Sample Tests)


📜 Description

Adds a root integrationTests task that runs every module's integration test suites in one invocation:

Suite Tests
:sentry-spring-boot:integrationTest (Boot 2) 24
:sentry-spring-boot-jakarta:integrationTest (Boot 3) 29
:sentry-spring-boot-jakarta:integrationTestOtelAgent (Boot 3 with the agent) 2
:sentry-spring-boot-4:integrationTest (Boot 4) 25

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.parallel and 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 aren't part of any module's check; the Spring Boot matrices run them.

💡 Motivation and Context

This gives you one command, ./gradlew integrationTests, for every Spring Boot line's integration tests. Plain ./gradlew integrationTest already matches the three integrationTest tasks by name, but it misses the agent suite.

💚 How did you test it?

  • ./gradlew integrationTests --dry-run selects the four suites.
  • Ran all four with --rerun: 80 tests pass in 24.6s of wall time.
  • The test reports show the four suites starting within 0.5s of each other and overlapping. The tests finish within 15.3s, which is the agent suite's length. Run one after another, they'd take about 47s.

📝 Checklist

  • I added GH Issue ID & Linear ID
  • I added tests to verify the changes.
  • No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
  • I updated the docs if needed.
  • I updated the wizard if needed.
  • Review from the native team if needed.
  • No breaking change or entry added to the changelog.
  • No breaking change for hybrid SDKs or communicated to hybrid SDKs.
  • Public API changes reviewed by another Mobile SDK team member or implemented according to the develop docs spec.

🔮 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

@sentry

sentry Bot commented Oct 20, 2026 •

Copy link
Copy Markdown

📲 Install Builds

Android

🔗 App Name App ID Version Configuration
SDK Size io.sentry.tests.size 8.61.1 (1) release

⚙️ sentry-android Build Distribution Settings

This was referenced Oct 20, 2026
@runningcode
runningcode force-pushed the no/integration-tests-aggregate branch from cecf268 to d2cbac0 Compare October 21, 2026 09:19
@runningcode
runningcode force-pushed the no/boot2-graphql-kafka-test branch from 2f13c19 to 550a03b Compare October 21, 2026 11:27
@runningcode
runningcode force-pushed the no/integration-tests-aggregate branch from d2cbac0 to 0c845ff Compare October 21, 2026 11:27
@runningcode
runningcode force-pushed the no/boot2-graphql-kafka-test branch from 550a03b to b4d3cb3 Compare October 22, 2026 12:40
@runningcode
runningcode force-pushed the no/integration-tests-aggregate branch from 0c845ff to 545ef61 Compare October 22, 2026 12:40
@runningcode
runningcode force-pushed the no/boot2-graphql-kafka-test branch from b4d3cb3 to f67a837 Compare October 22, 2026 13:31
@runningcode
runningcode force-pushed the no/integration-tests-aggregate branch 2 times, most recently from 39df936 to ea995a8 Compare October 22, 2026 14:02
@runningcode
runningcode force-pushed the no/boot2-graphql-kafka-test branch from 13d3112 to c64319f Compare October 22, 2026 16:02
@runningcode
runningcode force-pushed the no/integration-tests-aggregate branch 2 times, most recently from 20cb23c to dc5d79e Compare October 23, 2026 08:24
@runningcode
runningcode force-pushed the no/boot2-graphql-kafka-test branch 2 times, most recently from be1b3a0 to f300bc7 Compare October 23, 2026 08:58
@runningcode
runningcode force-pushed the no/integration-tests-aggregate branch 2 times, most recently from 34f896b to 922c453 Compare October 23, 2026 09:35
@runningcode
runningcode force-pushed the no/boot2-graphql-kafka-test branch from 1681bc0 to a97923b Compare October 23, 2026 11:51
@runningcode
runningcode force-pushed the no/integration-tests-aggregate branch from 922c453 to 99c94c8 Compare October 23, 2026 11:51
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 aren't part of check; the Spring Boot matrices run them.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@runningcode
runningcode force-pushed the no/boot2-graphql-kafka-test branch from a97923b to d5312e0 Compare October 23, 2026 12:48
@runningcode
runningcode force-pushed the no/integration-tests-aggregate branch from 99c94c8 to c8fb997 Compare October 23, 2026 12:48
@runningcode

Copy link
Copy Markdown
Contributor Author

Dropped from the stack: the Spring Boot matrices run each suite, so a hand-maintained root task listing them isn't worth keeping in sync. #6306 now builds on #6300.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant