Skip to content

build(samples): [Sample Tests 46] Move the Android integration tests to their own build - #6393

Merged
runningcode merged 8 commits into
no/android-sample-own-buildfrom
no/android-integration-tests-own-build
Nov 6, 2026
Merged

runningcode merged 8 commits into
no/android-sample-own-buildfrom
no/android-integration-tests-own-build

Conversation

@runningcode

@runningcode runningcode commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor

PR Stack (Sample Tests)


📜 Description

Here's a diagram of what this build pulls out made by my clanker:

sentry_android_integration_tests_build_6393

So basically sentry-uitest-android, sentry-uitest-android-critical and test-app-size are now standalone Gradle builds in sentry-android-integration-tests. They depend on io.sentry:*, which Gradle substitutes with the SDK's projects, including the unpublished sentry-test-support.

💡 Motivation and Context

Part of the Linear project "Separate sample projects and tests from build." (JAVA-626): untie the SDK build from the versions used to test.

💚 How did you test it?

Tests pass

📝 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

#6394 moves the JVM samples to their own build.

#skip-changelog

🤖 Generated with Claude Code

@sentry

sentry Bot commented Oct 27, 2026 •

Copy link
Copy Markdown

📲 Install Builds

Android

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

⚙️ sentry-android Build Distribution Settings

@runningcode
runningcode force-pushed the no/android-sample-own-build branch from f28da1f to 63b12f6 Compare October 27, 2026 14:33
@runningcode
runningcode force-pushed the no/android-integration-tests-own-build branch from 04f1683 to 7771435 Compare October 27, 2026 14:33
@runningcode runningcode changed the title build(samples): [Sample Tests 46] Move the Android integration tests to their own build build(samples): [Sample Tests 47] Move the Android integration tests to their own build Oct 27, 2026
@runningcode
runningcode force-pushed the no/android-sample-own-build branch from 63b12f6 to e4a9b5a Compare October 27, 2026 15:08
@runningcode
runningcode force-pushed the no/android-integration-tests-own-build branch from 7771435 to 76332ce Compare October 27, 2026 15:08
@runningcode
runningcode force-pushed the no/android-sample-own-build branch from e4a9b5a to c44fa03 Compare October 28, 2026 10:09
@runningcode
runningcode force-pushed the no/android-integration-tests-own-build branch from 76332ce to 77bdde5 Compare October 28, 2026 10:09
@runningcode
runningcode force-pushed the no/android-sample-own-build branch from c44fa03 to b454372 Compare October 28, 2026 10:38
@runningcode
runningcode force-pushed the no/android-integration-tests-own-build branch from 77bdde5 to 12d5c7c Compare October 28, 2026 10:38
@runningcode runningcode changed the title build(samples): [Sample Tests 47] Move the Android integration tests to their own build build(samples): [Sample Tests 46] Move the Android integration tests to their own build Oct 28, 2026
@runningcode
runningcode force-pushed the no/android-integration-tests-own-build branch from 12d5c7c to 0ec48f1 Compare October 28, 2026 16:32
@runningcode
runningcode force-pushed the no/android-sample-own-build branch from b454372 to 0da6737 Compare October 28, 2026 16:32
@runningcode
runningcode force-pushed the no/android-sample-own-build branch from 1992d3b to d5f25ea Compare November 5, 2026 16:06
@runningcode
runningcode force-pushed the no/android-integration-tests-own-build branch 3 times, most recently from ebe1d63 to 356db6c Compare November 5, 2026 17:16
@runningcode
runningcode marked this pull request as ready for review November 5, 2026 17:21
@runningcode
runningcode requested review from a team and adinauer as code owners November 5, 2026 17:21
@runningcode
runningcode requested review from markushi and removed request for a team November 5, 2026 17:21
@runningcode runningcode added sanity-check PR needs a lightweight review for obvious issues ship-it PR is ready to merge from a reviewer perspective and removed sanity-check PR needs a lightweight review for obvious issues labels Nov 5, 2026
@runningcode
runningcode force-pushed the no/android-integration-tests-own-build branch from 356db6c to 9d8ac7b Compare November 5, 2026 17:32
runningcode and others added 8 commits November 5, 2026 18:34
sentry-uitest-android, sentry-uitest-android-critical and test-app-size
are now a standalone Gradle build that includes the SDK build, like the
Android sample. They depend on io.sentry:* coordinates, which Gradle
substitutes with the SDK's projects, including the unpublished
sentry-test-support. The SDK build doesn't include them back, so SAGP,
errorprone's uitest checks and their AndroidX test dependencies no longer
load in the SDK build.

AGP stays shared: a composite build can only use one AGP version, so the
AGP matrix job's VERSION_AGP still applies to both builds.

Root check and spotlessApply no longer reach these apps, so preMerge runs
this build's check, which covers what the root check ran for them: lint,
detekt and spotless. The format workflow runs its spotlessApply, and the
AGP matrix, UI test and size workflows call it with -p. APK paths don't
change.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…workflow

Adds the integration tests build to the Samples workflow's matrix instead
of a `make preMerge` target.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
With the Android sample and integration tests in their own builds, no
project in the SDK build applies the Sentry Android Gradle Plugin. The
root no longer declares it or looks it up in mavenLocal when useSagp is
set; those builds declare it and handle useSagp themselves.

The root keeps the AGP declaration: the SDK's Android modules apply
com.android.library without a version and get AGP from it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…uild's

gradle.properties, gradlew, gradle/wrapper and
gradle/gradle-daemon-jvm.properties are now symlinks to the SDK build's
files, as in the Android sample. The copied gradle.properties had drifted
from the root one (-Xmx6g and CrashOnOutOfMemoryError), and the build had
no wrapper or daemon JDK pin. The SDK version now comes from the shared
versionName property instead of parsing the root file.

The root drops android.experimental.lint.version. It equals the lint
bundled with AGP 9.4.0, so it changes nothing for the SDK build, and
sentry-uitest-android's warningsAsErrors fails on it once the integration
tests share the root gradle.properties.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Adding or removing a project then changes only its own line.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… versions current

The integration tests' settings use the root build's Develocity plugin
version, and Dependabot also scans their build, as it does the Android
sample's.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ettings

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@runningcode
runningcode force-pushed the no/android-integration-tests-own-build branch from 9d8ac7b to 27ec18e Compare November 5, 2026 17:35
@runningcode
runningcode merged commit f9a4d8d into no/android-sample-own-build Nov 6, 2026
41 checks passed
@runningcode
runningcode deleted the no/android-integration-tests-own-build branch November 6, 2026 14:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ship-it PR is ready to merge from a reviewer perspective

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants