mcpField
T
test

test

github.com/owainlewisTesting & quality423335 installsUpdated today
Repository

About test

A testing skill for proving user-visible behavior against task or specification criteria. It maps each criterion to evidence, calls for focused checks, and requires gaps to be reported rather than obscured.

Key features

  1. 01Map criteria to proof by ID
  2. 02Add focused tests for missing proof
  3. 03Run narrow or wider checks as needed
  4. 04Verify browser flows and failures
  5. 05Report each criterion with evidence

Use cases

  1. 01Validate behavior changed by a code edit
  2. 02Check UI flows in a real browser
  3. 03Assess regression coverage after refactoring

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/owainlewis/blueprint --skill test

After installing, type/testin Claude Code to confirm it loaded.

Bundled filesagents/openai.yaml

Details

From the project README

Test

Prove the behavior that matters. A passing build or a source-code reading can support the proof, but neither proves a user-visible flow.

Process

  1. Read the task, its source spec when present, changed code, existing tests, and repository instructions. Acceptance criteria come from the task or reviewed spec. Preserve their wording and AC-n, REQ-n, or INV-n IDs. Never rewrite criteria to match the code.
  2. Map every acceptance criterion, cited invariant, and affected failure path to proof by ID. Test changed behavior and behavior a refactor must preserve.
  3. If automated tests cannot exercise the affected behavior, explain why and give other evidence.
  4. Add or update focused tests where proof is missing. Assertions should fail when the changed behavior breaks.
  5. Assert behavior a user or caller can observe unless the test targets a documented internal contract. Keep setup and assertions no more complex than the scenario.
  6. Run the narrowest checks that exercise the changed behavior and affected interfaces. Run wider checks when shared behavior or interfaces changed.
  7. When browser-rendered behavior changes, start the documented app and check the required flows and affected failures in a real browser.
    • Check desktop and mobile when layout or responsive styles changed.
    • Check keyboard use when interactions changed.
    • Check console errors and failed requests during every flow.
    • Capture evidence. Reading source is not browser proof.
  8. Report each AC-n, REQ-n, INV-n, or task criterion as pass, fail, or unverified. Include the command, browser flow, or other evidence.

Return

Report each criterion in this shape:

Criterion: <ID or exact wording>
Result: Pass / Fail / Unverified
Evidence: <command, browser flow, or artifact>
Gap: <what remains unknown, or None>

Lead with failures and unverified criteria. Do not hide them below passing checks.

Boundaries

  • Do not weaken assertions to make a change pass.
  • Do not fix unrelated failures.
  • If required browser tooling is unavailable, report the check as blocked unless the user explicitly accepts a manual exception.

Comments

Markdown supported