QA and evidence
QA reference pages preserve evidence exactly enough for reviewers to understand what passed, what was blocked, and what must be rerun before release decisions.
Evidence status labels
Section titled “Evidence status labels”- Pass rows are historical evidence from the recorded run date and command output.
- Blocked, pending hardware QA, and release-readiness follow-up rows are intentionally stale until rerun on current phone/TV/desktop hardware.
- Android and Android TV pages prioritize no-wipe recovery paths because data-wipe-class recovery failures are release blockers.
Android, TV, playback, and visual evidence
Section titled “Android, TV, playback, and visual evidence”| Page | Coverage |
|---|---|
| Playback auth regression QA | Server stream tickets, desktop GStreamer/MPV smoke, Android/TV auth-expiry units, and manual playback follow-up. |
| Android and Android TV final QA acceptance packet | Diagnostics, recovery, playback/watch-state, TV focus, codegen status, and redaction requirements. |
| Android library cache preflight | Recovery-first library cache substrate and reset expectations. |
| Android image pipeline preflight | Large-library artwork recovery, stale-ready behavior, selected-cache clear, and reset matrix. |
| Android playback QA matrix | Ticketed Media3 playback, watch progress, retry/recovery, and track selection matrix. |
| Android TV 10-foot QA matrix | D-pad, Back, focus restore, dense grid, recovery exits, and hardware runbook. |
| Android visual QA and accessibility runbook | Contrast/tag unit tests, screenshot runner, accessibility dumps, manual phone/TV paths, and redaction rules. |