saqib mirandClaude Sonnet 5 8400a8db84 feat(016-load-concurrency-testing): US5 — autocannon load-test tooling
tests/load/autocannon.config.ts is a thin shared wrapper over autocannon's
programmatic API producing this feature's own report shape (throughput,
latency p50/p90/p99, non-2xx, rate-limited count) — printed and written to
tests/load/reports/ (gitignored) for every run. No pass/fail threshold is
applied (FR-009): throughput/latency targets are an OPEN BUSINESS DECISION
per the roadmap's own convention, never invented.

Three scripts cover the named critical endpoint groups: ticket-creation
(pure DB path), admin-reporting (015-reporting-dashboards, pure DB path),
and ai-support-flow (005-ai-support's real Anthropic API calls — clearly
flagged as real, billed cost, run only at a small bounded amount rather than
an open-ended duration). All three were run once at a small scale against the
real dev server to confirm the tooling works end-to-end and cleans up fully
after itself (verified via direct DB checks, not just script exit codes).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-10 11:50:12 +05:30
2026-08-19 16:29:17 +05:30
2026-08-19 16:29:17 +05:30
2026-08-19 16:29:17 +05:30
2026-08-19 16:29:17 +05:30
2026-08-19 16:29:17 +05:30
2026-08-19 16:29:17 +05:30
2026-08-19 16:29:17 +05:30
2026-08-20 11:27:15 +05:30
2026-08-19 16:29:17 +05:30
2026-08-19 16:29:17 +05:30
2026-08-19 16:29:17 +05:30
2026-09-09 17:39:12 +05:30
2026-08-19 16:29:17 +05:30
2026-08-19 16:29:17 +05:30

Development

  • docker compose --env-file .env.development -f docker-compose.development.yml up -d --build

Test

  • docker compose --env-file .env.test -f docker-compose.test.yml up --build

Production

  • docker compose --env-file .env.prod -f docker-compose.prod.yml up --build -d

Stop

  • docker compose -f docker-compose.prod.yml down

List Containers

  • docker compose --env-file .env.development -f docker-compose.development.yml ps

Logs

  • docker compose --env-file .env.development -f docker-compose.development.yml logs -f

Database Migrations

  • Local (using .env.development):
    • Create/apply new migration: npx prisma migrate dev --name <name>
    • Push schema directly (prototype/sync): npx prisma db push
    • Deploy pending migrations: npm run prisma:deploy
  • Inside Docker Container:
    • docker exec -it support-api-development npx prisma migrate deploy

Database Seeding

  • Local:
    • npm run prisma:seed (or npx tsx --env-file=.env.development prisma/seed/index.ts)
  • Inside Docker Container:
    • docker exec -it support-api-development npm run prisma:seed
S
Description
No description provided
Readme
1.2 MiB
Languages
TypeScript 93.2%
PowerShell 6.5%
JavaScript 0.2%