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
Copy file name to clipboardExpand all lines: docs/kane-ai-using-variables.md
+10-6Lines changed: 10 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -73,15 +73,15 @@ Variables can be created using the following three methods:
73
73
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.
74
74
The value of variables can be edited by clicking on the variables listing icon on the top right.
KaneAI allows you to create variables using natural language. For instance, you can write:
80
80
81
81
```bash
82
82
Set username as John
83
83
```
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".
85
85
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.
86
86
87
87
@@ -128,23 +128,25 @@ Persist value check is a mechanism used to ensure that variables retain their va
128
128
The persist check option becomes available only when you change a variable's scope from local to global.
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.
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.
142
142
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.
**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,
0 commit comments