three-tier-testlisted
Install: claude install-skill nuwansamaranayake/AiGNITEClaudeAssets
# three-tier-test
## Purpose
Catch bugs at the layer that surfaces them cheapest. Chrome catches console errors and broken API calls. Mirror catches gesture and layout bugs. Physical device catches sensor, push, and battery bugs.
## When to trigger
Trigger on these user phrases. Match loosely.
- "test my app"
- "verify the build"
- "is this ready to ship"
- "run the test suite"
- "QA the mobile app"
- "three-tier test"
- "pre-flight test"
## Behavior
Run the three tiers in order. Refuse to mark the build "ready" unless all three pass. Each tier writes a pass or fail line to `TEST_RESULTS.md` with a timestamp.
### Tier one: Chrome (Playwright)
1. Start the Expo web build (`npx expo start --web`).
2. Wait for the bundler to settle.
3. Run `scripts/run-tier-one.ps1`. It drives Playwright through every screen.
4. Assert every screen renders without a console error.
5. Assert every API call returns a 2xx status.
6. Hit the same endpoints listed in `scripts/smoke-test.sh`. Reuse the probe list.
7. Write pass or fail to `TEST_RESULTS.md`.
Fails this tier produces an immediate stop. Fix and re-run.
### Tier two: Mirror (iPhone Mirroring or Android emulator)
1. Build a development client (`eas build --profile development --platform <ios|android>`).
2. Install to iPhone Mirroring (Mac) or to the Android emulator.
3. Run `scripts/run-tier-two.ps1`. It loads a Maestro flow or a Detox flow against the running app.
4. Capture screen video for review.
5. Write pass or fail to `T