B2BEA.org Rebuild qa-baseline-spec

Full legacy body rendered for humans

B2BEA.org V1 QA Baseline Spec

Source of record: RedKey local project artifact draft.

• Project: B2BEA.org Rebuild
• Project ID: a820dd0c-6cef-4133-bfbd-d802fd806e44
• Artifact: qa-baseline-spec
• Version: 1
• Status: draft
• Generated: 2026-05-08

Purpose

Define the minimum QA baseline every implementation slice must satisfy before being treated as complete.

Release Gate Decision

Use all three release gates for launch-critical slices:

1. Automated tests

2. Desktop/mobile screenshots

3. Manual QA checklist

No launch-critical slice may rely on screenshots alone or manual QA alone.

Required Automated Tests

| area | required_tests |

| --- | --- |

| route registry | public/private classification, redirects, custom markers, sitemap inclusion/exclusion |

| metadata | required fields by page family, private noindex, slug redirect requirement |

| authorization | denied/allowed decisions for anonymous, member, vendor, company, admin |

| ownership | users cannot read/write another vendor/company/member scope |

| design system | tokens, core components, page title scale, field/button/card contracts |

| publishing | draft/preview/scheduled/published/archived visibility |

| exports | authorization, scope, audit event, expiration |

| forms/surveys | validation, submission state, duplicate/update policy |

Screenshot Baseline

Minimum viewport set:

• desktop: 1440x1000
• tablet: 834x1112
• mobile: 390x844

Minimum route set for Slice 0:

• /
• /login
• /admin
• /member
• /vendor
• /company
• /access-denied

Minimum route families before launch:

• home/custom
• standard marketing page
• editorial index
• editorial detail
• resource index
• resource detail/download gate
• directory index
• vendor profile detail
• event index/detail
• job board/detail
• course catalog/detail
• auth/account utility
• admin table/detail/review
• member dashboard/profile
• vendor dashboard/profile editor
• company dashboard/roster
• maturity assessment flow

Visual QA Rules

Screenshots fail if:

• horizontal overflow appears
• text overlaps controls or adjacent content
• mobile nav traps or hides content
• button/control text does not fit
• cards nest inside decorative cards
• admin/portal pages use oversized marketing heroes
• private routes expose public navigation incorrectly
• loading/empty/error states are unstyled

Manual Checklist

Every launch slice must record:

• routes tested
• roles tested
• browsers/viewports tested
• known issues
• unresolved risks
• deploy target
• rollback path

Acceptance Criteria

• QA baseline is concrete enough to automate in Slice 0.
• Representative routes exist for every page family before launch.
• Visual QA checks directly reflect design-system and surface-spec rules.
• Manual release checklist is required only as final evidence, not a substitute for tests.