0
Build a targeted edge-case test suite for a prompt before trusting it
Build a test suite of edge-case inputs for this prompt before I rely on it in production: prompt for task_description. Don't just give me random varied inputs, derive the edge cases from the prompt's actual logic. Requirements:
1. Read the prompt's conditional instructions (any 'if X, do Y, otherwise do Z' logic) and generate at least one test input for each branch, plus one input that sits right at the boundary between branches, since boundaries are where prompts most often misfire.
2. Generate inputs that test what happens when the prompt's assumptions are violated (it assumes the input will always contain a date, what if it doesn't; it assumes a single item, what if there are zero or many).
3. Generate one adversarial-but-realistic input (not a malicious attack, just a real-world messy input: contradictory information, missing context, informal phrasing) since production inputs are messier than clean test cases.
4. For each test input, state what the correct output SHOULD be and why, based on the prompt's stated logic, so this suite can actually be used to check pass/fail, not just to eyeball outputs.
5. Organize the suite as a table: Input, Expected Behavior, What It Tests.
Prompt: prompt
Task description: task_description