You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can also convert a hard-coded value in a Manual Interaction step into a Parameter directly — without deleting or re-recording the step. This flow is available on both **Desktop** and **Mobile App** Manual Interaction sessions.
77
+
78
+
1. Open the recorded Manual Interaction step.
79
+
2.**Select the portion** of the instruction text you want to parameterize (for example, highlight `test.com`).
3. In the **Convert as** popover that appears, switch to the **`{$}` Parameter** tab.
82
+
4. Either pick an existing parameter from the searchable list, or click **`+` Create Parameter** to define a new one inline.
83
+
5. The selected text in the step is replaced with the parameter reference (for example, `{{search_query}}`). The parameterized step is now ready for data-driven execution.
84
+
85
+
:::note
86
+
This flow is only supported for `Click` and `Type` commands. For the full Convert as popover behavior across Parameters, Variables, and Secrets, see [Creating variables from a Manual Interaction step](/support/docs/kane-ai-using-variables/#from-a-manual-interaction-step).
87
+
:::
88
+
74
89
## Test Summary Page
75
90
Upon completing the test, review the Test Summary Page, where all utilized parameters are clearly displayed, and the corresponding generated code is readily available for seamless integration into future test scenarios.
Copy file name to clipboardExpand all lines: docs/kane-ai-using-variables.md
+33Lines changed: 33 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -91,6 +91,39 @@ For such _local_ variables, only the scope of the variable can be changed to a g
91
91
By visiting the [variables page](https://kaneai.lambdatest.com/variables), you can click on "Create new" option and add relevant details and scope. You can list of all global and environment variables on this page.
92
92
You can edit the session value for the variables here which will lead to updation of the value in all new test executions and sessions for that variable.
93
93
94
+
### From a Manual Interaction step
95
+
96
+
While reviewing a Manual Interaction step, you can replace any hard-coded value in the step's instruction with a Parameter, Variable, or Secret — without deleting or re-recording the step. This flow is available on both **Desktop** and **Mobile App** Manual Interaction sessions.
97
+
98
+
#### Steps to convert a value
99
+
100
+
1. Open the recorded Manual Interaction step (for example, *Type in main search input field 'test.com'*).
101
+
2.**Select the portion** of the instruction text you want to replace (for example, highlight `test.com`).
- Existing secrets cannot be reused from the Convert as popover — the Secret tab only exposes the **`+` Create Secret** action. This is enforced for security, so a fresh secret must be created each time one is assigned to a Manual Interaction step.
122
+
- This is only supported for `Click` and `Type` Commands
123
+
:::
124
+
125
+
For details on secrets and parameters, see [KaneAI Secrets](/support/docs/kane-ai-secrets/) and [KaneAI Parameters](/support/docs/kane-ai-using-parameters/).
126
+
94
127
## How to leverage variables during authoring
95
128
Variables can be used to enhance your test cases, making them more dynamic.
0 commit comments