mr-onion

TestForge Phase 16 Implementation Backlog

Version: 1.0 Date: 2026-08-26 Status: Complete. TFP-001-004 and 010-026 landed 2026-08-28 (af0492d through 69e996f); TFP-033 cce15cf (2026-08-29); TFP-030 92b921b, TFP-032 c965442, TFP-005 and 031 4d58947 (all 2026-09-17). Decision record: docs/decisions/phase-16-local-first-decision-record.md. Reconciled with git 2026-09-29.

Ticket prefix is TFP-. This is distinct from the TFXX-NNN identifiers TestForge assigns to tests inside generated suites at runtime.


Product Vision

TestForge is an AI-native test automation assistant for testers who understand quality but do not write automation code. A tester describes what to test in plain English; TestForge generates a Playwright suite, runs it, and returns a structured report covering execution, defects, coverage, performance, usability and SEO. It runs on the tester’s own machine against a local target.

Current Functionality (Baseline)

Scope (Phase 16)

In scope

  1. Removing the deployment surface and asserting local-only posture.
  2. Deleting the FastAPI backend and the backend-proxy layer.
  3. Scoping browser execution to Chromium.
  4. Decomposing the three oversized source files.
  5. Bringing documentation into line with the shipped product.
  6. Creating the project’s first TEST_PLAN.md.

Out of scope

Development Phases

Phase 16A — Posture and hygiene

Phase 16B — Removal

Phase 16C — Decomposition

Phase 16D — Coverage


Backlog

TFP-001 — Remove the production and staging deployment surface

TFP-002 — Document the local-execution security model

TFP-003 — Untrack committed build and test artifacts

TFP-004 — Add .gitattributes and a LICENSE

TFP-005 — Delete stale remote branches

TFP-010 — Delete the FastAPI backend and Python toolchain

TFP-011 — Remove the backend-proxy layer from all five API routes

TFP-012 — Scope browser execution to Chromium

TFP-013 — Deduplicate pull-request CI

TFP-014 — Rewrite README against the shipped product

TFP-020 — Extract the report engine into src/lib/report/

TFP-021 — Split the run route into modules

TFP-022 — Split the generate route into modules

TFP-023 — Split page.tsx into section components

TFP-024 — Add a file-size guard to lint

TFP-025 — Decompose the mock suite generator

TFP-026 — Decompose the introspect route

TFP-030 — Create TEST_PLAN.md

TFP-031 — Close the regression gap left by proxy removal

HLT-01 evidence

Moved word for word from docs/test-plan/HLT.md by TFP-253; the case’s row there links here.

Test: GET /api/health (automated: tests/regression/testforge.sections.spec.ts — “reports health and observability metadata”)

Expected result: Response is ok; JSON body includes status: "ok", service: "testforge-next", a string environment, mode: "local-in-process" (TFP-031 — every route runs in-process since TFP-010/011 deleted the FastAPI proxy layer, so there is no other mode to report), a siteUrl containing http, and an ISO timestamp; response carries X-Frame-Options: DENY, X-Content-Type-Options: nosniff, Referrer-Policy: strict-origin-when-cross-origin, a Permissions-Policy restricting camera, and a Content-Security-Policy with default-src 'self'.

TFP-032 — Record the SaaS prerequisites


  1. TFP-001 — remove the deployment surface
  2. TFP-002 — document the security model
  3. TFP-003 — untrack artifacts
  4. TFP-004 — .gitattributes and LICENSE
  5. TFP-010 — delete FastAPI
  6. TFP-011 — remove the proxy layer
  7. TFP-012 — scope to Chromium
  8. TFP-013 — deduplicate PR CI
  9. TFP-014 — rewrite the README
  10. TFP-020 — extract the report engine
  11. TFP-021 — split the run route
  12. TFP-022 — split the generate route
  13. TFP-023 — split page.tsx
  14. TFP-024 — file-size guard
  15. TFP-025 — decompose the mock suite generator
  16. TFP-026 — decompose the introspect route
  17. TFP-030 — create TEST_PLAN.md
  18. TFP-031 — close the regression gap
  19. TFP-032 — record SaaS prerequisites
  20. TFP-033 — fix javascript:/tel: link miscategorization
  21. TFP-005 — delete stale remote branches

TFP-001 through TFP-004 have no dependencies and are ordered first because they are cheap and remove the most misleading content in the repository. TFP-005 is last because branch deletion is irreversible and worth doing only once the phase is otherwise settled. TFP-020 precedes TFP-021, TFP-022 and TFP-023 because all three shrink substantially once report construction has already moved out — doing them in the other order means moving the same code twice. TFP-025 and TFP-026 follow TFP-024 because the lint gate it added is what surfaced them: both decompose files that TFP-020 through TFP-023’s original scoping missed, and both must land before Gate C can be honestly declared complete. TFP-033 depends on TFP-026 because it touches the same introspection module that ticket just finished decomposing, and it was found by exercising the shipped Phase 16 build against a real site rather than by any ticket in the original scope — it predates Phase 16 and is not a Gate requirement, but it should land before Phase 17 is locked.

Suggested Milestone Gates

Gate A — Posture and hygiene complete

Gate B — Removal complete

Gate C — Decomposition complete

Gate D — Phase 16 complete