Skip to content

Commit a8697f9

Browse files
authored
Merge pull request #1789 from Private1647/stage
Update kane-ai-using-variables.md
2 parents 2b27328 + 7e5adf8 commit a8697f9

File tree

1 file changed

+10
-6
lines changed

1 file changed

+10
-6
lines changed

docs/kane-ai-using-variables.md

Lines changed: 10 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -73,15 +73,15 @@ Variables can be created using the following three methods:
7373
You can define variables directly by using the `/` command in the step input and select "Add a variable" option. You are allowed to create _global_ and _environment_ variables using this approach and define their values.
7474
The value of variables can be edited by clicking on the variables listing icon on the top right.
7575

76-
<img loading="lazy" src={require('../assets/images/kane-ai/knowledge-base/variables/variable-listing-in-session.jpg').default} alt="Image" className="doc_img img_center"/>
76+
<img loading="lazy" src={require('../assets/images/kane-ai/knowledge-base/variables/environment.jpg').default} alt="Image" className="doc_img img_center"/>
7777

7878
### Using Natural Language in authoring session
7979
KaneAI allows you to create variables using natural language. For instance, you can write:
8080

8181
```bash
8282
Set username as John
8383
```
84-
This will automatically create a _local_ variable {{username}} with the value "John".
84+
This will automatically create a _local_ variable `{{username}}` with the value "John".
8585
For such _local_ variables, only the scope of the variable can be changed to a global with an option to enable the persist check which ensures that the value when updated in one session or test execution gets persistes across sessions and test executions.
8686

8787

@@ -128,23 +128,25 @@ Persist value check is a mechanism used to ensure that variables retain their va
128128
The persist check option becomes available only when you change a variable's scope from local to global.
129129
:::
130130

131-
<img loading="lazy" src={require('../assets/images/kane-ai/knowledge-base/variables/persist-value.jpg').default} alt="Image" className="doc_img img_center"/>
131+
<img loading="lazy" src={require('../assets/images/kane-ai/knowledge-base/variables/variable-listing-in-session.jpg').default} alt="Image" className="doc_img img_center"/>
132132

133133
## Environments
134134

135135
### What are Environments?
136136
Environments in KaneAI refer to the different configurations under which the tests are executed. Environments typically represent different stages of deployment (e.g., development, staging, production). Each environment can have its own set of variables tailored to the respective deployment scenario.
137137

138-
<img loading="lazy" src={require('../assets/images/kane-ai/knowledge-base/variables/environment.jpg').default} alt="Image" className="doc_img img_center"/>
138+
<img loading="lazy" src={require('../assets/images/kane-ai/knowledge-base/variables/persist-value.jpg').default} alt="Image" className="doc_img img_center"/>
139139

140140
### How to Use Environments During Test Runs
141141
Once a test case is authored using environment variables, it can then be executed in any environment as long as the variables used in the test case, exist in the requested environment.
142142

143-
**UI**: While executing a test run or scheduling one, you can choose which environment they want to execute a test run on. All the test cases inside a test run can be executed on a single environment only at a point of time.
143+
#### Leveraging UI
144+
While executing a test run or scheduling one, you can choose which environment they want to execute a test run on. All the test cases inside a test run can be executed on a single environment only at a point of time.
144145

145146
<img loading="lazy" src={require('../assets/images/kane-ai/knowledge-base/variables/test-run-environment.jpg').default} alt="Image" className="doc_img img_center"/>
146147

147-
**API**: You can pass environment name programmatically when initiating test runs via the API. This allows you to automate the execution of tests in different environments without manual intervention. For instance,
148+
#### Leveraging API
149+
You can pass environment name programmatically when initiating test runs via the API. This allows you to automate the execution of tests in different environments without manual intervention. For instance,
148150

149151
```bash
150152
curl --location 'https://test-manager-api.lambdatest.com/api/atm/v1/hyperexecute' \
@@ -158,4 +160,6 @@ curl --location 'https://test-manager-api.lambdatest.com/api/atm/v1/hyperexecute
158160
159161
This will run the test case in the "staging" environment.
160162
163+
If you have any feedback or suggestions, feel free to reach out at support@lambdatest.com with your comments.
164+
161165

0 commit comments

Comments
 (0)