testgen_skill
- Shell
8
GitHub Stars
3
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill 0xdarkmatter/claude-mods --skill testgen- frameworks.md18.0 KB
- SKILL.md8.1 KB
- visual-testing.md4.6 KB
Overview
This skill generates comprehensive tests with automatic framework detection, expert agent routing, and auto TaskCreate to verify results. It matches project conventions and creates test files in the correct locations, covering happy paths, edge cases, and error handling. The tool supports multiple languages and test runners and integrates with a task system to run and review generated tests.
How this skill works
Given a target file, function, or directory, the skill analyzes source code, finds existing tests to avoid duplicates, and extracts signatures when available. It detects the project test framework (e.g., jest, pytest, go test, cargo test) and loads project conventions to choose file naming and placement. The system routes work to language-specific expert agents (TypeScript, Python, Go, Rust, PHP, React, Vue, Cypress, etc.), generates focused tests according to requested depth and focus, and auto-creates a verification task for running and reviewing results.
When to use it
- Add unit tests to a new or existing file without manual framework setup
- Generate quick coverage for functions or directories before a refactor
- Create E2E tests or visual checks (with --visual) for UI flows
- Auto-create tasks to run and verify generated tests in CI or locally
- Bootstrap test suites across polyglot repositories
Best practices
- Run framework detection in the repo root so package/config files are available
- Specify --focus (happy|edge|error|all) and --depth (quick|normal|thorough) for predictable output
- Review generated tests before committing and refine edge/error cases manually
- Keep test files co-located or follow the project’s established test layout to avoid clutter
- Use the TaskCreate output to run tests and iterate (/review, /save)
Example use cases
- Generate Jest unit tests for src/utils/helper.ts, placing files per project convention
- Create pytest cases for a specific Python function with parameterized edge inputs
- Produce table-driven Go tests and subtests for pkg/auth/token.go
- Dispatch parallel expert agents to create tests across a multi-language feature directory
- Generate Cypress E2E tests for cypress/ flows or visual checks with Chrome DevTools MCP
FAQ
Common frameworks: Jest, Vitest, Mocha, Cypress, Playwright, pytest, unittest, go test, cargo test, PHPUnit/Pest, and related runners via project config files.
How do I control test scope and thoroughness?
Use --focus (happy, edge, error, all) to choose types of tests and --depth (quick, normal, thorough) to select coverage level and mocking detail.
Can it avoid creating duplicate tests?
Yes. It scans existing test files and naming patterns to skip duplicates and follow existing conventions.