QA Report: Bootstrap monorepo (PR #29)

[sortakool]

QA Report

PR: #29 — Bootstrap monorepo: Bun + Hono backend, Next.js frontend, Doppler secrets
Branch: feat/bootstrap-monorepo
Date: 2026-02-25
Verdict: ✅ PASS

All 24 Gherkin scenarios passed. Zero failures, zero errors.

---

Gherkin Scenarios

#	Scenario	Category	Result
1	Root package.json defines Bun workspaces	Monorepo Structure	✅ PASS
2	Shared TypeScript strict configuration	Monorepo Structure	✅ PASS
3	Root .gitignore covers all expected patterns	Monorepo Structure	✅ PASS
4	Backend workspace exists with Hono dependency	Backend (apps/api)	✅ PASS
5	Backend project structure follows conventions	Backend (apps/api)	✅ PASS
6	Backend health endpoint returns OK	Backend (apps/api)	✅ PASS
7	Backend starts with hot reload on port 4000	Backend (apps/api)	✅ PASS
8	Backend CORS allows the frontend origin	Backend (apps/api)	✅ PASS
9	Backend TypeScript config extends the root base	Backend (apps/api)	✅ PASS
10	Frontend workspace exists with Next.js and React Query	Frontend (apps/web)	✅ PASS
11	Frontend has Tailwind CSS configured	Frontend (apps/web)	✅ PASS
12	Frontend uses Next.js App Router layout	Frontend (apps/web)	✅ PASS
13	React Query provider is wired up	Frontend (apps/web)	✅ PASS
14	Sidebar navigation contains all required links	Frontend (apps/web)	✅ PASS
15	Placeholder pages exist for each nav item	Frontend (apps/web)	✅ PASS
16	API client utility reads backend URL from environment	Frontend (apps/web)	✅ PASS
17	Frontend starts on port 3000	Frontend (apps/web)	✅ PASS
18	Frontend TypeScript config extends the root base	Frontend (apps/web)	✅ PASS
19	Doppler config file points to the project	Doppler Integration	✅ PASS
20	Environment example file documents all required variables	Doppler Integration	✅ PASS
21	Backend reads secrets via process.env at runtime	Doppler Integration	✅ PASS
22	README documents Doppler workflow	Doppler Integration	✅ PASS
23	Root dev script starts both apps concurrently	Dev Experience	✅ PASS
24	README includes setup instructions	Dev Experience	✅ PASS

Total: 24 passed, 0 failed, 0 errors (607ms, 1 worker)

---

Failures

None. All 24 scenarios passed.

---

Screenshots

No screenshots were captured — Playwright only saves screenshots on failure by default, and all tests passed.

---

Analysis Notes

• Static (filesystem) checks: 22 of 24 scenarios — validate file existence, content, and configuration by reading the repo directly via Node fs.
• Runtime (HTTP) checks: 2 of 24 scenarios (Amadeus API integration service #6 and Hotel search API: venue-proximity hotel recommendations #8) — hit the live backend on http://localhost:4000 to verify the health endpoint and CORS headers.
• Browser (Playwright page navigation) checks: 0 of 24 scenarios — no tests use Playwright's browser automation.

Observations

1. No browser-level testing. All 24 tests are either filesystem assertions or raw fetch() calls. None navigate to the Next.js frontend at http://localhost:3000 in a browser context. Pragmatic for a bootstrap PR but means visual/rendering regressions are not caught.

2. Dev server teardown noise. The backend was killed (SIGKILL) after tests completed, followed by an EADDRINUSE error on port 4000 — cosmetic, does not affect test results.

3. Frontend dev server not exercised. The Playwright config sets baseURL: "http://localhost:3000" but no test navigates to it. A follow-up PR could add a smoke test that loads the root page in a browser.

4. Gherkin ↔ Spec fidelity is excellent. Every Scenario: line in bootstrap-monorepo.feature has a 1:1 corresponding test() block in gherkin.spec.ts.

5. .env.example secret leakage check is smart. Scenario 20 parses each KEY=value line and asserts values are empty or safe defaults.

---

Full Playwright output

Running 24 tests using 1 worker

  ✓   1 .attractor/qa-report/gherkin.spec.ts:35:7 › Category 1: Monorepo Structure › Scenario 1: Root package.json defines Bun workspaces (2ms)
  ✓   2 .attractor/qa-report/gherkin.spec.ts:49:7 › Category 1: Monorepo Structure › Scenario 2: Shared TypeScript strict configuration (1ms)
  ✓   3 .attractor/qa-report/gherkin.spec.ts:60:7 › Category 1: Monorepo Structure › Scenario 3: Root .gitignore covers all expected patterns (2ms)
  ✓   4 .attractor/qa-report/gherkin.spec.ts:90:7 › Category 2: Backend (apps/api) › Scenario 4: Backend workspace exists with Hono dependency (1ms)
  ✓   5 .attractor/qa-report/gherkin.spec.ts:100:7 › Category 2: Backend (apps/api) › Scenario 5: Backend project structure follows conventions (1ms)
  ✓   6 .attractor/qa-report/gherkin.spec.ts:117:7 › Category 2: Backend (apps/api) › Scenario 6: Backend health endpoint returns OK (12ms)
  ✓   7 .attractor/qa-report/gherkin.spec.ts:130:7 › Category 2: Backend (apps/api) › Scenario 7: Backend starts with hot reload on port 4000 (1ms)
  ✓   8 .attractor/qa-report/gherkin.spec.ts:145:7 › Category 2: Backend (apps/api) › Scenario 8: Backend CORS allows the frontend origin (2ms)
  ✓   9 .attractor/qa-report/gherkin.spec.ts:158:7 › Category 2: Backend (apps/api) › Scenario 9: Backend TypeScript config extends the root base (1ms)
  ✓  10 .attractor/qa-report/gherkin.spec.ts:173:7 › Category 3: Frontend (apps/web) › Scenario 10: Frontend workspace exists with Next.js and React Query (3ms)
  ✓  11 .attractor/qa-report/gherkin.spec.ts:189:7 › Category 3: Frontend (apps/web) › Scenario 11: Frontend has Tailwind CSS configured (1ms)
  ✓  12 .attractor/qa-report/gherkin.spec.ts:207:7 › Category 3: Frontend (apps/web) › Scenario 12: Frontend uses Next.js App Router layout (1ms)
  ✓  13 .attractor/qa-report/gherkin.spec.ts:220:7 › Category 3: Frontend (apps/web) › Scenario 13: React Query provider is wired up (1ms)
  ✓  14 .attractor/qa-report/gherkin.spec.ts:233:7 › Category 3: Frontend (apps/web) › Scenario 14: Sidebar navigation contains all required links (1ms)
  ✓  15 .attractor/qa-report/gherkin.spec.ts:246:7 › Category 3: Frontend (apps/web) › Scenario 15: Placeholder pages exist for each nav item (2ms)
  ✓  16 .attractor/qa-report/gherkin.spec.ts:259:7 › Category 3: Frontend (apps/web) › Scenario 16: API client utility reads backend URL from environment (1ms)
  ✓  17 .attractor/qa-report/gherkin.spec.ts:269:7 › Category 3: Frontend (apps/web) › Scenario 17: Frontend starts on port 3000 (0ms)
  ✓  18 .attractor/qa-report/gherkin.spec.ts:282:7 › Category 3: Frontend (apps/web) › Scenario 18: Frontend TypeScript config extends the root base (0ms)
  ✓  19 .attractor/qa-report/gherkin.spec.ts:297:7 › Category 4: Doppler Integration › Scenario 19: Doppler config file points to the project (0ms)
  ✓  20 .attractor/qa-report/gherkin.spec.ts:310:7 › Category 4: Doppler Integration › Scenario 20: Environment example file documents all required variables (2ms)
  ✓  21 .attractor/qa-report/gherkin.spec.ts:345:7 › Category 4: Doppler Integration › Scenario 21: Backend reads secrets via process.env at runtime (1ms)
  ✓  22 .attractor/qa-report/gherkin.spec.ts:364:7 › Category 4: Doppler Integration › Scenario 22: README documents Doppler workflow (0ms)
  ✓  23 .attractor/qa-report/gherkin.spec.ts:385:7 › Category 5: Dev Experience › Scenario 23: Root dev script starts both apps concurrently (0ms)
  ✓  24 .attractor/qa-report/gherkin.spec.ts:401:7 › Category 5: Dev Experience › Scenario 24: README includes setup instructions (0ms)

  24 passed (607ms)