How android/testing-samples works
Project type and purpose
• This is a mono-repository of Android testing sample apps. It demonstrates various automated testing frameworks and techniques (Espresso, UiAutomator, AndroidJUnitRunner, JUnit4 Rules, ServiceTestRule) and supports two build systems: Gradle (for local/IDE development) and Bazel (for CI headless testing).
• The README confirms the samples’ goal: show best practices for writing and running Android tests using AndroidX Test, Bazel, and continuous integration.
File‐structure analysis
• Top‐level:
• CI & build configs (.github/workflows, bazelci/, .bazelrc, WORKSPACE, BUILD.bazel, top‐level Gradle scripts)
• Directory groups:
– integration/ServiceTestRuleSample
– runner/AndroidJunitRunnerSample, AndroidTestOrchestratorSample…
– ui/espresso/… (many Espresso samples), ui/uiautomator/BasicSample, ui/PreviewScreenshot (Compose)
– unit/… (unit test samples in Kotlin/Java, native C++ sample)
• Each sample is a standalone Android app module: contains its own build.gradle or BUILD.bazel, src/main, src/androidTest, src/test, AndroidManifest, resources, Gradle wrapper.
• Patterns:
• Multi‐module monorepo with separation by testing category.
• Dual‐build‐system support (Gradle vs. Bazel) for flexibility between local and CI builds.
• Shared definitions: common_defs.bzl, projects.conf, top‐level build.gradle to coordinate dependencies.
Insights from README
• Confirms build commands:
• Gradle: ./gradlew assemble, connectedAndroidTest, test
• Bazel: bazel test //... --config=...
• Enumerates samples and testing frameworks.
• CI integration via GitHub Actions and Buildkite (bazelci).