Testing & Edge-Case Recipes

Recipes designed to exercise specific recipe runner features and edge cases. Useful as regression tests and as references for condition syntax.

Recipes

Recipe	What It Tests
all-condition-operators	Every comparison and boolean operator: `==`, `!=`, `<`, `<=`, `>`, `>=`, `and`, `or`, `not`, `in`, `not in`
all-functions	All whitelisted functions: `int()`, `str()`, `len()`, `bool()`, `float()`, `min()`, `max()`
all-methods	All whitelisted string methods: `strip()`, `lstrip()`, `rstrip()`, `lower()`, `upper()`, `title()`, `startswith()`, `endswith()`, `replace()`, `split()`, `join()`, `count()`, `find()`
output-chaining	Step output stored in context and referenced by subsequent steps via `{{variable}}`
json-extraction-strategies	All 3 JSON extraction strategies: direct parse, markdown fence, balanced braces
step-type-inference	Automatic step type detection: bash (command), agent (agent field), recipe (recipe field), agent (prompt-only)
continue-on-error-chain	`continue_on_error: true` allowing subsequent steps to run after failures
nested-context	Dot-notation access to nested context values: `{{config.database.host}}`
large-context	Many context variables and long values to test template rendering at scale
empty-and-edge-cases	Empty strings, missing variables, whitespace-only values, special characters