Files
redis-gui-foundation/docs/qa/cross-platform-smoke-plan.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

2.6 KiB

Cross-Platform Smoke Plan

Date: 2026-03-27 Owner: QA Engineer

Goal

Provide one minimal but repeatable smoke flow for Windows, macOS, and Linux that proves a release candidate is installable, launchable, connectable to Redis, and safe around destructive actions.

Preconditions Required Before Smoke Can Run

  • A documented build command or signed artifact exists for each target OS.
  • A seedable Redis dataset exists with strings, hashes, lists, sets, sorted sets, JSON or binary payload samples if supported, and keys with TTL.
  • A documented demo or local startup path exists.
  • Smoke environment variables, sample credentials, and cleanup steps are documented.

Minimal Smoke Flow Per Platform

  1. Install or launch the app from the documented artifact or dev command.
  2. Verify window renders and version or build identity is visible.
  3. Add a connection to the seeded Redis instance and reconnect once.
  4. Browse keys and open at least one key from each supported type.
  5. Search for known keys and confirm zero-result handling.
  6. Edit one value, then verify persisted data through refresh or re-open.
  7. Change TTL on one key, remove TTL on another, and verify the observed state.
  8. Trigger one dangerous action and verify both cancel and confirm paths.
  9. Open command console, run one safe read command and one invalid command.
  10. Close and relaunch the app, then confirm recent connection state is consistent with product requirements.

Failure-Path Smoke

  • Start app when Redis is unreachable.
  • Attempt login with bad host or credential data.
  • Disconnect Redis mid-session.
  • Trigger invalid value save.
  • Attempt dangerous action, then cancel.
  • Run unsupported or invalid command in console.

Required Evidence

  • Platform, build identifier, and execution timestamp.
  • Screenshots for launch, connection success, key browse, edit save, dangerous-action confirmation, and error state.
  • Exact dataset version and Redis image or binary version.
  • QA log with pass, fail, blocked, or not-run result per step.

Current Blockers On 2026-03-27

  • Verified Linux package artifacts now exist for .deb and .rpm under target/release/bundle/, but AppImage failed in the latest run and no validated package artifact evidence exists yet for macOS or Windows.
  • The repository now provides a Linux-oriented local smoke runbook and Docker-backed Redis fixture conventions, but those steps still need saved cross-platform execution evidence.
  • Current desktop shell now supports live browse, inspect, string save, TTL update, and command execution in Tauri runtime, but full end-to-end smoke evidence still needs saved screenshots or run logs.