The simple identifier name being referenced.
Must be a SIMPLE identifier name (single word) that corresponds to a valid identifier in the current scope:
Should NOT reference API functions directly. Use IApiOperateStatement for API operations instead.
MUST NOT contain dots, brackets, or any compound access patterns. For compound access, use IPropertyAccessExpression or IElementAccessExpression.
Examples:
✅ CORRECT - Simple identifiers:
❌ WRONG - Compound expressions (use other expression types):
AI naming consistency: Must match exactly with variable names from previous IApiOperateStatement.variableName. Keep it simple - just the variable name, nothing more.
Type discriminator.
Identifier expression for referencing variables and utility functions.
Represents references to previously captured variables from API operations, imported utility functions, or global identifiers. Essential for data flow in test scenarios where values from earlier API operations are used in later operations.
IMPORTANT: Should NOT reference API functions directly. API operations should use
IApiOperateStatement
instead.🚨 CRITICAL: SIMPLE IDENTIFIERS ONLY! 🚨
This interface is ONLY for simple identifiers (single variable names). DO NOT use compound expressions like:
❌ WRONG - These are NOT simple identifiers:
Array.isArray
(use IPropertyAccessExpression instead)user.name
(use IPropertyAccessExpression instead)items[0]
(use IElementAccessExpression instead)console.log
(use IPropertyAccessExpression instead)Math.random
(use IPropertyAccessExpression instead)x.y?.z
(use chained IPropertyAccessExpression instead)✅ CORRECT - Simple identifiers only:
seller
(variable name from IApiOperateStatement)product
(variable name from IApiOperateStatement)Array
(global constructor name)console
(global object name)Math
(global object name)For compound access, use the appropriate expression types:
IPropertyAccessExpression
(e.g.,user.name
)IElementAccessExpression
(e.g.,items[0]
)ICallExpression
withIPropertyAccessExpression
for the functionCommon E2E testing usage:
AI function calling context: Use when referencing any simple named entity in the test scope, excluding direct API function references which should use dedicated statement types. For any property access or method calls, use the appropriate expression types instead.