docs(qa): QA-006 — the nine PRs nobody has looked at - #610
Merged
Conversation
Nine PRs shipped to production on 2026-09-11/12 and not one of the screens they changed has been opened by a person. The gap is structural, not an oversight: apps/mobile runs no component tests at all, a Tutor session needs an account with vocabulary plus a live LLM call, and the guest-merge warning needs a state that cannot be reached by clicking. Eight sections, each naming what the defect WAS so a tester knows what a pass looks like. Includes the two paths into the guest-merge warning (the reachable one is the expired token), and a section on what is deliberately out of scope with the reasoning, so nobody files a product decision as a bug. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011rgEMvYYi4Egj99dVtvm6E
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Nine PRs (#601–#609) shipped to production on 2026-09-11/12. Every one is covered by unit or integration tests, and not one of the screens they changed has been opened by a person.
That gap is structural, not an oversight, and the scenario says so up front:
apps/mobile/vitest.config.tsis narrowed tosrc/lib/**/*.test.ts— no component or screen test runs at all, so everything asserted about a mobile screen is an assertion about a projection function..envkey is stale, so it can only be exercised against production.What it covers
recallcard with four options is the defect this shipped to fixIt also states which JS you are actually testing: a dev build serves from Metro and does not receive the OTA, so testing "what a tester has" means installing build 26/27 and letting the
productionchannel update land — and §7 then behaves differently, because Sentry is enabled in a release build.And a short section on what is deliberately not covered, with the reasoning, so a product decision does not get filed as a bug: PDF-original progress,
LocatorKindon the catalog path, insight categories.🤖 Generated with Claude Code
https://claude.ai/code/session_011rgEMvYYi4Egj99dVtvm6E