Testing language behavior#

Tests should scale with the risk of the change. Configuration-driven rules need coverage for both the configured success path and closed failure path.

For test block syntax, context values, assertions, expectations, setup, and teardown, see Test declarations.

Required coverage for policy rules#

When adding a new configuration-driven rule, include e2e coverage for:

• Successful resolution of a valid configuration row.
• Missing required configuration.
• Ambiguous or invalid configuration when the resolver can encounter it.
• Unsupported enum or action values.

Strict input behavior#

Invalid input should return an actionable error. It should not be treated as a partial success.

Language-agnostic packages#

Do not add business-specific test shims to shared language packages. If a Business Language case fails, fix the grammar, compiler, runtime, or BL source layer that owns the behavior.