Skip to content

Commit 93d4afa

Browse files
author
akshayverma
committed
Highlight Parameters
1 parent 3e6b907 commit 93d4afa

3 files changed

Lines changed: 48 additions & 0 deletions

File tree

42.3 KB
Loading

docs/kane-ai-using-parameters.md

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -71,6 +71,21 @@ Reference any parameter using **dollar-curly braces syntax** (e.g.,`${phone_numb
7171

7272
<img loading="lazy" src={require('../assets/images/kane-ai/features/parameters/4.png').default} alt="Image" className="doc_img"/>
7373

74+
## From a Manual Interaction step
75+
76+
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`).
80+
<img loading="lazy" src={require('../assets/images/kane-ai/knowledge-base/variables/HighlightScreenshot.png').default} alt="Image" className="doc_img img_center"/>
81+
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+
7489
## Test Summary Page
7590
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.
7691
<img loading="lazy" src={require('../assets/images/kane-ai/features/parameters/7.png').default} alt="Image" className="doc_img"/>

docs/kane-ai-using-variables.md

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -91,6 +91,39 @@ For such _local_ variables, only the scope of the variable can be changed to a g
9191
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.
9292
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.
9393

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`).
102+
<img loading="lazy" src={require('../assets/images/kane-ai/knowledge-base/variables/HighlightScreenshot.png').default} alt="Image" className="doc_img img_center"/>
103+
3. In the **Convert as** popover that appears, choose one of the three tabs:
104+
- **`{$}` Parameter** — test-level variable, supports selecting an existing parameter or creating a new one.
105+
- **`{x}` Variable** — Global or Environment variable, supports selecting an existing variable or creating a new one.
106+
- **🔒 Secret** — encrypted value that resolves only at execution time. Only new secrets can be created from this tab.
107+
4. Either pick an existing entry from the searchable list, or click **`+` Create Parameter / Variable / Secret** to define a new one inline.
108+
5. The selected text in the step is replaced with the variable reference (for example, `{{search_query}}`). The step updates in place.
109+
110+
#### Support matrix
111+
112+
| Variable Type | Use Existing | Create New | Scope |
113+
|---------------|--------------|------------|-------|
114+
| `{$}` Parameter | Supported | Supported | Test-level |
115+
| `{x}` Variable | Supported | Supported | Global / Environment |
116+
| 🔒 Secret | Not supported | Supported | Vault-level |
117+
118+
119+
120+
:::note
121+
- 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+
94127
## How to leverage variables during authoring
95128
Variables can be used to enhance your test cases, making them more dynamic.
96129

0 commit comments

Comments
 (0)