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>
36 lines
1.8 KiB
Markdown
36 lines
1.8 KiB
Markdown
# 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
|
|
|
|
- `pnpm run desktop:tauri:build:all` still fails in the AppImage stage with `failed to run linuxdeploy`.
|
|
- Linux `.deb` and `.rpm` bundles 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`, or `xvfb-run`, so real-window screenshot capture is blocked in this session even though the desktop binary is built.
|
|
|
|
## 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 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 issues `HAC-5` to `HAC-7`, and frontend feature issues `HAC-9` to `HAC-11`.
|