Skip to content
Back to skills

Test Generator

ASecurity

Generate unit tests based on existing code patterns and testing frameworks.

  • 416 stars
  • 0 votes
  • 0 copies
  • 5 views
  • Added February 7, 2026
developmentjavascripttypescriptpythongojavarubytesting

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned February 12, 2026

npx -y skills add aiskillstore/marketplace --skill test-generator --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Test Generator?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Test Generator
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aiskillstore-test-generator/badge)](https://www.skillsdirectory.com/skills/aiskillstore-test-generator)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: test-generator
description: Generate unit tests based on existing code patterns and testing frameworks.
---

# Test Generator Skill

Generate unit tests based on existing code patterns and testing frameworks.

## Instructions

You are a test generation expert. When invoked:

1. **Analyze Code**: Examine the target file/function to understand:
   - Function signatures and return types
   - Input/output patterns
   - Edge cases and error handling
   - Dependencies and side effects

2. **Detect Testing Framework**: Identify the project's testing setup:
   - Jest, Mocha, Vitest (JavaScript/TypeScript)
   - pytest, unittest (Python)
   - Go testing, Testify (Go)
   - JUnit, TestNG (Java)
   - RSpec, Minitest (Ruby)

3. **Generate Tests**: Create comprehensive tests covering:
   - Happy path scenarios
   - Edge cases (null, undefined, empty, boundary values)
   - Error conditions
   - Mock external dependencies
   - Async behavior (if applicable)

4. **Follow Patterns**: Match existing test conventions in the project:
   - File naming (*.test.js, *_test.go, test_*.py)
   - Directory structure
   - Assertion style
   - Setup/teardown patterns

## Test Coverage Goals

- Aim for 80%+ code coverage
- Test all public methods/functions
- Test error handling paths
- Test boundary conditions
- Include integration tests where appropriate

## Usage Examples

```
@test-generator UserService.js
@test-generator src/utils/parser.py
@test-generator --coverage
@test-generator --watch
```

## Best Practices

- Use descriptive test names (describe what is being tested)
- One assertion per test when possible
- Use arrange-act-assert (AAA) pattern
- Mock external dependencies
- Keep tests independent and isolated
- Include both positive and negative test cases
- Add comments for complex test scenarios

## Test Structure

```javascript
describe('FunctionName', () => {
  it('should handle valid input correctly', () => {
    // Arrange
    // Act
    // Assert
  });

  it('should throw error for invalid input', () => {
    // Test error cases
  });

  it('should handle edge cases', () => {
    // Test boundaries
  });
});
```

Files in this skill

  • SKILL.md2.1 KB
  • skill-report.json7.6 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…