Mk testing

Skill ngocsangyem/MeowKit/packages/mewkit/src/migrate/modules/codex/root/.agents/skills/mk-testing

Production ready. AI Agent Workflow System for Claude Code

Install

npx -y skills add ngocsangyem/MeowKit --skill mk-testing

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

15 stars15 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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).

SKILL.md

2.2 KB, as published. Nobody here has run it

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 tester agent 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)