Comprehensive Test Case Generator for Any Function or Feature
Why this prompt matters
Most developers write the happy-path test and call it done. This prompt forces a systematic sweep of the full input space in under a minute, catching the bugs that slip through code review.
What we use it for
Generate a complete test suite for any function or feature — unit tests, edge cases, error scenarios, and integration outlines in one shot.
Prompt
You are an expert software engineer specializing in test-driven development. Given the following function or feature description, generate a comprehensive test suite covering: 1. Unit tests — standard inputs, boundary values, and typical use cases 2. Edge cases — null/undefined inputs, empty arrays/strings, maximum/minimum values 3. Error scenarios — invalid types, out-of-range values, missing required fields, network failures if applicable 4. Integration considerations — interactions with databases, APIs, or external services if mentioned For each test case provide: - A descriptive test name - Preconditions (if any) - Input values - Expected output or behavior - A one-sentence explanation of why this case matters Function/Feature to test: [PASTE YOUR FUNCTION OR FEATURE DESCRIPTION HERE] Language/Framework (optional): [e.g., Python/pytest, JavaScript/Jest, TypeScript/Vitest]
<h2>The Prompt</h2><p>Paste this into Claude, GPT-4, or any capable LLM with your function description:</p><pre><code>You are an expert software engineer specializing in test-driven development. Given the following function or feature description, generate a comprehensive test suite covering:
1. Unit tests — standard inputs, boundary values, and typical use cases 2. Edge cases — null/undefined inputs, empty arrays/strings, maximum/minimum values 3. Error scenarios — invalid types, out-of-range values, missing required fields, network failures if applicable 4. Integration considerations — interactions with databases, APIs, or external services if mentioned
For each test case provide: - A descriptive test name - Preconditions (if any) - Input values - Expected output or behavior - A one-sentence explanation of why this case matters
Function/Feature to test: [PASTE YOUR FUNCTION OR FEATURE DESCRIPTION HERE]
Language/Framework (optional): [e.g., Python/pytest, JavaScript/Jest, TypeScript/Vitest]</code></pre><h2>Example in Practice</h2><p>For a function like <code>getUserById(id)</code> that fetches a user from a database, this prompt produces test cases covering: valid IDs, non-existent IDs, soft-deleted users, malformed UUIDs, database timeout scenarios, and concurrent reads — cases a developer under deadline pressure routinely skips.</p><h2>Tips for Better Results</h2><ul><li><strong>Include the function signature</strong> — even a rough one. Type hints prompt the model to generate type-specific edge cases like passing a string where an integer is expected.</li><li><strong>Mention side effects</strong> — if the function writes to a database or sends an email, say so explicitly. The model will add rollback, idempotency, and duplicate-call scenarios.</li><li><strong>Name your framework</strong> — output shifts from abstract descriptions to actual test code in your chosen syntax (Jest <code>describe/it</code> blocks, pytest fixtures, etc.).</li></ul><h2>Takeaway</h2><p>Thorough test coverage is the most consistently skipped step in shipping software. This prompt turns a 30-minute cognitive exercise into a 30-second one — so there's no longer an excuse to skip it.</p>