How to introduce Playwright e2e testing after initial phases?

[thewebartisan7]

Hi,

I’ve just completed phase 3 of my project and I’m about to start phase 4.

So far, GSD has only generated tests using Vitest, and I realized only now that I would like to also include end-to-end testing with Playwright.

What would be the recommended way to:
1. Add Playwright e2e tests retroactively for phases 1–3
2. Ensure that all future phases automatically include Playwright tests (either after execution or during verification)

In particular, I’d like Playwright to become part of the standard testing/verification workflow alongside Vitest.

Thanks!

[trek-e]

Adding Playwright for future phases

The easiest way to make Playwright part of every future phase:

1. Mention it in /gsd-discuss-phase before each phase. Say something like: "All user-facing features must include Playwright e2e tests alongside unit tests." This gets captured in CONTEXT.md, and the planner/executor will include e2e tests in plans.

2. Add it to your project's CLAUDE.md (or REQUIREMENTS.md) as a standing convention:

   ## Testing
   - Unit tests: Vitest
   - E2e tests: Playwright — required for all user-facing features
   

   GSD agents read CLAUDE.md, so this becomes a persistent instruction.

Retroactive Playwright tests for phases 1-3

Use /gsd-add-tests — this is a workflow specifically for adding test coverage to existing code. Run it after mapping your codebase:

/gsd-map-codebase        # so GSD knows what was built
/gsd-add-tests           # specify Playwright e2e scope

Alternatively, create a dedicated phase for it:

/gsd-add-phase 3.5 e2e-testing
/gsd-discuss-phase 3.5   # scope: Playwright e2e for all existing features

See COMMANDS.md for command details.