Check in the PM product requirements, refreshed QA acceptance evidence, shared execution split plans, and current-phase status notes so the repo matches the current delivery baseline. Co-Authored-By: Paperclip <noreply@paperclip.ing>
1.8 KiB
1.8 KiB
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.mddocs/qa/cross-platform-smoke-plan.mddocs/qa/test-strategy.mddocs/qa/defect-severity.mddocs/qa/release-readiness-checklist.md
Immediate QA Priorities
- Keep blocked acceptance items visible until product entrypoints exist.
- Require a reproducible seed or demo path before any feature is marked accepted.
- Require at least one smoke run per supported OS before release sign-off.
Known Blockers
pnpm run desktop:tauri:build:allstill fails in the AppImage stage withfailed to run linuxdeploy.- Linux
.deband.rpmbundles now exist, but macOS and Windows artifact evidence is still absent. - The local fixture and smoke runbook are reproducible, but saved Tauri-window smoke evidence is still missing.
- The current QA environment still has no GUI-capable
DISPLAY,WAYLAND_DISPLAY, orxvfb-run, so real-window screenshot capture is blocked in this session even though the desktop binary is built.
Alignment
- Product acceptance source:
HAC-2issue scope and completion comment remain the current acceptance baseline for connect, browse, search, edit, and command console flows. - CTO priority source:
HAC-15is now the high-priority owner for Tauri build, packaging, local smoke steps, and Redis fixture conventions. - QA baseline closure for this plan is now materially achieved on Linux through the shared docs and repeatable smoke path; broader product release sign-off remains downstream of
HAC-15, backend feature issuesHAC-5toHAC-7, and frontend feature issuesHAC-9toHAC-11.