The base expression being accessed.
Typically an IIdentifier for the root object, but can be another property access expression for chained access. Represents the object whose property is being accessed.
The property name being accessed.
Must be a valid property name on the base expression's type. Should correspond to actual properties defined in DTO schemas or utility function names.
AI validation requirement: Ensure property exists on the base expression's type according to schema definitions, excluding API paths.
OptionalquestionWhether to use optional chaining (?.) operator.
True: Uses ?. for safe property access (property may not exist) False: Uses . for standard property access (property expected to exist)
E2E testing context: Use optional chaining when accessing properties that might not exist based on business conditions or API variations.
AI decision rule: Use true for optional business data, false for guaranteed response structures and utility function paths.
Type discriminator.
Property access expression for object member navigation.
Enables access to properties of objects, which is fundamental for navigating captured data from API operations, utility namespaces, and business entity relationships in E2E test scenarios.
IMPORTANT: Should NOT be used to construct API function calls. Use
IApiOperateStatementfor all API operations instead.Critical E2E testing patterns:
AI function calling usage: Essential for building dot-notation chains for data access and utility function calls, but NOT for API operations which have their own dedicated statement type.