Files

Ramadhan Sjamsani 9696eadeaf Mitra §A: pre-home (S3a/S3b/AccountInactive) + design system + Bestie Home

- Port halo_tokens + halo_theme + HaloButton to mitra_app (rose palette,
  Bricolage display, Poppins body, JetBrainsMono).
- Build S3a Input WhatsApp (figma-bestie BestieS3 first half) with
  +62 chip, leading-zero/62 normalization, allow '+' in input.
- Build S3b OTP verification (6-digit, 60s resend timer, attempts hint,
  Focus(canRequestFocus:false) for maestro inputText compat) with full
  error branching (CODE_MISMATCH, OTP_EXPIRED, OTP_USED, ATTEMPTS_EXCEEDED,
  WRONG_FLOW, ACCOUNT_INACTIVE).
- Add AccountInactive terminal screen for is_active=false mitras.
- Typed MitraAuthError with Indonesian-first localized messages +
  retryAfterSeconds passthrough.
- Rebuild home_screen.dart to match figma BestieHome (greeting + status
  card + Ganti Status CTA + Pengingat + 2-tile dark grid).
- Backend: POST /internal/_test/seed-mitra (idempotent) and
  PATCH /internal/mitras/:id (display_name update).
- Control center: inline Edit Nama on mitras row + expandable inline log
  table under clicked mitra (vs old below-table panel).
- 5 maestro flows ts-mitra-A-01/03/04/05/06 covering invalid input, happy
  path, account inactive, phone-format normalization, and the back-to-S3a
  regression. All green.

Plan + memory documented in:
- requirement/phase4-mitra-prehome-plan.md
- requirement/flow_mitra.md / flow_mitra.mermaid.md §A

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-19 22:01:28 +08:00

flows

Mitra §A: pre-home (S3a/S3b/AccountInactive) + design system + Bestie Home

2026-05-19 22:01:28 +08:00

scripts

Mitra §A: pre-home (S3a/S3b/AccountInactive) + design system + Bestie Home

2026-05-19 22:01:28 +08:00

config.yaml

Phase 3.7: paid pairing flow + returning chat + extension flip

2026-05-03 23:02:49 +08:00

README.md

Phase 3.7: paid pairing flow + returning chat + extension flip

2026-05-03 23:02:49 +08:00

README.md

mitra_app Maestro flows

End-to-end UI automation for the mitra Flutter app using Maestro. Single-emulator + curl-as-customer pattern — when a flow needs a customer to "do something", it's simulated via backend API calls fired from runScript steps.

One-time install

See client_app/.maestro/README.md — Maestro is a global CLI, install once and it serves both apps.

You also need:

adb on your PATH (Android Studio platform-tools)
jq (apt install jq / brew install jq)
One Android emulator OR one connected device — only one at a time (per project decision)

Folder layout

.maestro/
├── README.md                 # this file
├── config.yaml               # shared env: app IDs, backend URL, test credentials
├── flows/
│   ├── 01_smoke.yaml
│   ├── 02_online_offline_toggle.yaml
│   └── 03_accept_general_blast.yaml
└── scripts/
    └── customer_blast_now.sh

Configure for your environment

Edit .maestro/config.yaml and fill in:

BACKEND_URL — must match the --dart-define=API_BASE_URL=... value the installed APK was built with
TEST_CUSTOMER_ID and TEST_CUSTOMER_JWT — used by the curl harness to fire blasts toward this mitra

Run a flow

maestro test mitra_app/.maestro/flows/01_smoke.yaml

# all flows
maestro test mitra_app/.maestro/flows/

If multiple devices are attached:

adb devices
maestro --device emulator-5554 test mitra_app/.maestro/flows/01_smoke.yaml

Per-machine overrides

Override config.yaml values at runtime:

maestro test \
  --env BACKEND_URL=http://192.168.99.10:3000 \
  --env TEST_CUSTOMER_JWT=eyJhbGc... \
  mitra_app/.maestro/flows/03_accept_general_blast.yaml

Single-emulator + curl pattern

This mirrors the client_app pattern. When a mitra-side flow needs the customer to act, the flow uses runScript: to fire the customer's API calls directly:

Mitra app is on screen via Maestro on the only connected device
runScript: ../scripts/customer_blast_now.sh creates + confirms a payment_session and fires a chat request as a "fake" customer
The mitra app receives the blast via WS as it would from a real customer; Maestro asserts the overlay appears

For the customer-side equivalent (drive customer with Maestro, simulate mitra via curl), see client_app/.maestro/.

When to run mitra flows vs. client_app flows

Default: drive the customer side via client_app/.maestro/. Most Phase 3.7 assertions live there (CTA gating, payment screen, searching screen, failed-pairing terminal, "Curhat lagi" overlays).
Run mitra flows when you specifically need to assert mitra UI:
- Returning-chat 20s countdown actually visible + ticking
- Extension card copy reads "otomatis disetujui"
- Online/offline toggle behavior (Section J — mitra goes offline mid-session)
- Incoming-request overlay accept/decline buttons

Adding a new flow

See client_app/.maestro/README.md — same pattern.

Troubleshooting

See client_app/.maestro/README.md — same checklist applies.