android-qa-verification
This skill is used to verify Android features against acceptance criteria, catch regressions and define tests that reflect real device behaviour.
When & Why to Use This Skill
This Claude skill streamlines Android application quality assurance by transforming product acceptance criteria into comprehensive test plans. It specializes in identifying mobile-specific edge cases—such as lifecycle changes, process death, and configuration shifts—while providing actionable strategies for unit, instrumentation, and UI testing to ensure robust app performance and prevent regressions.
Use Cases
- Feature Validation: Converting product acceptance criteria into detailed test cases to ensure new features meet requirements on real devices and emulators.
- Edge Case Identification: Detecting and testing Android-specific scenarios like screen rotation, theme changes, process death, and app backgrounding/resuming.
- Regression Testing: Systematically verifying app behavior after new implementation work to catch bugs and ensure stability across different OS versions.
- Bug Reproduction & Fixing: Generating minimal, deterministic reproduction paths for reported issues and suggesting targeted fixes at the UI, ViewModel, or Repository layer.
- Migration Verification: Planning and validating database migrations to ensure data integrity is preserved when upgrading between app versions.
| name | android-qa-verification |
|---|---|
| description | This skill is used to verify Android features against acceptance criteria, catch regressions and define tests that reflect real device behaviour. |
Android QA and Verification Skill
Purpose
Ensure implemented Android features behave correctly, survive lifecycle changes and match acceptance criteria on real devices and emulators.
When to Use
Use this skill after implementation work or when bugs or regressions are suspected.
Outputs
- Behaviour-based test plan
- Unit, instrumentation and UI test ideas
- Edge-case scenarios
- Reproduction steps
- Focused fix suggestions
Procedure
- Take the acceptance criteria from product shaping and turn each into one or more test cases.
- Identify Android-specific edge conditions:
- Configuration changes (rotation, theme change).
- Process death and recreation.
- Timezone changes and daylight saving shifts if times are involved.
- App backgrounding and resuming.
- Plan tests at appropriate levels:
- Unit tests for repositories and ViewModels.
- Instrumentation or UI tests for flows through Composables and navigation.
- Manual test steps where automation is difficult (for example notifications).
- Validate migrations:
- Describe steps to upgrade from an old database version to the new one.
- Confirm existing data is preserved and new fields behave as expected.
- For each bug:
- Provide a minimal, deterministic reproduction path.
- Map the likely layer (UI, ViewModel, repository, database, platform integration).
- Suggest a targeted change, not a refactor.
Guardrails
- Do not propose architectural rewrites.
- Do not rely on brittle UI tests that mirror implementation details closely.
- Focus on user-visible behaviour, data integrity and stability across lifecycle events.