Android APK UI & Performance Testing
Budget: ₹1,500 – ₹12,500 INR
An internal Android APK needs a complete manual QA pass before it moves to the next release gate. The build is not yet in any store, so access will be shared privately once the engagement begins.
Scope
• Build structured, step-by-step test cases that cover core flows, edge conditions, error handling and user-level settings.
• Execute those cases across at least one real Android phone and, if available, an emulator to surface OS-level quirks.
• Focus on the visual layer first: layout consistency, touch targets, typography, dark/light mode behaviour and orientation changes.
• Probe performance: launch time, screen-to-screen latency, scrolling smoothness and memory spikes. Simple profiling via Android Studio, adb or similar is welcome but not mandatory—clear observations with evidence (screenshots, screen recordings, logs) take priority.
Deliverables
1. Test-case document (spreadsheet or TestRail export) that maps each user journey, expected result and actual outcome.
2. Bug reports in our Jira project (or a shared sheet if you do not have a Jira licence) including steps to reproduce, environment details, severity, supporting media and suggested fix notes when obvious.
3. A short summary highlighting any critical blockers or patterns noticed during the run.
Acceptance Criteria
• Every test case reproducible by another QA team member.
• No blocker or critical issue left undocumented.
• All media assets clearly labelled and linked back to the relevant ticket or row.
Timeline is flexible but an initial pass within three days of receiving the APK keeps us on track for the sprint review. I’ll be available on Slack for immediate clarifications throughout the test window.
Scope
• Build structured, step-by-step test cases that cover core flows, edge conditions, error handling and user-level settings.
• Execute those cases across at least one real Android phone and, if available, an emulator to surface OS-level quirks.
• Focus on the visual layer first: layout consistency, touch targets, typography, dark/light mode behaviour and orientation changes.
• Probe performance: launch time, screen-to-screen latency, scrolling smoothness and memory spikes. Simple profiling via Android Studio, adb or similar is welcome but not mandatory—clear observations with evidence (screenshots, screen recordings, logs) take priority.
Deliverables
1. Test-case document (spreadsheet or TestRail export) that maps each user journey, expected result and actual outcome.
2. Bug reports in our Jira project (or a shared sheet if you do not have a Jira licence) including steps to reproduce, environment details, severity, supporting media and suggested fix notes when obvious.
3. A short summary highlighting any critical blockers or patterns noticed during the run.
Acceptance Criteria
• Every test case reproducible by another QA team member.
• No blocker or critical issue left undocumented.
• All media assets clearly labelled and linked back to the relevant ticket or row.
Timeline is flexible but an initial pass within three days of receiving the APK keeps us on track for the sprint review. I’ll be available on Slack for immediate clarifications throughout the test window.