test-data-and-stubs
Use when a case needs data, a user/role, or a third-party dependency - seeding through the product first, test credentials, namespacing on shared environments, and stubbing an external HTTP service by hand
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-15
- Stars
- ★ 122
- Forks
- 18
01 前言 Front Matter
- name
- test-data-and-stubs
- category
- qa
- description
- Use when a case needs data, a user/role, or a third-party dependency - seeding through the product first, test credentials, namespacing on shared environments, and stubbing an external HTTP service by hand
03 SKILL.md 正文
Test Data and Stubs
Seed order
- Through the product's own API/UI (black-box; this exercises validation as a side effect).
- The repo's documented seed (
make seed,npm run db:seed,prisma db seed— find it viaget_project_briefor the README). - SQL last, and only on a local DB.
Record the seed commands you ran in the case's evidence.
Database
The repo's docker-compose service (docker compose up -d db returns), else its documented local DB. No container runtime available → say so as a blocker (qa-verify-before-verdict's triage table), don't improvise a different engine — a SQLite stand-in for Postgres hides real dialect bugs.
Credentials
Pull from .env.example or the repo's own seed fixtures. Never a real person's account. A third-party sandbox key you don't have is a human blocker (ask_user), not something to work around.
Namespacing on shared environments
On stage: prefix everything you create with qa-<task-key>-…, clean it up when you're done, never run a destructive scenario there.
Stubbing a third-party HTTP dependency by hand
docker run -d --rm -p 8089:8080 wiremock/wiremock:3.13.2
curl -X POST localhost:8089/__admin/mappings -d '{"request":{"method":"POST","url":"/charge"},"response":{"status":402,"jsonBody":{"error":"declined"}}}'
# point the app's dependency URL env var at http://localhost:8089, drive the scenario, then:
curl -s localhost:8089/__admin/requests | jq '.requests[].request.url' # no jq: node -e 'let d="";process.stdin.on("data",c=>d+=c).on("end",()=>JSON.parse(d).requests.forEach(r=>console.log(r.request.url)))'
Or use the repo's own mock server if it already has one — prefer that over standing up a second one.
After the round
Save a working boot+seed recipe to project memory (save_memory, scope=project) once it cost you real effort — the next QA round on this repo should not rediscover it.
04 同仓库更多 Skills
visual-craft
暂无简介
ux-copy
Use when you write any words a user reads in a mockup or a hand-off - content language and voice, buttons, labels, errors, empty states, confirmations, numbers and dates, and the longest-string check
screen-mockup-html
Use when you draw screens as the design task's HTML mockup - ONE canvas document holding every screen and every variant side by side, the sanitizer-safe recipe, phone and wide frames, the states grid, static control states, and the loopback self-check with screenshots at 375, 768 and 1440 attached to the task
performance-awareness
How the performance score moves for your role. Use when the score context shows a declining trend, or before handing off work you have not self-checked against every criterion.
design-variants
Use when a screen design needs variants - how many, variants as side-by-side rows on the one canvas, what makes two variants genuinely different, recommending one, how the human's choice is read, and narrowing to the chosen one in revision
design-system-authoring
Use when you derive, change or extend a design system - where tokens live per stack, the DTCG token tree, role-based names for both themes, base vs layer vs drift, the DESIGN.md section order, the inventory format, the contrast check and the lint every proposal returns