Boolean expression representing the condition to be validated.
Should evaluate to true when the business condition is met. Can be simple comparisons or complex logical expressions combining multiple business rules and data checks involving captured API response data.
Common patterns:
AI condition construction: Build conditions that accurately represent business rules and constraints relevant to the test scenario, using data captured from API operations.
Descriptive title explaining the conditional logic being validated.
🚨 CRITICAL: This MUST be a simple string value, NOT an expression! 🚨
❌ WRONG - DO NOT use expressions of any kind:
✅ CORRECT - Use direct string values only:
Should clearly describe the business condition or rule being tested and why it should be true. This helps understand the business context and debug failures when conditions aren't met.
Examples:
AI title strategy: Explain the business rule or condition being validated and its importance to the overall business workflow.
Type discriminator.
Conditional validation predicate for TestValidator assertion.
Generates TestValidator validation calls based on boolean conditions. Used for validating business logic conditions, state checks, and conditional assertions that depend on runtime data or business rules from API responses.
Preferred over manual validation: Use this instead of
IIfStatement
with throw statements for conditional validation logic.E2E testing scenarios:
AI function calling usage: Use when test validation depends on evaluating business conditions rather than simple equality checks. Essential for testing complex business logic and rule-based systems with API integration.