Testing strategies including unit tests, integration tests, E2E tests, mocking, coverage analysis, and TDD workflow. Trigger when users need help writing tests, choosing testing frameworks, implementing mocking strategies, or setting up test infrastructure.
Write solid unit tests using property-based testing and mutation testing. Use whenever unit tests are being written, fixed, audited, or reviewed in a TypeScript project; whether the user asks directly or test-writing occurs as a step inside another workflow (TDD, feature implementation, bug fixing, code review). Also…
Testing patterns for Zod schemas using Jest and Vitest. Covers schema correctness testing, mock data generation, error assertion patterns, integration testing with API handlers and forms, snapshot testing with z.toJSONSchema(), and property-based testing. Baseline: zod ^4.0.0. Triggers on: test files for Zod schemas…
Write tests for Redux Sagas using redux-saga-test-plan, runSaga, and manual generator testing. Covers expectSaga (integration), testSaga (unit), providers, partial matchers, reducer integration, error simulation, and cancellation testing. Works with Jest and Vitest. Triggers on: test files for sagas…
Generates comprehensive test suites for code including unit tests, integration tests, and end-to-end tests. Use when creating tests for functions, classes, APIs, or entire modules, covering edge cases, error conditions, and ensuring high code coverage.
Full project test coverage. Analyzes the entire codebase, identifies coverage gaps, and writes tests to achieve 100% coverage (minimum 80%). Ensures every source file with exportable logic has at least one test. Use when the user mentions 'alltest', wants comprehensive testing, or asks for full test coverage.
A guide for documenting and testing an existing software feature or page by studying how its code already works. It creates requirement, design, and test documents that describe the current behavior rather than an imagined future version.
Write and review tests — unit, integration, and E2E — following the Testing Trophy model. Use after writing a feature, after fixing a bug (regression test required), during refactoring (existing tests must continue to pass), or during a quality audit to check overall coverage.
Use when writing or modifying Scala 3 tests with weaver-cats, weaver-discipline, or weaver-scalacheck; covers suites, effects, expectations, resources, and laws.
Use when refactoring TypeScript code whose tests require monkey-patching modules, swapping globals, or stubbing imports (vi.mock, jest.mock, sinon) because collaborators (database, HTTP client, clock, RNG, env, logger) are hardcoded inside the unit. Trigger on requests like "I can't test this without mocking the…
Orchestrate test execution — run unit, integration, and E2E tests, collect coverage reports, and analyze failures. Use when running tests, checking coverage, debugging test failures, or validating code changes before merge.
Run the HUMHUM quality gates that are actually touched by the current diff — frontend typecheck + vitest, and Rust fmt/clippy/test — mirroring CI. Use before marking work done, opening a PR, or when asked to "verify", "check", or "run the gates".
Run the InvenTree Plugin AI Toolkit devcontainer and execute a plugin's test-all.sh. Covers Docker setup, postCreateCommand, server startup, and the lint/unit/integration/frontend-build/E2E layers.
Implement a feature phase by phase from a phased JSON master or Markdown plan. Before each phase, confirm whether to create/run unit tests and whether to run ck:quality, unless explicit flags supply those choices. Supports token-budgeted execution, resumable state, and TDD handoff to ck:test.
Drive a VUnit (HDL unit-testing) project through the vunit-mcp MCP server (vunitstatus, vunitlisttests, vunitlistfiles, vunitcompile, vunitelaborate, vunitruntests, vunitgetreport, vunitgettestlog, vunitgettestwaveform, vunitexportjson, vunittestdependencies). Use when the user asks to run or compile VUnit tests, find…
Run a battery of PCB design-hygiene checks against the board open in EasyEDA Pro, through the easyeda MCP tools, and produce a scored report. Use when the user says "/pcb-lint", "lint the board", "run PCB checks", "check my layout", "is this board ready to fab?", or finishes a PCB layout iteration and is about to…
★not rated 0 3d agoA108 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: