Add isolated visual testing guidance

2026-10-27 19:17:49 +03:00
parent 54a5c849d4
commit 464b610bf1
7 changed files with 137 additions and 2 deletions
@@ -31,6 +31,7 @@ Copy `assets/task.md.tmpl`. Rules:
 - Write scope: globs. Everything else is read-only.
 - Contract: exact signature or output shape. If it is not written, it is not frozen.
 - Acceptance: 1–3 commands a verifier can re-run. "Code is clean" is not a check.
+- GUI: acceptance includes a deterministic screenshot command, fixed window sizes and an isolated display; see `references/visual-testing.md`.
 - Stop conditions: time/attempt limit (25 min for S/M, 45–60 for L) plus "ask, do not guess" for load-bearing unknowns.
 - Never include another task's internal details; workers do not need the whole plan.

@@ -43,6 +44,7 @@ Copy `assets/verifier.md.tmpl`. Rules:
 - Require a table: criterion, command, observed, pass/fail.
 - Ask for scope, contract, and test-quality checks.
 - Require the full review file **first**, then a minimal `{task_id, verdict, summary, review_file}` return (`assets/verdict.schema.json`). The review file is the source of truth; a schema miss must not erase the verification work.
+- GUI: require an isolated Xvfb/display, screenshots at default and minimum sizes, and the exact commands used; shared-desktop screenshots are not evidence.

 ## Report