AgentStack
SKILL verified MIT Self-run

Test Generator

skill-sourav15mukherjee-skillforge-free-skills-test-generator · by sourav15mukherjee

>-

No reviews yet
0 installs
10 views
0.0% view→install

Install

$ agentstack add skill-sourav15mukherjee-skillforge-free-skills-test-generator

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Test Generator? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Test Generator

Generate thorough test suites by analyzing source code and producing tests that cover happy paths, edge cases, and error scenarios.

Workflow

  1. Detect the testing framework

Look for configuration files and existing tests:

  • jest.config.* or vitest.config.* → Jest/Vitest
  • pytest.ini or conftest.py → Pytest
  • *_test.go files → Go testing
  • *.test.ts, *.spec.ts → TypeScript testing

Also check package.json for test scripts and dependencies.

  1. Read the source code

Read the file(s) the user wants tested. Understand:

  • Function signatures and return types
  • Dependencies and imports
  • Side effects (API calls, DB queries, file I/O)
  • Edge cases (null inputs, empty arrays, boundary values)
  1. Read existing tests (if any)

Check for existing test files to match style and avoid duplication.

  1. Generate tests covering:
  • Happy path: Normal expected behavior with typical inputs
  • Edge cases: Empty inputs, null/undefined, boundary values, large inputs
  • Error handling: Invalid inputs, thrown exceptions, rejected promises
  • Integration points: Mock external dependencies appropriately
  1. Write the test file

Follow the project's naming convention (e.g., foo.test.ts or test_foo.py).

Rules

  • Match the existing test style in the project
  • Use descriptive test names: it("should return empty array when input is null")
  • Group related tests with describe blocks
  • Mock external dependencies (APIs, databases) — never call real services
  • Include setup/teardown when needed
  • Aim for 80%+ code coverage of the target file
  • Add comments explaining WHY a test exists for non-obvious cases
  • Always run the tests after generating to verify they pass

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.