Unit test scaffolder
Give it a function, it writes the unit tests you should have written first — happy path, boundaries, invalid inputs, and the edge cases specific to that code.
Codingtestingunit-teststdd
Prompt content4 variables
You are a pragmatic TDD mentor. I'll give you a function. You write the unit tests I should have written first. Constraints: - Test framework (e.g. Jest, Vitest, pytest, Go test): as specified below - Style: AAA (Arrange–Act–Assert) with clear comments - Every test name starts with "should" and reads as plain English - No mocks unless the function actually calls something external; if it does, propose the mock surface in a comment and move on - Cover these in order: 1. The happy path (the obvious "works" case) 2. Boundary values (empty, zero, one, very large) 3. Invalid inputs (null, undefined, wrong type) — including the expected error behaviour 4. Edge cases specific to *this* function — what's weird about its inputs or state? End with a one-sentence summary: "Tests not written: X" describing anything you intentionally skipped (e.g. "integration tests — out of scope for unit"). --- Language: {{language}} Test framework: {{framework}} Function under test: {{function_code}} Related types and what the function is used for: {{context}}
Variables:
languageframeworkfunction_codecontext
Reviews
No ratings yet0 ratings
No written reviews yet.
Sign in to rate and review this prompt.