davidl/tolaria
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: QA phase 2 uses pnpm tauri dev instead of DMG, remove Brian review phase

Browse Source
This commit is contained in:
Test
2026-03-30 17:43:43 +02:00
parent d05bc271a8
commit 860efc1f42
1 changed files with 5 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
CLAUDE.md
View File

@@ -50,21 +50,14 @@ BASE_URL="http://localhost:5201" npx playwright test tests/smoke/<slug>.spec.ts
**Phase 2 — Native app QA (also you):**
Install the latest release build and test on the real app before marking done. This catches visual/layout issues that Playwright misses.
Run the app in dev mode and test natively — no need to build a release DMG:
```bash
# Download and install latest release
gh release download --repo refactoringhq/laputa-app \
--pattern "*aarch64.dmg" --dir /tmp/ --clobber
osascript -e 'quit app "laputa"' 2>/dev/null; sleep 2
trash /Applications/laputa.app 2>/dev/null || true
hdiutil attach /tmp/*.dmg -nobrowse -quiet
cp -R /Volumes/laputa/laputa.app /Applications/
hdiutil detach /Volumes/laputa -quiet
open /Applications/laputa.app; sleep 5
pnpm tauri dev &
sleep 10 # wait for app to start
```
Then use the QA scripts to test:
Then use the QA scripts:
```bash
bash ~/.openclaw/skills/laputa-qa/scripts/focus-app.sh laputa
bash ~/.openclaw/skills/laputa-qa/scripts/screenshot.sh /tmp/qa-native.png
@@ -72,16 +65,12 @@ bash ~/.openclaw/skills/laputa-qa/scripts/screenshot.sh /tmp/qa-native.png
bash ~/.openclaw/skills/laputa-qa/scripts/shortcut.sh "command" "s"
```
Use `osascript` for keyboard interactions. Write the result as a comment on the Todoist task:
Use `osascript` for keyboard interactions. Write the result as a Todoist comment on the task:
- ✅ if native QA passes (describe what you tested and saw)
- ❌ if it fails (describe what's wrong) — fix and repeat from Phase 1
**⚠️ WKWebView limitation:** `osascript keystroke` is blocked inside the editor for text input. For features requiring text input: verify app launches + stability, then rely on Playwright for correctness.
**Phase 3 — Brian's review (after push):**
Brian installs the release build and does a final visual check. You've already done the hard part — this is a sanity check. Tasks that pass your Phase 2 rarely fail here.
---
## 2. Development Process