The Inline Variable Editor allows you to insert and manage variables directly within input fields across your Test Cases. Instead of manually typing variable names with square brackets, you can use an inline suggestion menu to quickly search, select, and insert variables.
Where Can You Use the Inline Variable Editor
The Inline Variable Editor is available in the following areas:
AI Step — use variables in AI-powered test steps
Conditional Step — reference variables in conditional logic
API Step — use variables in URL, Parameters, Headers, Authentication
Copilot Chat — reference variables when writing test instructions
How to Trigger the Variable Menu
There are several ways to open the variable suggestion menu:
Type / (Slash)
Typing / in any supported input field opens the suggestion menu. You can then start typing to filter variables by name.
📝 Note: Typing a space right after / will close the menu (it assumes you are writing regular text). The / inside URLs (like https://) is automatically ignored.
Type [ (Open Bracket)
Typing [ also opens the suggestion menu. This is an alternative trigger for users accustomed to the bracket-based variable syntax.
📝 Note: Typing ] after [ will close the menu (closing bracket detected).
Click the Variable Button
Each input field has a Variable button (brackets icon). Click it to open the suggestion menu without typing any trigger character.
💡 Tip: The button trigger keeps the menu open until you select a variable or dismiss it manually — it will not auto-close on the next keystroke.
Using the Suggestion Menu
Once the suggestion menu is open, you can search and insert variables quickly.
Insert a Variable
Trigger the menu using
/,[, or the Variable buttonA suggestion menu appears listing available variables
Type to filter variables by name
Click on a variable to insert it into the field
💡 Tip: The suggestion menu displays both Project and Environment Variables and Step Variables (extracted or generated in previous steps).
Variable Types in the Suggestion Menu
Variable Type | Source | Description |
Project Variables | Project Settings | Static variables defined in your Project configuration |
Step Variables | Previous Test Steps | Variables generated or extracted during earlier steps in the same Test Case |
Environment Variables | Environment settings | Static variables defined in your environment configuration |
📝 Note: Step Variables are context-aware — only variables from steps that execute before the current step are shown.
Create a Variable Inline
You can create a new variable directly from the editor without leaving the current input field.
Open the suggestion menu
Click Create Variable
Fill in the variable name and value
The new variable is automatically inserted into the field
⚠️ Important: Variable names must follow these rules:
Can only contain uppercase letters, numbers, and underscores (_)
Maximum length of 32 characters
No spaces or special characters allowed
Wrap Text as a Variable
You can select existing text in an input field and convert it into a variable reference.
Select (highlight) the text you want to convert
Click the Wrap as Variable button that appears
The selected text is wrapped as a variable reference
Using Variables in API Steps
The Variable Editor is fully integrated into API Step form fields. You can insert variables into:
URL — reference environment-specific base URLs or endpoints
Parameters — use variables as query parameter values
Headers — insert tokens or dynamic header values
Authentication — reference credentials stored as variables
Body — include variables in request payloads
📝 Note: When a URL contains variable references, URL validation is automatically skipped to avoid false errors.
Understanding Variable Icons and Previews
Each variable in the suggestion menu displays an icon and a value preview to help you quickly identify its type and content.
Icons
Value Previews
The suggestion menu shows a preview of each variable's value underneath its name:
Standard variables: The full value is shown, truncated to 20 characters with an ellipsis (…) if longer
Secret / Credential variables: Only the first 4 characters are shown, followed by
••••••••to mask the restEmpty values: No preview is displayed
💡 Tip: This lets you quickly verify you're selecting the right variable without exposing sensitive data.
Variable Availability by Context
Not all variable types are available in every context. The table below shows which variable types appear in each surface:
Context | Environment URL | Step Variables | Environment Variables | Project Variables |
Copilot Test Case | Yes | No | No | Yes |
Copilot Test Plan | Yes | No | No | Yes |
Test Case Chat | Yes | Yes | Yes | Yes |
AI Step | Yes | Yes | Yes | Yes |
Conditional Step | Yes | Yes | Yes | Yes |
API Step | Yes | Yes | Yes | Yes |
📝 Note: Environment Variables only appear when an environment is selected. Step Variables are context-aware — only variables from steps that execute before the current step are shown.
Variable Display Order
Variables appear in the suggestion menu in the following order:
Environment URL
Step Variables (generated/extracted from previous steps)
Environment Variables (scoped to the selected environment)
Project Variables
If two variables share the same name, the first occurrence wins (following the order above).
Q&A - Troubleshooting
Variable not appearing in suggestions? Make sure the variable is defined in your current Environment or in a previous test step. Step Variables only appear if they come from a step that executes before the current one.
Variable value not resolving? Check that the variable name matches exactly (case-sensitive). Variable names use uppercase letters, numbers, and underscores only.
Other related reads you might find useful:
—> Variables












