testing-techniques SKILL.md skillA
testing-techniques from kamiazya/whiteboard is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add kamiazya/whiteboard/testing-techniques@git:20261016.1b514a4Pins git:20261016.1b514a4 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- kamiazya/whiteboard
- Path
.claude/skills/testing-techniques/SKILL.md- Versions recorded
- 7
- Latest version
- git:20261016.1b514a4, committed Oct 16, 2026
- First version recorded
- Sep 5, 2026
- Size
- 7,900 bytes
- Repository stars
- 10
- License
- Apache-2.0
The whiteboard repo's automated-testing technique catalogue — how to write a vitest test that stays green under a full parallel run (async assertions, fake timers, browser mode, mocks and isolation), how to prove a test is stable before pushing (repeats, stress, quarantine budget), how property-based and mutation testing close the loop on a test that asserts nothing, which flake shapes are already caught by an executable rung (GritQL plugin, setup-file guard, arch-lint scan) and how to add…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Testing techniques (whiteboard) `test-layer-selection` answers **where** a test goes. This skill answers **how to write one that stays green** and **how to know it asserts something**. The body here is an index; the detail is in `resources/*.md`, opened one at a time for the situation at hand — never all at once. ## The rung ladder Every technique here sits on a rung, and the rung is chosen by what would actually catch the mistake — strongest first: | Rung | Catches the mistake… | This repo's instruments | |---|---|---| | **executable** | at lint / typecheck / test time, mechanically | `tools/biome-plugins/test-flake-shapes.grit` (rules read from the file by its guard), `tools/arch-lint`'s test scans (lazy imports, duplicate titles, the sleep ledger), guard tests (`browser-test-name-length`, `vitest-data-dir`, `local-node-version`) | | **setup guard** | at runtime, for every test in a project | `apps/web/vitest.setup.ts` (cleanup, fake-timer leak, localStorage), `browser-setup.ts` (stylesheet, async budget), `sharedBrowserTestConfig` (trace bounds) | | **review criteria** | when a reviewer reads the diff | `review-gate/resources/test-coverage.md` | …
Read the whole file at its exact version.
How to install
mdr add kamiazya/whiteboard/testing-techniques@sha256:77585dcf3aec9153The line at the top of this page pins the label git:20261016.1b514a4, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_w7ixreutxjzy3tw6)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 7 versions of this file, between Sep 5, 2026 and Oct 16, 2026, about one every 7 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261016.1b514a4 latest | 2026-10-16 | 1b514a4 | 7,900 B | A | view · diff |
| git:20261005.1352b04 | 2026-10-05 | 1352b04 | 7,845 B | A | view · diff |
| git:20261002.3e13332 | 2026-10-02 | 3e13332 | 7,700 B | A | view · diff |
| git:20260910.4198017 | 2026-09-10 | 4198017 | 7,706 B | A | view · diff |
| git:20260906.55daf32 | 2026-09-06 | 55daf32 | 7,704 B | A | view · diff |
| git:20260905.5aa74fd | 2026-09-05 | 5aa74fd | 7,689 B | A | view · diff |
| git:20260905.fbee5e2 | 2026-09-05 | fbee5e2 | 6,559 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7900 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
kamiazya/whiteboard · 10 stars · license Apache-2.0 · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_w7ixreutxjzy3tw6 GET https://markdownregistry.com/api/v1/resolve?ref=kamiazya/whiteboard/testing-techniques GET https://markdownregistry.com/api/v1/blob/77585dcf3aec9153d852e046b1cf476d445d00c77bb0d489a3d612b6ec5e5d93
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.