Phase 3.7: paid pairing flow + returning chat + extension flip
- 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>
This commit is contained in:
25
backend/test/helpers/server.js
Normal file
25
backend/test/helpers/server.js
Normal file
@@ -0,0 +1,25 @@
|
||||
/**
|
||||
* Build the public or internal Fastify app for in-process testing.
|
||||
*
|
||||
* Tests use `app.inject({ method, url, headers, payload })` to issue requests —
|
||||
* this skips the HTTP layer entirely (no port binding, no socket overhead) and
|
||||
* returns a typed response object.
|
||||
*
|
||||
* Each test file should call `buildPublic()` / `buildInternal()` in beforeAll and
|
||||
* `await app.close()` in afterAll. Re-using the same app across tests in a file
|
||||
* is fine — the DB state is what's reset between tests.
|
||||
*/
|
||||
|
||||
export const buildPublic = async () => {
|
||||
const { buildPublicApp } = await import('../../src/app.public.js')
|
||||
const app = await buildPublicApp()
|
||||
await app.ready()
|
||||
return app
|
||||
}
|
||||
|
||||
export const buildInternal = async () => {
|
||||
const { buildInternalApp } = await import('../../src/app.internal.js')
|
||||
const app = await buildInternalApp()
|
||||
await app.ready()
|
||||
return app
|
||||
}
|
||||
Reference in New Issue
Block a user