A complete loop for defining, generating, running and gating tests:
- qa/: scenario-card template + examples (API/UI/binding), the Claude
generation prompt, and a QA runbook tying it together
- e2e/CLAUDE.md: conventions that keep AI-generated tests consistent
- run-tests.ps1: one runner for every layer (backend/api/web/ui/binding),
logs per run under .testlogs/, JUnit output, evidence report, and a
re-seed guard against stale demo data
- .githooks/ + scripts/install-hooks.ps1: pre-commit secret scan and
pre-push unit tests (shift-left before CI)
- evidence report now captures each API call's request, payload and
response (Authorization redacted); JUnit reporter added for CI
- scripts/db.mjs: db:check freshness guard
Azure DevOps pipeline deferred; the runner already emits JUnit + the
evidence report for any CI to publish.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Angular + Go + PostgreSQL sample with strict per-tenant isolation.
- Backend: Go API (basic auth, tenant-scoped repository layer, pgx pool)
- Frontend: Angular 22 SPA (search, checkout, bookings, dashboard)
- Database: schema, seed data and demo bookings migrations
- Tests: 311 across Go (integration), Angular (unit) and Playwright (e2e),
plus a generated evidence report with PDF export
- Security: whitebox VAPT report under security/
Secrets (.env, tokens, DB credentials) are git-ignored.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
nilesh.pandClaude Opus 4.8