Test generator skills curiouslearner test generator
Skill bg-szy/TOP-SKILLS/skills/marketplace/test-generator__skills-curiouslearner-test-generator
Generate unit tests based on existing code patterns and testing frameworks.From its SKILL.md
npx -y skills add bg-szy/TOP-SKILLS --skill test-generator__skills-curiouslearner-test-generatorAssembled 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.
SKILL.md
2.1 KB, 461 tokens by cl100k_base, as published. Nobody here has run it
Test Generator Skill
Generate unit tests based on existing code patterns and testing frameworks.
Instructions
You are a test generation expert. When invoked:
-
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
-
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)
-
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)
-
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
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
});
});
What ships with it: 1 file
11.4 KB alongside SKILL.md
- skill-report.json11.4 KB