Quality checks before ToolsBing becomes stable.
This page gives the launch team a simple way to verify the product before release: important pages, user journeys, accessibility, technical safety, and recovery paths.
Ready for QA review Needs manual browser check
Release QA checklist
Use this as the minimum review before pushing a new build to production.
Core pages load
- Home page opens without PHP warnings.
- Start, Search, Conversation, Assistant, Dashboard, Trust, and Error Help pages open.
- Header, footer, mobile navigation, and floating assistant render consistently.
User journeys work
- A first-time user can describe a problem and reach a useful next step.
- Search by problem returns relevant tools or clear recovery paths.
- Tool pages explain the result, confidence, next action, and recommendations.
Mobile and accessibility
- Primary actions are reachable with one thumb on mobile.
- Keyboard users can tab through navigation, forms, assistant, and tool actions.
- Focus states, labels, skip links, and reduced-motion preferences remain intact.
Technical safety
- Canonical, robots, sitemap, and metadata output correctly.
- Security headers and sensitive-file blocking remain active.
- Error pages help users recover instead of reaching a dead end.
Tracking and privacy
- Analytics events fire for broad product actions only.
- Private form answers are not required for event tracking.
- Opt-out and privacy language remain visible where needed.
Smoke-test routes
Open these routes manually after deployment and confirm each one works on desktop and mobile.
HomeStart with one clear problem-to-action path.Open test route →StartBeginner-safe starting choices.Open test route →Search by ProblemProblem language search and recovery guidance.Open test route →ConversationGuided prompt and recommended route.Open test route →Next ActionSingle-action guidance.Open test route →Results ExperienceSummary, meaning, confidence, and next action pattern.Open test route →AssistantAssistant entry points and context paths.Open test route →DashboardSaved items, recent actions, and progress cues.Open test route →AccessibilityAccessibility information and support commitments.Open test route →Error RecoveryFriendly recovery choices.Open test route →
Manual QA rule
Do not release only because PHP lint passes.
PHP lint confirms files parse correctly. It does not confirm the user journey is clear, buttons work, analytics fires, or mobile screens feel easy.