redis-gui-foundation/plans/2026-03-27-qa-acceptance-baseline.md

QA Acceptance Baseline Plan

Date: 2026-03-27 Owner: QA Engineer

Objective

Create the first acceptance matrix and cross-platform smoke plan for Redis GUI V1, based only on repository evidence.

Outputs

• docs/qa/acceptance-matrix.md
• docs/qa/cross-platform-smoke-plan.md
• docs/qa/test-strategy.md
• docs/qa/defect-severity.md
• docs/qa/release-readiness-checklist.md

Immediate QA Priorities

1. Keep blocked acceptance items visible until product entrypoints exist.
2. Require a reproducible seed or demo path before any feature is marked accepted.
3. Require at least one smoke run per supported OS before release sign-off.

Known Blockers

• npm run desktop:tauri:build currently fails because its pre-build command targets a non-existent parent build script.
• Repository does not yet contain Docker, demo, or seed assets.
• Current automated coverage is limited to foundation-model tests in crates/redis-core.
• Completed issue comments for HAC-2 and HAC-8 reference shared files that are absent from the current workspace, so QA cannot inspect those artifacts locally.
• Existing Rust test artifacts in target/ are stale relative to current source, so backend baseline verification needs a fresh cargo test rerun.

Alignment

• Product acceptance source: HAC-2 issue scope and completion comment remain the current acceptance baseline for connect, browse, search, edit, and command console flows.
• CTO priority source: HAC-15 is now the high-priority owner for Tauri build, packaging, local smoke steps, and Redis fixture conventions.
• QA closure for this plan remains downstream of HAC-15, backend feature issues HAC-5 to HAC-7, and frontend feature issues HAC-9 to HAC-11.