mk-testing
Writing tests, running validation, and (TDD mode) red-green-refactor. Active in Test + Build phases. NOT for coverage-gap mapping (mk:nyquist) or sprint contracts (mk:sprint-contract).
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 16
- Forks
- 3
01 前言 Front Matter
- name
- mk-testing
- description
- Writing tests, running validation, and (TDD mode) red-green-refactor. Active in Test + Build phases. NOT for coverage-gap mapping (mk:nyquist) or sprint contracts (mk:sprint-contract).
02 资源文件 4
- 参考文档references/e2e-best-practices.md3.5 KB
- 参考文档references/red-green-refactor.md5.5 KB
- 参考文档references/validation-scripts.md3.7 KB
- 参考文档references/visual-qa.md4.1 KB
03 SKILL.md 正文
Testing Toolkit
Reference guides for testing: TDD red-green-refactor, validation scripts, and visual QA.
When to Use
- During Phase 2 (Test) for writing tests — failing tests first in TDD mode (
--tdd/MEOWKIT_TDD=1), or any-order tests in default mode - During Phase 3 (Build) for verifying implementation
- When the
testeragent needs testing patterns - For visual QA testing of web applications
Workflow Integration
Operates in Phase 2 (Test) and Phase 3 (Build). Output supports the tester agent.
In TDD mode the cycle is RED → GREEN → REFACTOR (failing tests required before implementation). In default mode (TDD off), tests may be written before, alongside, or after implementation — the developer chooses.
References
| Reference | When to load | Content |
|---|---|---|
| red-green-refactor.md | Phase 2-3 | TDD cycle, test-first rules, refactoring guidelines |
| validation-scripts.md | After code changes | Running validation scripts, interpreting results |
| visual-qa.md | UI testing | Browser-based visual QA, screenshot comparison, responsive testing |
| e2e-best-practices.md | When creating E2E tests | Tool preference, locator strategy, wait patterns, POM, flaky quarantine, success metrics |
Gotchas
- Mocks hiding integration failures: All mocked tests pass but real service calls fail → Use integration tests for critical paths; mock only external third-party services
- Test coverage metric gamed by trivial assertions: 100% coverage with
expect(true).toBe(true)→ Measure mutation testing score alongside coverage; flag tests with zero assertions - Vue-specific test design/review: for designing or auditing Vitest + Vue Test Utils tests (components, composables, Pinia, router, Suspense, Teleport) → use
mk:vue-testing-best-practices(advisory/review only; this skill still owns running tests + TDD)
04 同仓库更多 Skills
mk-worktree
Manages git worktrees for parallel agent isolation: creates parallel/{name}-{timestamp} branches, merges with conflict detection. NOT for user feature branches (use git worktree directly).
mk-workflow-orchestrator
Auto-invoked 7-phase workflow for complex-feature intent; fasttrack mode for pre-approved specs. NOT for explicit single tasks (mk:cook), green-field builds (mk:autobuild), or simple fixes (mk:fix).
mk-web-to-markdown
Fetch a URL and return clean markdown, for arbitrary external pages (blog, RFC, GitHub issue, vendor doc) not covered by mk:docs-finder. Static-only by default; opt-in JS rendering available.
mk-vulnerability-scanner
Vulnerability analysis: OWASP Top 10, current threat landscape, supply chain security, attack surface mapping, risk prioritization. Use for security audits. NOT for STRIDE/CSO infra audits (mk:cso).
mk-vue
Vue 3 authoring/review: components, composables, reactivity, Pinia, Pinia Colada, file routing, forms. Composition API + script setup. Auto-activates on .vue files. Deep review: mk:vue-best-practices.
mk-vue-testing-best-practices
Vue 3 testing best-practices review: Vitest + Vue Test Utils for components, composables, Pinia, Router, async/Suspense, forms, a11y, plus Playwright E2E strategy. Advisory only.