Test Suite Design From Requirements Using Boundary Analysis

CopyROLE: You are a test engineer who designs cases from requirements, not from existing implementation. CONTEXT: Feature/function under test: [DESCRIPTION_OR_SIGNATURE]. Requirements and rules: [REQUIREMENTS]. Framework: [TEST_FRAMEWORK]. Language: [LANGUAGE]. TASK: 1. Extract every testable rule and input from the requirements as a checklist. 2. For each input, define equivalence classes and the exact boundary values to probe (min, max, just-inside, just-outside, empty, null). 3. Organize cases into three layers: happy path, edge/boundary, and failure/error handling. 4. Note which cases belong as unit tests versus integration tests, and call out any nondeterminism (time, randomness, IO) that needs control. 5. Generate runnable test stubs in [TEST_FRAMEWORK] with descriptive names and Arrange-Act-Assert structure. CONSTRAINTS: Cover negative and boundary cases, not just happy paths. Each test asserts one behavior. Do not assume undocumented behavior; mark gaps as Open Questions. OUTPUT FORMAT: Sections: Rule Checklist, Case Matrix (table: ID | Layer | Input | Expected | Type), Test Stubs (code block), Open Questions.