Interface IIfStatement

Conditional statement for business rule-based test flow control.

Enables test scenarios to branch based on runtime conditions or business rules. This should be used for genuine business logic branching where different test paths are needed based on data state or business conditions.

IMPORTANT: For validation purposes, prefer predicate expressions instead:

• Use IEqualPredicate instead of if (x === y) throw new Error(...)
• Use INotEqualPredicate instead of if (x !== y) throw new Error(...)
• Use IConditionalPredicate instead of if (!condition) throw new Error(...)
• Use IErrorPredicate instead of if blocks that only contain error throwing

Only use IIfStatement when:

• Different business logic paths are needed (not just validation)
• Complex conditional workflows that can't be expressed as simple predicates
• Role-based or feature-flag dependent test scenarios
• Multi-step conditional operations where predicates are insufficient

Business scenarios requiring conditional logic:

• Role-based test flows (premium vs regular customers)
• Feature availability testing with different user journeys
• Optional business process steps based on entity state
• Complex workflow branching that involves multiple operations per branch

AI function calling strategy: First consider if the validation can be handled by predicate expressions. Use IIfStatement only when genuine business logic branching is required that cannot be expressed through predicates.