Launch QA
Verification RequiredMake final QA explicit.
DOCS-090 records the launch QA coverage model for navigation, search, links, code blocks, accessibility, responsive behavior, build output, and browser evidence. It separates P0/P1 launch blockers from accepted P2/P3 risks and keeps full-route smoke expansion in DOCS-100.
QA Summary
- QA lanes
- 8
- P0/P1 blockers
- 0 recorded
- Accepted risks
- 4
- Deferred PR evidence
- Playwright run
QA Lanes
| Area | Required evidence | Current signal | Disposition |
|---|---|---|---|
| Navigation and IA | Header, footer, product navigation, breadcrumbs, in-page anchors, and roadmap paths stay reachable without source-only links. | Source review and link validation cover public route reachability; existing browser automation covers home, roadmap, page actions, mobile navigation, and product rails. | Ready for launch review. No P0 or P1 navigation blocker is recorded. |
| Search and discovery | Search query behavior, product facets, content-type facets, maturity filters, and new launch-review routes stay discoverable. | Search index entries cover roadmap reviews, products, status, legal, support, limits, guides, references, and route keywords. | Ready for launch review. DOCS-091 owns post-launch failed-search triage. |
| Links and routes | Internal Markdown, Gatsby route, navigation, anchor, sitemap, and generated manifest links pass release validation. | `validate:links`, `validate:links:strict`, `validate:seo-crawl`, and `validate:llms` provide source-side route and manifest evidence. | Ready for launch review. Unapproved external failures remain blockers under DOCS-099. |
| Code blocks and examples | Commands, snippets, expected outputs, tutorial smoke rationale, and example manifests remain copy-safe and evidence-backed. | `validate:snippets`, `validate:examples`, `validate:tutorial-smoke`, and the existing CodeExamples browser page cover the current model. | Ready for launch review. Product-behavior changes still require product SME and docs QA acceptance. |
| Accessibility | Skip links, headings, landmarks, keyboard paths, table semantics, labels, and link names stay usable on representative routes. | Existing AccessibilityPerformance browser coverage exercises shared shell behavior across Chromium, Firefox, and WebKit. | Ready for launch review after the required Playwright suite is run for final launch evidence. |
| Responsive behavior | Mobile, tablet, and desktop layouts avoid horizontal overflow, overlapping controls, and hidden active navigation. | Existing browser coverage checks representative mobile and desktop viewports, product rails, and route load budgets. | Ready with accepted limitations. DOCS-100 remains the full-route smoke expansion. |
| Privacy, support, and feedback | Public footer, privacy, terms, support, hidden feedback controls, and analytics-disabled posture remain customer-safe. | DOCS-092, DOCS-096, and DOCS-097 supply implementation evidence; `validate:analytics-privacy`, public footer automation, and feedback intake automation cover regression risk. | Ready for launch review. Inline page rating controls remain gated separately from the public feedback intake route. |
| Build and public assets | Gatsby build, local metadata assets, sitemap, robots, favicon metadata, social previews, and LLM exports stay current. | `npm run build`, `validate:external-assets`, `validate:seo-crawl`, `validate:llms`, and DOCS-101 cover source, generated asset, CDN, DNS, cache-header, invalidation, and rollback evidence. | Ready for launch review. Final environment samples and owner signoff remain DOCS-104 go/no-go evidence. |
Validation Gates
| Gate | Evidence | PR status | Launch rule |
|---|---|---|---|
| Claims | `npm run validate:claim-lint` | Required for this PR. | P0/P1 if risky launch claims remain unbounded. |
| Metadata | `npm run validate:docs-metadata` | Required for this PR. | P1 if publishable docs lack required owner, audience, maturity, or review metadata. |
| Links | `npm run validate:links` and `npm run validate:links:strict` | Required for this PR. | P1 if internal routes fail or unapproved external blockers remain. |
| Search, SEO, and machine-readable assets | `npm run validate:seo-crawl` and `npm run validate:llms` | Required for this PR. | P1 if public route manifests omit launch-critical pages. |
| Examples, snippets, references, tutorials, and compatibility | `npm run validate:examples`, `npm run validate:snippets`, `npm run validate:reference-schema`, `npm run validate:tutorial-smoke`, and `npm run validate:compatibility-matrix` | Required for this PR when feasible. | P1 if runnable or reference content would mislead a reader. |
| Release docs, privacy, and assets | `npm run validate:release-docs`, `npm run validate:analytics-privacy`, and `npm run validate:external-assets` | Required for this PR when touched or launch-significant. | P1 if release, privacy, support, or asset fallback posture regresses. |
| Static build | `npm run build` | Required for this PR. | P0 if the site cannot build. |
| Browser QA | `DOCS_SITE_BASE_URL=http://localhost:8002 dotnet test Automation/Stornamics.DocsWebsite.Automation.sln --nologo` | Skipped for this PR by reviewer direction on August 27, 2026; still required before final launch signoff. | P1 if representative browser coverage fails on an approved docs URL. |
Browser And Device Expectations
| Surface | Required coverage | Current coverage | Follow-up |
|---|---|---|---|
| Desktop browsers | Chromium, Firefox, and WebKit render representative entry, search, status, roadmap, support, legal, and product routes. | The .NET Playwright suite declares Chromium, Firefox, and WebKit theory rows for representative pages. | Run the suite before final launch signoff and whenever reviewer skip guidance expires. |
| Mobile viewport | Narrow layouts keep the menu keyboard path, active product rail, in-page anchors, tables, and forms usable. | Existing accessibility and performance coverage checks 390px mobile behavior for shared shell, product navigation, and overflow. | DOCS-100 expands from representative routes to release-candidate route inventory. |
| Tablet and mid-width | Navigation, tables, cards, search controls, and code blocks stay readable between mobile and desktop breakpoints. | Source review keeps tables inside scroll wrappers and shared layouts responsive; no dedicated tablet-only automation is required for DOCS-090. | Track tablet-only polish as P2 unless it hides core route content or a primary action. |
| Generated static site | Built HTML, generated assets, route manifests, and static metadata match the launch source state. | Gatsby build plus SEO, sitemap, robots, favicon, LLM export validation, and DOCS-101 provide static-site and production cutover evidence paths. | Capture the final environment samples in DOCS-104. |
Accepted Risks
| Severity | Risk | Owner | Disposition |
|---|---|---|---|
| P2 | The required Playwright suite is skipped for this PR by explicit reviewer direction. | docs QA reviewer | Accepted for PR validation only. It must pass before final launch signoff on local, docs-dev, docs-tst, or production docs. |
| P2 | Representative browser coverage exists, but full-route release-candidate smoke coverage remains incomplete. | docs QA reviewer | Accepted only with DOCS-100 open. Escalate to P1 if a core route lacks any launch validation path. |
| P2 | Inline page feedback controls remain hidden while the public feedback route handles approved intake. | support, privacy, and docs platform | Accepted under DOCS-092 and DOCS-105. The feedback route, support, issue templates, search signals, and page-health data remain the launch signals. |
| P3 | Optional visual asset polish can lag behind text-first launch readiness. | docs platform | Accepted when text, labels, local fallbacks, and remote image fallback behavior keep pages understandable. |
Blocking Rules
| Severity | Blocks launch? | Condition | Required action |
|---|---|---|---|
| P0 | Yes | The site cannot build, primary navigation is absent, public docs expose private systems or credentials, or automation cannot target an approved docs URL. | Fix before launch review continues and rerun build, link, metadata, SEO, LLM, and browser validation. |
| P1 | Yes | A product hub, quickstart, core reference, search path, status page, legal/support surface, or known-limits link materially misleads or strands a reader. | Fix, remove, relabel, or secure owner acceptance before launch foundation. |
| P2 | No, if tracked | A secondary route has copy, layout, optional visual, or non-critical viewport polish that does not hide core content or strengthen claims. | Record owner, target date, and accepted launch posture. |
Remaining Owner Work
| Work item | Owner | Disposition |
|---|---|---|
| DOCS-091 | support and docs | Available. Use the post-launch triage plan for support reports, issue templates, failed searches, broken journeys, stale pages, severity, and response expectations. |
| DOCS-092 | support, privacy, and docs platform | Available. Keep the public feedback route in footer/support navigation and keep inline page rating controls gated until separately approved. |
| DOCS-101 | release, platform, operations, security, and docs leads | Available. Use the production CDN, DNS, cache, invalidation, rollback, owner, and go/no-go runbook before final launch acceptance. |
| DOCS-102 | release, platform, security, legal, and docs leads | Available. Use the dependency, license, vulnerability, private-feed, owner-decision, and remediation audit before final launch acceptance. |
| DOCS-115 | docs platform, security, legal, QA, and release | Available. Use the Gatsby dependency remediation record and clean npm audit evidence; final launch still needs private-feed, install-script, license, and validation acceptance. |
| DOCS-103 through DOCS-104 | release, platform, operations, security, and docs leads | Close observability and final launch acceptance evidence. |