Verification · Intent and spec conformance · Functional spec verification
Browser verification
An agent or script performs the flow and checks the outcome.
How to build it
- Turn each acceptance criterion into a sequence of browser steps.
- Run the steps against the preview deployment for the pull request.
- Assert the observable outcome, such as visible text or a URL change, for each step.
Signals in a repository
- Playwright test files that open the preview URL from an environment variable.
- A preview deployment workflow that passes its URL to the test job.
In practice
55 repositories run a tool for this check in the scanned set.
playwright· 55 repos
Examples
-
freeCodeCamp/freeCodeCamp ·
playwrightplaywright test --ui-port=0 -
nousresearch/hermes-agent ·
playwrightplaywright test -c e2e/core/playwright.config.ts local-gateway-attach.spec.ts -
microsoft/vscode ·
playwrightplaywright test -
n8n-io/n8n ·
playwrightplaywright test --project=e2e tests/e2e/building-blocks/ --workers=1 --retries=2 --reporter=list -
langflow-ai/langflow ·
playwrightplaywright test $SCAN_SPECS --project=chromium --shard=$EXPR/$EXPR --workers=2 --retries=1