agentsclimarketplace

Unit test generator

Skill WesleySmits/agent-skills/.agent/skills/unit-test-generator

43 production-ready skills for AI coding agents. Works with Claude, GitHub Copilot, Cursor, Windsurf, and Zed.

Install
npx -y skills add WesleySmits/agent-skills --skill unit-test-generator

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

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 5 stars5 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

Generates unit tests for changed files and identifies coverage gaps. Use when the user asks to write tests, generate test suites, check coverage, or mentions Jest, Vitest, Playwright, or Mocha.

SKILL.md

5.7 KB, as published. Nobody here has run it

Unit Test Generator & Validator

When to use this skill

  • User asks to generate tests for a file or function
  • User wants to improve test coverage
  • User mentions Jest, Vitest, Playwright, or Mocha
  • User asks for edge case suggestions
  • User wants to validate existing tests

Workflow

  • Identify changed or target files
  • Detect test framework in project
  • Analyze code to understand testable units
  • Generate test file with appropriate structure
  • Include edge cases and error scenarios
  • Run tests to validate
  • Check coverage if configured

Instructions

Step 1: Identify Target Files

For changed files:

git diff --cached --name-only --diff-filter=ACMR | grep -E '\.(js|jsx|ts|tsx|vue)$' | grep -v '\.test\.|\.spec\.'

For specific file, derive test path:

  • src/utils/format.tssrc/utils/format.test.ts or __tests__/utils/format.test.ts

Step 2: Detect Test Framework

FrameworkConfig FilesTest Pattern
Jestjest.config.*, package.json (jest key)*.test.{js,ts,tsx}
Vitestvitest.config.*, vite.config.**.test.{js,ts,tsx}
Playwrightplaywright.config.**.spec.{js,ts}
Mocha.mocharc.*, package.json (mocha key)*.test.{js,ts}

Check installed framework:

npm ls jest vitest @playwright/test mocha 2>/dev/null

Step 3: Analyze Source Code

Extract testable units:

  • Exported functions and their signatures
  • Class methods and their visibility
  • React/Vue component props and behavior
  • API handlers and their responses
  • Pure functions vs side-effect functions

Identify inputs and outputs:

  • Parameter types and valid ranges
  • Return types and possible values
  • Thrown errors and conditions
  • External dependencies to mock

Step 4: Generate Test Structure

Jest/Vitest template:

import { describe, it, expect, vi } from "vitest"; // or from '@jest/globals'
import { functionName } from "../path/to/module";

describe("functionName", () => {
  it("should handle normal input", () => {
    expect(functionName(validInput)).toBe(expectedOutput);
  });

  it("should handle edge case", () => {
    expect(functionName(edgeInput)).toBe(edgeOutput);
  });

  it("should throw on invalid input", () => {
    expect(() => functionName(invalidInput)).toThrow(ExpectedError);
  });
});

React component template:

import { render, screen, fireEvent } from '@testing-library/react';
import { Component } from '../Component';

describe('Component', () => {
  it('renders with default props', () => {
    render(<Component />);
    expect(screen.getByRole('button')).toBeInTheDocument();
  });

  it('handles user interaction', async () => {
    const onAction = vi.fn();
    render(<Component onAction={onAction} />);
    fireEvent.click(screen.getByRole('button'));
    expect(onAction).toHaveBeenCalledOnce();
  });
});

Playwright E2E template:

import { test, expect } from "@playwright/test";

test.describe("Feature", () => {
  test("should complete user flow", async ({ page }) => {
    await page.goto("/path");
    await page.click('button[data-testid="action"]');
    await expect(page.locator(".result")).toBeVisible();
  });
});

Step 5: Include Edge Cases

Always generate tests for:

  • Boundary values: 0, -1, empty string, empty array, max values
  • Null/undefined handling: missing optional params
  • Type coercion: string numbers, boolean strings
  • Async behavior: resolved, rejected, timeout
  • Error paths: invalid input, network failures, permission denied

Step 6: Run and Validate

Execute tests:

# Jest
npx jest --testPathPattern="<test-file>" --coverage

# Vitest
npx vitest run <test-file> --coverage

# Playwright
npx playwright test <test-file>

# Mocha
npx mocha <test-file>

Step 7: Check Coverage

View coverage report:

# Jest/Vitest generate coverage in ./coverage/
open coverage/lcov-report/index.html

Coverage targets:

  • Statements: 80%+
  • Branches: 75%+
  • Functions: 80%+
  • Lines: 80%+

Mocking Patterns

Mock external modules:

vi.mock("../api", () => ({
  fetchData: vi.fn().mockResolvedValue({ data: "mocked" }),
}));

Mock timers:

vi.useFakeTimers();
vi.advanceTimersByTime(1000);
vi.useRealTimers();

Mock environment:

const originalEnv = process.env;
beforeEach(() => {
  process.env = { ...originalEnv, API_KEY: "test-key" };
});
afterEach(() => {
  process.env = originalEnv;
});

Validation

Before completing:

  • Tests pass without modification to source
  • Edge cases covered
  • Mocks properly reset between tests
  • No flaky async behavior
  • Coverage improved or maintained

Error Handling

  • Framework not installed: Run npm install --save-dev <framework>.
  • Tests fail immediately: Check import paths and module resolution.
  • Mock not working: Ensure mock is defined before import in Jest, or use vi.mock hoisting in Vitest.
  • Coverage not generating: Add --coverage flag and check config for coverage settings.
  • Unsure about command: Run npx <framework> --help.

Resources

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.