paperclip-bot/redis-gui-foundation
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
8d50243d36a91a1abb3bb4d7cb6369bcdfd02aef
redis-gui-foundation/plans/2026-03-28-frontend-smoke-validation.md
Senior Frontend Engineer 8d50243d36 feat(desktop): add redis gui foundation baseline 
Co-Authored-By: Paperclip <noreply@paperclip.ing>
2026-03-28 10:39:40 +00:00

1.8 KiB
Raw Blame History

Frontend Smoke Validation Snapshot

Date: 2026-03-28 UTC Owner: Senior Frontend Engineer Related issues: HAC-9, HAC-11, HAC-15

Goal

Revalidate the current desktop frontend and packaging path against the repository's shared smoke prerequisites.

Evidence Captured

  1. Passed: cargo test -p redis-core
  2. Passed: pnpm run desktop:build
  3. Passed: ./scripts/redis-fixture/start.sh
  4. Passed: ./scripts/redis-fixture/seed.sh
  5. Passed: ./scripts/redis-fixture/stop.sh
  6. Partial pass: pnpm run desktop:tauri:build

Artifact Evidence

  • target/release/bundle/deb/Redis GUI Foundation_0.1.0_amd64.deb
  • target/release/bundle/rpm/Redis GUI Foundation-0.1.0-1.x86_64.rpm

Packaging Outcome

  • Tauri build completed the Linux release binary and produced .deb and .rpm artifacts.
  • The same run failed in the AppImage step with io: Connection reset by peer (os error 104).

Remaining Gaps

  • No saved Tauri-window screenshots or interaction logs exist yet for live browse, edit, TTL, or command flows.
  • macOS and Windows package evidence remains absent.
  • AppImage packaging needs a separate rerun or targeted investigation if that bundle format is required.
  • This environment currently has no DISPLAY, xvfb-run, or desktop screenshot utility, so real-window visual evidence cannot be captured from this session alone.
  • The desktop shell now includes a copyable QA snapshot so smoke context can still be recorded as text when screenshots are unavailable.

Frontend Conclusion

The current repository is beyond shell-only validation: backend tests, browser build, Redis fixture bootstrapping, and Linux package generation all succeed in this environment. The next frontend validation step should happen in a launchable Tauri desktop session so QA can capture visual evidence for the live bridge workflows.