Array of argument expressions passed to the function.
Each argument must match the expected parameter type of the called function. Order and types must correspond exactly to the function signature defined in utility or validation documentation.
Common patterns:
AI validation: Ensure argument types and count match the target function's signature exactly, excluding API functions.
Expression representing the function to be called.
Should NOT represent API/SDK functions - use IApiOperateStatement
for those instead.
Typically represents utility functions:
Can also be a simple identifier for direct function references.
AI requirement: Must NOT resolve to SDK API functions. Those should use the dedicated API function call statement type.
Type discriminator.
Function call expression for non-API function invocations and utility calls.
IMPORTANT: For API function calls, use
IApiOperateStatementinstead. This type should only be used for:Essential for E2E testing for utility operations, but API calls should use the dedicated
IApiOperateStatementfor proper handling of business operations and response capturing.AI function calling importance: This represents utility and validation operations in test scenarios, but should NOT be used for SDK API calls which have their own dedicated statement type.