paperclip-bot/redis-gui-foundation
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
b6cbe5a47e1f9b0a2e416663a9d1b7a94171f942
redis-gui-foundation/docs/qa/verification-path-inventory.md
Senior Frontend Engineer b6cbe5a47e docs(project): refresh baseline verification artifacts 
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>
2026-03-31 10:15:39 +00:00

2.7 KiB
Raw Blame History

Verification Path Inventory

Date: 2026-03-31 Owner: QA Engineer

Goal

Pin down which startup, demo, seed, smoke, and Docker paths are actually reproducible in the current repository, and which ones remain blocked or undocumented.

Inventory

Path Entry Point Evidence On 2026-03-31 Current Status Gap
Browser demo startup pnpm run desktop:dev Vite served http://127.0.0.1:1420/; curl returned the shell HTML entrypoint Reproducible Demo-only path; not valid live Redis evidence
Browser production build pnpm run desktop:build Build passed and emitted apps/desktop/dist/ Reproducible Still frontend-shell evidence only
Linux desktop package build pnpm run desktop:tauri:build Build passed and produced .deb and .rpm under target/release/bundle/ Reproducible Does not prove install, launch, or workflow acceptance
Linux native app launch target/release/desktop-shell Launch failed with Failed to initialize GTK in a session with no DISPLAY, WAYLAND_DISPLAY, or xvfb-run Blocked by environment Needs GUI-capable session or virtual display tooling
Full Linux bundle path pnpm run desktop:tauri:build:all .deb and .rpm bundled, then AppImage failed with failed to run linuxdeploy Partially reproducible AppImage remains unverified
Seed fixture happy path ./scripts/redis-fixture/start.sh -> seed.sh -> redis-cli checks -> stop.sh Container started, 7 smoke:* keys seeded, types and TTL verified, cleanup succeeded Reproducible No GUI evidence attached to the live desktop workflow yet
Seed fixture failure path ./scripts/redis-fixture/seed.sh without a running container Script failed explicitly with Run scripts/redis-fixture/start.sh first. Reproducible Only one negative fixture path is documented so far
Local smoke runbook docs/qa/local-desktop-smoke.md Commands, fixture inputs, and expected keys align with current scripts and README Reproducible on the command line Still blocked from real-window smoke capture in this session
Docker support path Local Docker daemon + fixture scripts Docker daemon reachable and scripts work Reproducible No Dockerfile or compose asset exists; reproducibility depends on direct script usage

QA Readout

  • Startup paths are split cleanly between browser demo evidence and Tauri package evidence.
  • The seeded Docker fixture path is now reproducible on both success and one clear failure path.
  • The release-critical missing evidence is still real-window desktop smoke, not command-level buildability.
  • Docker support exists only as a QA fixture dependency, not as a packaged app runtime or compose-managed environment.