Descriptive title explaining what inequality is 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 why the values should NOT be equal or what difference is expected. This helps with understanding test intent and debugging failures.
Examples:
AI title strategy: Focus on the business reason for the inequality check and what change or difference is being validated.
Type discriminator.
First value expression for comparison.
Typically represents the original value, previous state, or value that should be different from the second expression. Often captured from earlier API operations or represents a baseline state.
Common patterns:
Second value expression for comparison.
Represents the new value, current state, or value that should differ from the first expression. Often the result of API operations or updated data captured from API responses.
Common patterns:
Inequality validation predicate for TestValidator assertion.
Used for negative validations and ensuring values have changed or differ from previous states.
Preferred over manual validation: Use this instead of
IIfStatement
with throw statements for inequality checking.E2E testing scenarios:
AI function calling usage: Use when business logic requires confirming differences or ensuring values have been modified by API operations. Important for testing update operations and data transformations.