run-tests

name	run-tests
description	Run the project's test suites and interpret results. Use when asked to run tests, verify changes, check if tests pass, run unit tests, run lint, run instrumented tests, or validate a change. Covers unit tests (Robolectric), instrumented tests (Espresso), and lint checks with the correct Gradle commands and output locations.

Run Tests

Run unit tests, instrumented tests, or lint checks and interpret the results.

Test Suites

Unit tests (Robolectric — no emulator needed)

The primary test suite. Runs in-JVM using Robolectric to simulate Android APIs. This is the suite to run for most code changes.

./gradlew testAndroidDebugUnitTest

What it covers:

• Collection creation and coin counts (CollectionCreationTests)
• Database upgrades from all previous versions (CollectionUpgradeTests)
• Fixture-based upgrade tests covering all parameter configurations (CollectionUpgradeAllParamsTests)
• Targeted upgrade tests for SemiQ coins with non-default parameters (CollectionUpgradeSemiQParamTests)
• Database access patterns (DatabaseAccessTests)
• Export/import (CSV and JSON) (ExportImportTests, ExportImportJsonTests)
• Activity launch and lifecycle (LaunchCoinPageTests, MainActivityTests)
• Application initialization (MainApplicationTests)
• Collection page behavior (CollectionPageActivityTests)
• Collection creator parameter round-trips (CoinPageCreatorTests)
• Coin image ID correctness (CoinImageIdTests)

Also present: GenerateV23Fixtures is an @Ignore'd manual fixture generator — it does not run with the suite and is only run by hand when the V23 upgrade fixture files need regenerating.

Report location: app/build/reports/tests/testAndroidDebugUnitTest/index.html

Test results XML: app/build/test-results/testAndroidDebugUnitTest/

Lint

Static analysis for Android best practices, accessibility, performance, and correctness issues.

./gradlew lintAndroidDebug

Report location: app/build/reports/lint-results-androidDebug.html

Instrumented tests (requires running emulator)

On-device tests using Espresso and UIAutomator. Only needed when testing UI behavior that can't be covered by Robolectric.

./gradlew connectedAndroidTest

What it covers:

• Collection page views (basic and advanced) (CollectionPageBasicViewTests, CollectionPageAdvancedViewTests)
• Edit collection parameters (EditCollectionParametersTests)
• Export flow (ExportCollectionTests)
• Main activity UI (MainActivityTests)
• Parcelable serialization (ParcelableTests)
• Rename and reorder collections (RenameCollectionTests, ReorderCollectionsTests)
• Tutorial dialog display (TutorialDialogsTest)
• Screenshot generation (ScreenshotsUITest)

Prerequisites: A running Android emulator or connected device. Verify with adb devices.

Report location: app/build/reports/androidTests/connected/

When to Run Which Suite

Change type	Run
Collection class (add/edit coins, parameters)	Unit tests
Database migration	Unit tests
Export/import logic	Unit tests
Activity or Fragment code	Unit tests + Instrumented (if UI)
Layout XML changes	Instrumented tests
Build configuration	Unit tests + Lint
Any change before committing	Unit tests + Lint

Procedure

1. Run the appropriate suite

For most changes, start with unit tests:

./gradlew testAndroidDebugUnitTest

If tests pass and you want a full check:

./gradlew testAndroidDebugUnitTest && ./gradlew lintAndroidDebug

2. Interpret results

• BUILD SUCCESSFUL — All tests passed.
• BUILD FAILED — Check the terminal output for the failing test name and assertion message. The HTML report has detailed stack traces.
• Common failures:
  • CollectionCreationTests count mismatch → Expected coin counts need updating after adding/removing coins.
  • CollectionUpgradeTests failure → Database migration logic doesn't produce expected results.
  • ExportImportTests failure → Serialization format changed; update expected output.
  • Compilation error → Missing import, resource, or method.

3. Fix and re-run

After fixing a failure, re-run only the specific test class for faster feedback:

./gradlew testAndroidDebugUnitTest --tests "com.spencerpages.CollectionCreationTests"

Then run the full suite to confirm no regressions:

./gradlew testAndroidDebugUnitTest

Test Conventions

• Unit tests extend BaseTestCase
• Use SharedTest.COLLECTION_LIST_INFO_SCENARIOS for parametrized test data
• Use SharedTest.compareCollectionListInfos() and compareCoinSlots() for deep-equality assertions
• Default test variant is androidDebug (not amazonDebug)
• Two product flavors exist: android and amazon

Reference files

File	Purpose
app/src/test/java/com/spencerpages/	Unit test classes
app/src/androidTest/java/com/spencerpages/	Instrumented test classes
shared-test/src/main/java/com/spencerpages/SharedTest.java	Shared test data and comparison helpers
app/src/test/java/com/spencerpages/BaseTestCase.java	Unit test base class
app/src/androidTest/java/com/spencerpages/UITestHelper.java	Instrumented test utilities