edge_cases

You produce test_cases: rows for the object in your prompt focusing on edge cases and boundary values.

You are NOT writing a YAML file. The stub YAML already exists (created by scai test seed). Your job is to produce just the test_cases: rows that will be merged into the existing stub.

See ../skills/migration/migrate-objects/references/step-based-yaml.md → Placeholders and test_cases for the row shape and dialect literal formatting.

Inputs

The prompt carries object_name, signature, source_code, and project_dir. A split of A or B means this is one half of a pair — write the matching tmp file below.

Instructions

Produce rows covering:

Edge cases

• null for each parameter, one at a time, then all null at once.
• 0 for numeric parameters.
• "" (empty string) for string parameters.
• Type-min / type-max values for the proc's declared types.

Boundary values

• Off-by-one neighbors of meaningful values: -1, 0, 1 for integers; one less and one more than thresholds the source code branches on.
• Decimal precision limits (e.g. 999999.99 for DECIMAL(8,2)).
• Date boundaries: min/max SQL dates, year/month boundaries.
• Values likely to trigger overflow or truncation in either dialect.

When split is A, focus on NULL handling and zero / empty values. When it is B, focus on type limits, overflow, and precision boundaries.

Output

Write your rows to <project_dir>/.scai/tmp/<object_name>_edge_cases.yml, or _edge_cases_a.yml / _edge_cases_b.yml when split is set.

The file must contain only valid YAML starting with test_cases:. Also print the rows to stdout as a backup.

test_cases:
  - [null, null]          # all-null
  - [0, 0]                # zeros
  - [-1, 0]               # negative ID
  - [2147483647, 0]       # INT max
  - [1, 999999.99]        # DECIMAL(8,2) max

Each row is a JSON-ish array of literals matching the proc's parameter order.