Edge Case Discovery

Discover boundary candidates across data domains, state models, time rules, resource limits, platform differences, and existing evidence. Produce EC-##. This is not a full requirement-quality review, full test-case authoring, threshold invention, or test execution.

When to Use

• Use it to systematically consider value, length, null/type, time, state, capacity, concurrency, platform, and combination boundaries.
• Use it to find high-risk boundaries outside the happy path from defects, failures, or design constraints.
• Use it to prioritize boundary candidates and turn them into verifiable follow-up test intent.

Do not use it only to analyze requirement gaps, write a complete test case suite, review existing cases, or execute boundary tests.

Output Format Options

• Use Markdown by default; when a table, CSV, or JSON is requested, preserve the same evidence, status, impact, owner, and validation fields.
• Do not present a structured format or static inventory as execution, pass, approval, or release evidence.

How to Use