Test Master
Generates test files, designs mocking strategies and test architectures, analyzes coverage gaps, and produces test plans and defect reports across functional, performance.
Before & after
Same prompt, same agent — the only difference is the skill.
I can write tests for your cart calculation function. Generally, you'll want to test the basic cases like adding items and calculating totals. You should probably also think about edge cases, though the specifics depend on your implementation. Some people use Jest, others use Vitest or Mocha—whatever you prefer. Would it help if I also wrote tests for discounts? And do you have any special requirements like tax handling or shipping? Let me know what framework you're using and I can provide more targeted guidance.
TEST SUITE: CartTotal.test.js UNIT TESTS (5 essential cases) • Base case: 2 items × $50 = $100 ✓ • Empty cart returns $0 ✓ • Negative quantity rejected (validation layer, not calculation) ✓ • Floating point precision (three items at $33.33 each vs $100 total) ✓ • Currency override (EUR vs USD formatting, not calculation—mocked) ✓ MOCKING STRATEGY • Tax calculator: stub return 18% for all inputs • Shipping API: return fixed $9.99 per call (predictable test data) • Exchange rate service: mock at 1.1 EUR/USD (no live calls in test suite) COVERAGE GAPS • Edge case: coupon with $0 discount applied (tests discount presence, not absence) • Boundary: 99 items (tests array length limit) vs 1 item (minimum) • Integration risk: discount + tax interaction not isolated—add parameterized test FLAKY TEST PREVENTION • No floating point equality (use toBeCloseTo with 2 decimal places) • No time-dependent assertions (freeze Date.now via sinon.useFakeTimers) • No async without await or async/await syntax ESTIMATED COVERAGE: 87% (missing coupon.expiry interactions; add 2 more tests)
About this skill
name: test-master description: Use when Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing...
Test Master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation frameworks; analyzing coverage gaps; performance testing with k6 or Artillery; security testing with OWASP methods; debugging flaky tests; or working on QA, regression, test automation, quality gates, shift-left testing, or test maintenance.
What you get
- Public GitHub repo
- the skills/test-master folder with SKILL.md and references.
Customize your output
- Fork the repo and extend the skill's reference files for your own stack conventions.
Example output
Activates on a matching request (e.g. building or reviewing Test Master code) and can chain with other skills in the pack.
Best for
Full-stack developers and engineering teams using Claude Code.
SKILL.md preview
---
name: test-master
description: Use this skill when writing tests, designing test architectures, analyzing coverage gaps, or running functional, performance, and security testing.
version: 1.0.0
category: Development / Testing
author: AgentVolt
license: proprietary
tags:
- development
- testing
---
# Test Master
Generates test files, designs mocking strategies and test architectures, analyzes coverage gaps, and produces test plans and defect reports across functional, performance, and security disciplines.
## When to use
… (sign up to view the full skill)More development skills
View all Development skills →Playwright
Gives Claude autonomous headless browser control — it spins up a browser, clicks through your UI, checks everything works, and fixes broken tests.
Claude TDD Skill
Forces Claude Code to write a failing test before writing any implementation code.
Playwright Expert
Use when writing E2E tests with Playwright, setting up test infrastructure, or debugging flaky browser tests.
Debugging Wizard
Parses error messages, traces execution flow through stack traces, correlates log entries to identify failure points, and applies systematic hypothesis-driven methodology to isolate and resolve bugs.