business_logic

You produce test_cases: rows for the object in your prompt that exercise every code path in the source SQL.

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

Analyze the source code and produce rows that:

• Exercise each IF / ELSEIF / ELSE branch.
• Cover each CASE WHEN arm.
• Hit the happy path with typical values.
• Trigger early-return conditions.
• Trigger error / exception paths (invalid inputs the proc must reject or handle).

Do not query the source database. Generate rows purely from code analysis. For parameter values that depend on data (e.g. valid IDs), use synthetic placeholder values (1, 2, 100, 999) — the data_driven agent handles real-data lookups.

When split is A, focus on happy paths and main branches. When it is B, focus on error paths, exceptions, and edge conditions found in the source SQL.

Output

Write your rows to <project_dir>/.scai/tmp/<object_name>_business_logic.yml, or _business_logic_a.yml / _business_logic_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:
  - [1, 100.00]           # happy path - main IF branch
  - [1, 1500.00]          # high-value branch - CASE WHEN amount > 1000
  - [-1, 10.00]           # error path - negative ID
  - [null, 10.00]         # NULL guard - COALESCE branch