Test Case Generator

Turn the supplied inputs into **test case generator**. Optimize for the person searching “test case generator prompt”: they need a clear result, the reasoning that affects it, and an obvious next step.

## Situation to solve — Test Case Generator
- [ACTUAL_BEHAVIOR] — for Test Case Generator, supply the relevant actual behavior. If unavailable, label [ACTUAL_BEHAVIOR] `unknown`; never infer it.
- [CONSTRAINTS] — for Test Case Generator, supply the relevant constraints. If unavailable, label [CONSTRAINTS] `unknown`; never infer it.
- [LANGUAGE] — for Test Case Generator, supply the relevant language. If unavailable, label [LANGUAGE] `unknown`; never infer it.
- [EXPECTED_BEHAVIOR] — for Test Case Generator, supply the relevant expected behavior. If unavailable, label [EXPECTED_BEHAVIOR] `unknown`; never infer it.
- [REPRODUCTION_STEPS] — for Test Case Generator, supply the relevant reproduction steps. If unavailable, label [REPRODUCTION_STEPS] `unknown`; never infer it.
- [CODE] — for Test Case Generator, supply the relevant code. If unavailable, label [CODE] `unknown`; never infer it.
- [SELECTION_CRITERIA] — for Test Case Generator, supply the relevant selection criteria. If unavailable, label [SELECTION_CRITERIA] `unknown`; never infer it.
- [REPOSITORY_CONTEXT] — for Test Case Generator, supply the relevant repository context. If unavailable, label [REPOSITORY_CONTEXT] `unknown`; never infer it.

## How to work — Test Case Generator
1. Generate options from explicit constraints, then filter them instead of presenting an undifferentiated list.
2. Rank the strongest options and explain fit, risk, and the next validation step.
3. Trace observable behavior through the relevant code path before editing anything.
4. Provide the smallest defensible patch, regression tests, and exact verification steps.
5. Show a minimal change before optional refactoring.
6. Include tests that would fail before the correction.
7. Reproduce or reason from the observed failure before proposing a fix.
8. Identify the smallest causal code path.
9. Boundary for Test Case Generator: Do not invent APIs, packages, files, runtime behavior, command output, or successful test results.

## Make the answer usable — Test Case Generator
- **Technical finding for Test Case Generator** — test case generator prompt evidence → Test Case Generator; omit preamble.
- **Evidence or reproduction for Test Case Generator** — material inputs for Test Case Generator, each connected to test case generator prompt.
- **Minimal change for Test Case Generator** — ready-to-use Test Case Generator, formatted for test case generator prompt.
- **Test coverage for Test Case Generator** — Test Case Generator weak points, unknowns, and test case generator prompt limits.
- **Verification command for Test Case Generator** — test case generator prompt → verify Test Case Generator before use.

## Integrity check — Test Case Generator
Before returning the Test Case Generator, remove filler, label every unresolved fact, and verify that each recommendation connects to a supplied goal.