Skip to content
Skills Library
Programming · Testing

qa-unit-testing

/qa-unit-testing

Creates unit tests for isolated functions and modules. Use when testing utility functions or pure logic in isolation with mocked dependencies. Not for test-first React component development (use test-first-react).

Repository
vibe.md ↗
Licence
MIT
Last repository change
13.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Creates unit tests for isolated functions and modules. Use when testing utility functions or pure logic in isolation with mocked dependencies. Not for test-first React component development (use test-first-react).

Original author description

Creates unit tests for isolated functions and modules. Use when testing utility functions or pure logic in isolation with mocked dependencies. Not for test-first React component development (use test-first-react).

How it works

  1. Purpose
  2. When to Use
  3. Step-by-Step Instructions
  4. Examples
Original SKILL.md headings · 20 lines, 183 words
SKILL.md preview
---
name: qa-unit-testing
description: Creates unit tests for isolated functions and modules. Use when testing utility functions or pure logic in isolation with mocked dependencies. Not for test-first React component development (use test-first-react).
metadata:
  collection: vibe.md
  group: qa
---

# QA Unit Testing

## Purpose
Tests individual functions, utilities, and modules in isolation with mocked dependencies.

## When to Use
- Writing unit tests for pure functions, algorithms, and isolated application logic.

## Step-by-Step Instructions
1. **Locate Test Framework:** Identify the project's test runner (e.g., Jest, Vitest, PyTest) and test execution command.
2. **Analyze Logic:** Identify inputs, expected outputs, pure functions, and edge conditions.
3. **Setup Mocks:** Explicitly mock external dependencies, databases, network calls, and timers to isolate the unit under test.
4. **Implement Tests:** Write unit tests covering happy paths, negative inputs, and boundary values.
5. **Execute & Verify:** Run the test suite using the project's CLI command to confirm passing tests.
6. **Stop Condition:** If a unit test fails due to a bug in the target code, stop and report the bug to the user. Do NOT modify the target code logic or weaken test assertions without explicit user instructions.

## Examples
**User:** "Add unit tests for `formatCurrency`."
**Agent:** Identifies Jest runner, creates test cases covering positive values, zero, negative numbers, and invalid inputs, runs Jest, and verifies all pass.

Versions

The database has no other skills named qa-unit-testing.

Database snapshot: 13.11.2026 · package version e308e4d95446 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 2 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100uw-analyze-unit-tests
    Use when analyzing unit test coverage, patterns, and test code for isolated component testing
  • 100generating-unit-tests
    Test automatically generate comprehensive unit tests from source code covering happy paths, edge cases, and error conditions. Use when creating test coverage for functions, classes, or modules. Trigger with phrases like "generate unit tests", "create tests for", or "add test coverage".
  • 100generating-unit-tests
    Test automatically generate comprehensive unit tests from source code covering happy paths, edge cases, and error conditions. Use when creating test coverage for functions, classes, or modules. Trigger with phrases like "generate unit tests", "create tests for", or "add test coverage".
  • 95unit-testing
    Use when writing unit tests for a function or module, mocking external dependencies, practising TDD on new business logic, or enforcing a coverage target across a codebase in Python, TypeScript, or Go.
  • 95move-unit-testing
    Use when writing unit tests for Move smart contracts on Sui. Applies to test function naming, assertions, test attributes, context usage, and cleanup patterns. Use whenever user asks to write tests, add tests, or test a Move module.
  • 90integration-testing
    Tests that components work together — service against real database, API against real dependencies, module against module. Use this whenever the user mentions integration tests, testing against a real database or queue, contract testing between services, or has unit tests…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.