feat(desktop): add redis gui foundation baseline
Co-Authored-By: Paperclip <noreply@paperclip.ing>
This commit is contained in:
35
docs/qa/release-readiness-checklist.md
Normal file
35
docs/qa/release-readiness-checklist.md
Normal file
@@ -0,0 +1,35 @@
|
||||
# Release Readiness Checklist
|
||||
|
||||
Date: 2026-03-27
|
||||
Owner: QA Engineer
|
||||
|
||||
## Must Be True Before Redis GUI V1 Can Ship
|
||||
|
||||
- A documented build or package path exists for Linux, macOS, and Windows.
|
||||
- Smoke steps are executable and repeatable by someone other than the original implementer.
|
||||
- Seed data or demo environment is documented and reproducible.
|
||||
- Core workflows have explicit pass evidence:
|
||||
- connection management
|
||||
- key browsing
|
||||
- search
|
||||
- value editing
|
||||
- TTL operations
|
||||
- command console
|
||||
- dangerous operation confirmation
|
||||
- Known release blockers are triaged with owner and severity.
|
||||
- Installer or portable package basic install, launch, and uninstall checks are complete.
|
||||
|
||||
## Current Release Blockers On 2026-03-27
|
||||
|
||||
- Blocked: Linux package artifact evidence now exists for `.deb` and `.rpm`, but AppImage is still unverified and there is no validated artifact evidence yet for macOS or Windows.
|
||||
- Blocked: a repeatable Docker-backed seed and smoke path now exists, but no completed smoke evidence set has been captured from it yet.
|
||||
- Blocked: release artifact naming now exists in produced Linux packages, but install and uninstall verification is still not documented with saved evidence.
|
||||
- Blocked: the desktop app is not yet validated end-to-end against a seeded Redis path; browse, edit, and TTL controls are inspectable, but broader workflow evidence remains incomplete.
|
||||
- Blocked: desktop runtime smoke evidence inside the real Tauri window is still pending even though current `redis-core` Rust test evidence and Linux package artifacts are reproducible from the present tree.
|
||||
|
||||
## Minimum Sign-Off Evidence
|
||||
|
||||
- Test run log with date, platform, build id, and tester.
|
||||
- Screenshots or terminal evidence for each smoke step.
|
||||
- Defect list with severity and explicit disposition.
|
||||
- Final QA judgment: pass, fail, blocked, or pass with waiver.
|
||||
Reference in New Issue
Block a user