ken/opencode-boilerplate
2
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Require Playwright E2E tests in every verification step

Browse Source 
- New skill e2e-testing: on-demand Playwright setup (config, test:e2e script), acceptance-criteria-driven specs (one per feature + app-shell smoke), blueprint-driven semantic locators, and the shared verification checklist
- /add-feature Step 7 and /execute-milestones Step 2.6 now write/update E2E specs and run npm run test:e2e alongside test/lint/typecheck; milestone gates and completion criteria include E2E
- /generate-app Step 5 sets up Playwright and creates the app-shell smoke spec for the web target (integration_test / UI automation noted for flutter/winui3)
- steering tasklist template, milestone-planning Definition of Done, milestone-execution task slicing/gates, development-guidelines pointers, and implementation-validator checks updated
- AGENTS.md and README updated

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Ken Yasue
2026-07-02 12:26:23 +02:00
parent 3274aa41e2
commit 362eebd22d
11 changed files with 168 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
.opencode/command/add-feature.md
View File

@ -119,15 +119,19 @@ If any of the following situations occur while the implementation loop is runnin
**Once this step completes successfully, never stop; immediately proceed to Step 7.**
## Step 7: Run Automated Tests
## Step 7: Run Automated Tests (including Playwright E2E)
1. Run the following commands in order and confirm that all tests pass.
1. Write or update the feature's end-to-end tests following the **e2e-testing** skill (loaded automatically):
- Create/update `e2e/[feature-name].spec.ts` covering the feature's acceptance criteria.
- If Playwright is not yet set up in the repository, set it up first as described in the skill.
2. Run the following commands in order and confirm that all of them pass.
```bash
npm test
npm run lint
npm run typecheck
npm run test:e2e
```
2. If any command produces an error, analyze the problem, generate and apply a fix, and then run this step again.
3. If any command produces an error, analyze the problem, generate and apply a fix, and then run this step again. Never skip or delete a failing test to make verification pass.
**Once this step completes successfully, never stop; immediately proceed to Step 8.**
@ -162,7 +166,7 @@ If any of the following situations occur while the implementation loop is runnin
This workflow completes automatically once all of the following conditions are met.
- Step 5: All tasks in `tasklist.md` are complete (`[x]` or skipped for a valid reason).
- Step 6: The `implementation-validator` subagent's validation passes.
- Step 7: The `test`, `lint`, and `typecheck` commands all succeed without errors.
- Step 7: The `test`, `lint`, `typecheck`, and `test:e2e` (Playwright) commands all succeed without errors, and the feature has E2E tests covering its acceptance criteria.
- Step 8: Handover notes are recorded in `tasklist.md`, all six persistent documents in `docs/` have been reconciled with the feature (updates applied, or a skip reason noted for each), and the feature is checked off in its phase file (if `docs/milestones/` exists).
Until these completion criteria are met, continue to think autonomously, solve problems, and carry on the work.