ramadhan sjamsani
d09e50af55
- Backend: payment_sessions + pairing_failures tables; payment.service.js and pairing-failure.service.js (new); rewritten pairing.service.js (payment-gated blast + targeted "Curhat lagi" + cancel + fallback); rewritten extension.service.js (data-driven auto-approve with offline safeguard, charge-at-approval); pricing.service.js (extension tiers without free trial); mitra-status.service.js (countAvailableMitras cached path); 60s sweeper for stale payment sessions - Backend routes: client.payment.routes, client.mitra-availability.routes, internal/failed-pairings.routes; client.chat.routes rewritten for payment-gated start + /returning + /cancel + /fallback-to-blast; internal/config.routes adds 4 new keys with Valkey invalidate publish - client_app: mitra-availability poll, payment screen + notifier, pairing notifier rewrite (PairingTargetedWaiting + PairingFailed states), targeted-waiting overlay + bestie-unavailable dialog, "Curhat lagi" CTA, failed-pairing terminal, extension via payment-session - mitra_app: PairingRequestType enum, returning-chat 20s countdown auto-dismiss, extension card "otomatis disetujui" copy - control_center: 4 new config rows in Settings, Failed Pairings page (filter + paginate + action menu), sidebar + route registered - Test infrastructure: Vitest backend (7/7 pass), Playwright CC (4/4 pass), Maestro mobile scaffold (CLI install pending) - Bugs found via Playwright + fixed: LoginPage labels not associated with inputs (a11y); backend internal CORS missing PATCH/PUT/DELETE in allow-methods (silent settings breakage in browsers since Stage 4) - Docs: phase3.7.md PRD, phase3.7-plan.md, phase3.7-questions.md (Q&A), phase3.7-testing.md (E2E checklist), phase3.7-test-run-2026-05-03.md (today's run results) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
26 lines
1.2 KiB
YAML
26 lines
1.2 KiB
YAML
# Shared variables for all client_app Maestro flows.
|
|
#
|
|
# Override at runtime with `maestro test --env KEY=value` or by setting shell env vars.
|
|
# See README.md for full setup + per-machine overrides.
|
|
|
|
env:
|
|
# App identifiers — Android / iOS bundle IDs picked up automatically by `appId:` in flows.
|
|
APP_ID_ANDROID: com.halobestie.client.client_app
|
|
APP_ID_IOS: com.halobestie.client.clientApp
|
|
|
|
# Backend the app talks to — must match what the installed APK was built with
|
|
# (the `--dart-define=API_BASE_URL=...` value at build time).
|
|
BACKEND_URL: http://192.168.88.247:3000
|
|
BACKEND_INTERNAL_URL: http://192.168.88.247:3001
|
|
|
|
# Test customer credentials — must exist in the customers table on the target backend.
|
|
# These are read by helper scripts (see .maestro/scripts/) when seeding state.
|
|
CUSTOMER_PHONE: "+628100000001"
|
|
CUSTOMER_OTP: "123456" # OTP stub mode emits a known code per phone
|
|
|
|
# If you need to drive a "second actor" (e.g., the mitra accepting a blast), the test
|
|
# flows curl the backend directly using these credentials. See README §"Single-emulator
|
|
# + curl pattern" for details.
|
|
TEST_MITRA_ID: "REPLACE-WITH-A-REAL-MITRA-UUID"
|
|
TEST_MITRA_JWT: "REPLACE-WITH-A-VALID-MITRA-JWT"
|