AutoBE
    Preparing search index...

    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:

    • Verifying values have changed after update API operations
    • Confirming different entities have different identifiers
    • Ensuring sensitive data is not exposed in API responses
    • Validating that values are NOT of unexpected types

    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.

    interface INotEqualPredicate {
        title: string & MinLength<1>;
        type: "notEqualPredicate";
        x: IExpression;
        y: IExpression;
    }
    Index

    Properties

    Properties

    title: string & MinLength<1>

    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:

    • { type: "binaryExpression", operator: "+", left: "Value", right: " should differ" }
    • { type: "stringLiteral", value: "some string" }
    • Any IExpression types - this is NOT an expression field!

    ✅ CORRECT - Use direct string values only:

    • "Updated product name should differ from original"
    • Simple, complete descriptive text as a raw string

    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:

    • "Updated product name should differ from original"
    • "New order ID should not match previous order"
    • "Modified review should have different content"
    • "Response should not contain sensitive password data"

    AI title strategy: Focus on the business reason for the inequality check and what change or difference is being validated.

    type: "notEqualPredicate"

    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:

    • Original values before update API operations
    • Different entity identifiers from API responses
    • Previous state values captured from earlier API calls
    • Baseline data for comparison

    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:

    • Updated values after modification API operations
    • Current entity states from API responses
    • New data from API responses
    • Transformed or processed values