1k-app-upgrade-test_skill

Overview

This skill automates creating test release branches and hardcoded build configurations to validate app auto-update and version migration flows. It standardizes test version naming, computes a deterministic build number, and updates the minimal set of configuration files needed to produce test installs. Use it to generate repeatable QA builds that mimic production upgrades without affecting production artifacts.

How this skill works

You supply a test version following the 9XXX.YY.Z pattern (for example, 9005.20.0). The skill computes a 10-digit build number from the current date (YYYYMMDD00 + 30), creates a new Git branch, and updates four configuration files with the test version and calculated build number. Finally it commits and pushes the branch so CI or QA can build and install the test package for upgrade/migration checks.

When to use it

• When you need a repeatable test build to verify upgrade or migration flows
• Before QA runs upgrade scenarios between a production release and a test install
• To validate auto-update behavior in mobile CI pipelines
• When creating release candidates that must carry a known build number
• To reproduce version-specific bug reports in a controlled test channel

Best practices

• Follow the 9XXX.YY.Z naming convention so test versions clearly map to production versions
• Run the build-number calculation at branch creation time to avoid collisions across days
• Edit configuration files in the specified order (.env.version → shared action → workflow → android gradle) to keep CI outputs consistent
• Use a descriptive commit message like "chore: create test version <version>" and push the branch to origin for CI to pick up
• Keep test branches short-lived and document their purpose in the branch name or commit body

Example use cases

• Create 9005.20.0 to test an upgrade path from production 5.20.0 to a test build
• Generate a dated build number for QA to validate Android versionCode/versionName changes
• Reproduce a migration failure reported on a specific production version by using an exact test-version branch
• Run automated QA that installs the test APK from CI and verifies data migration logic after update