Name: Test Suite Generator — Risk-First Unit Tests (Jest, Vitest, Pytest, JUnit, Go)
Price: 12 USD
Availability: InStock
Author: Agensi

See it in action

You say

Product: SeatHold venue seat holds TypeScript + Vitest Function: evaluateHold(heldAtMs, nowMs, holdMinutes, seatsRequested, seatsAvailable) Returns: { status: "active" | "expired" | "invalid", reason, expiresAtMs } Ask: solid unit suite; edge cases matter

Your agent does

Coverage confidence: STRONG Tests generated: 18 (Vitest, unit) Critical paths covered: yes

Plan highlights:

CRITICAL: nowMs === expiresAtMs → expired
CRITICAL: seatsRequested > seatsAvailable → invalid
HIGH: active mid-window + expiresAtMs contract

Generated: holdWindow.test.ts with it.each tables, fixed epoch clocks Run: npx vitest run src/lib/holdWindow.test.ts JSON: framework vitest, tests_generated 18, critical_paths 5/5

What you get

Add unit tests for a pure function or module with no coverageExpand edge-case coverage on critical path logicGenerate Jest/Vitest/Pytest/JUnit/Go tests that match project conventionsGet a prioritized test plan before writing any assertionsPair with a bug fix: ship a regression-oriented suite for the touched unit

About this skill

The problem

Blank “write some tests” prompts produce shallow happy-path cases and miss the edges where production breaks.
Teams need a plan for what to test and why — not only a pile of assertions.
Framework style matters: Jest, Vitest, Pytest, JUnit 5, and Go testing each have different idioms.

What it does

Analyzes a function, module, or class and builds a risk-prioritized test plan.
Enumerates edge cases (boundaries, invalid input, empty values, error paths, and more).
Generates idiomatic test code for the detected framework (Jest, Vitest, Pytest, JUnit 5, or Go testing).
Reports missing coverage honestly and lists what to add next.
Provides exact run commands and a machine-readable Test Suite JSON.

Frameworks & tools

JavaScript/TypeScript: Jest or Vitest (describe/it, it.each, spies).
Python: Pytest (fixtures, parametrize, raises).
Java: JUnit 5 (parameterized tests, clear display names).
Go: table-driven tests with testing (and testify only if already used).
Works from pasted code or repo paths your agent can read — no SaaS test cloud required.

Why this beats prompting it yourself

Risk-first priorities (CRITICAL/HIGH first) instead of random examples.
A full edge-case taxonomy so boundaries and invalid input are not forgotten.
Anti-pattern guardrails: no over-mocking, no always-pass asserts, no implementation-detail tests.
Framework-aware idioms instead of generic pseudocode.
Review-before-write: tests are draft artifacts until you approve saving them.