diff --git a/assets/images/kane-ai/knowledge-base/api-testing/image13.jpg b/assets/images/kane-ai/knowledge-base/api-testing/image13.jpg
new file mode 100644
index 000000000..bdbbf9088
Binary files /dev/null and b/assets/images/kane-ai/knowledge-base/api-testing/image13.jpg differ
diff --git a/assets/images/kane-ai/knowledge-base/variables/1.png b/assets/images/kane-ai/knowledge-base/variables/1.png
new file mode 100644
index 000000000..b90faaaed
Binary files /dev/null and b/assets/images/kane-ai/knowledge-base/variables/1.png differ
diff --git a/docs/contacts-on-real-devices.md b/docs/contacts-on-real-devices.md
index 210f3e95e..e9f01f2d2 100644
--- a/docs/contacts-on-real-devices.md
+++ b/docs/contacts-on-real-devices.md
@@ -49,18 +49,15 @@ import TabItem from '@theme/TabItem';
})
}}
>
-
With LambdaTest Real Devices, you can interact with the built-in Contacts app on our real devices to test your app's functionality. To support diverse testing, we've included sample contact data for you to use.
## Supported Devices
-
LambdaTest supports access to the dummy Contacts on the following devices:
- Devices running Android 10 and higher(Except Tabs).
- Devices running iOS 13 and higher.
## What you can test?
-
With access to the Contacts app on the remote devices, you can now test scenarios, such as:
- Access contacts from the Contacts app.
diff --git a/docs/kane-ai-api-testing.md b/docs/kane-ai-api-testing.md
index bf0fed23f..ade9e6fec 100644
--- a/docs/kane-ai-api-testing.md
+++ b/docs/kane-ai-api-testing.md
@@ -86,7 +86,7 @@ KaneAI allows batch processing of multiple APIs to streamline testing. This feat
- **Step**: Add multiple APIs by clicking the plus icon and selecting each API, or paste multiple curl commands to add them automatically to the test steps.
-
+
## 6. Handling Different HTTP Methods
@@ -98,7 +98,7 @@ KaneAI supports various HTTP methods like POST, PUT, GET, and DELETE, allowing y
-
+
## 7. Executing and Reviewing Test Steps
@@ -106,7 +106,7 @@ Once all APIs are added, KaneAI enables simultaneous execution, with details ava
- **Step**: Click to execute all added APIs in one go and review the response details for insights into API performance and data returned.
-
+
This structure provides logical groupings for different aspects of API testing with KaneAI, making it easier to follow each type of action required for comprehensive API testing.
\ No newline at end of file
diff --git a/docs/kane-ai-jira-integration.md b/docs/kane-ai-jira-integration.md
index d0e8c9836..417bfd363 100644
--- a/docs/kane-ai-jira-integration.md
+++ b/docs/kane-ai-jira-integration.md
@@ -77,9 +77,9 @@ After you post the comment, Kane AI will process the request and respond with a
### Step 4: Review and Schedule the Test Case on LambdaTest
-- **Access the Test Case :** Click on the link provided by Kane AI in the Jira comment. This will direct you to the [Test Planner platform](/support/docs/kane-ai-test-plan/#step-2-define-your-state-outcomes-error-messages-constraints-and-user-inputs) where the test case has been created.
+- **Access the Test Case :** Click on the link provided by Kane AI in the Jira comment. This will create a [Test Plan](/support/docs/kane-ai-test-plan/#step-2-define-your-state-outcomes-error-messages-constraints-and-user-inputs) for you to review and execute via KaneAI.
- **Review Test Case Details :** Check the generated test case for accuracy. You can review test steps, expected outcomes, and conditions to ensure they align with your requirements.
-- **Schedule Test Execution :** Once verified, schedule the test case for execution.
+- **Schedule the Task for KaneAI :** Once verified, schedule the task for KaneAI to generate and automate the test case on its own.
### Step 5: Check the test execution
Click on the Live Preview button to enter the playground and check the live execution of your test based on your defined objective.
diff --git a/docs/kane-ai-using-variables.md b/docs/kane-ai-using-variables.md
new file mode 100644
index 000000000..476daba5a
--- /dev/null
+++ b/docs/kane-ai-using-variables.md
@@ -0,0 +1,89 @@
+---
+id: kane-ai-using-variables
+title: KaneAI - Using Variables in Test Cases
+hide_title: false
+sidebar_label: Variables Guide
+description: Learn how to use variables in the KaneAI test cases
+keywords:
+ - lambdatest automation
+ - lambdatest kaneai
+ - kaneai scroll elements
+ - kaneai sidebar scroll
+url: https://www.lambdatest.com/support/docs/kane-ai-using-variables/
+site_name: LambdaTest
+slug: kane-ai-using-variables/
+---
+
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+import CodeBlock from '@theme/CodeBlock';
+import {YOUR_LAMBDATEST_USERNAME, YOUR_LAMBDATEST_ACCESS_KEY} from "@site/src/component/keys";
+
+
+The new variable definition feature in KaneAI allows users to define reusable variables, assign them values, and use those values within test cases. This feature enhances flexibility, readability, and consistency across test cases, making it easier to maintain and modify them.
+
+## Why Use Variables?
+Using variables enables you to:
+- Avoid repetitive entries in test cases.
+- Update values in one place without needing to modify multiple test cases.
+- Increase the reusability and adaptability of test scripts, especially useful for parameters that might change frequently, such as URLs, credentials, or environmental settings.
+
+## Variable Syntax
+To work with variables in KaneAI, you need to follow these syntax rules:
+
+- Variables are defined using the `$` prefix
+- Variable names should follow the `$` symbol without any spaces
+- Example: `$username`, `$phoneNumber`, `$address`
+
+## Creating Variables
+To create a variable:
+
+- Navigate to the "Write a Step" text field
+- Type your instruction using the following format: *create a variable `$variableName`*
+
+Example:
+```bash
+create a variable $phoneNumber
+```
+
+## Using Variables
+To use a previously created variable in any subsequent step or test case, reference the variable using the same `$` syntax. Format: *use the value of `$variableName`*
+
+Example:
+```bash
+use the value of $phoneNumber in the given text field
+```
+
+
+## Best Practices
+### Naming Conventions
+- Use descriptive names for your variables
+- Avoid special characters except for the required $ prefix
+- Use camelCase for multi-word variable names
+
+### Variable Management
+- Create variables at the beginning of your test case when possible
+- Document the purpose of each variable in comments
+- Verify that variables are defined before using them
\ No newline at end of file
diff --git a/docs/ui-inspector.md b/docs/ui-inspector.md
index c6ee81072..c0423d817 100644
--- a/docs/ui-inspector.md
+++ b/docs/ui-inspector.md
@@ -1,7 +1,7 @@
---
id: ui-inspector
title: UI Inspector
-hide_title: true
+hide_title: false
sidebar_label: UI Inspector
description: Learn real device app testing with LambdaTest across Android and iOS devices. Start testing effortlessly today!
keywords:
@@ -34,13 +34,8 @@ slug: ui-inspector/
})
}}
>
-
-# UI Inspector
-
LambdaTest UI App Inspector provides a graphical interface to inspect and interact with the elements of a mobile application. When you launch your mobile app, it retrieves the DOM (Document Object Model) of the app. This DOM includes various UI elements such as buttons, text fields, labels, etc., organised in a hierarchical structure.
-***
-
## Benefits of UI Inspector
- **DOM Representation:** It visually represents the DOM of the mobile application in a tree-like structure. This representation helps testers and developers understand the layout and structure of the app's UI.
@@ -85,8 +80,6 @@ Let's have a detailed look at each of these components:
- The Screenshot View provides a comprehensive overview of the mobile application's user interface elements, presented in a visual representation typically in the form of a screenshot dump.
- Users can click on individual elements within the screenshot dump, triggering simultaneous highlighting of the corresponding element in both the Hierarchy View and the Properties Table, facilitating quick navigation and detailed inspection.
-
-
.default})
+ .default})
## 6. Handling Different HTTP Methods
@@ -98,7 +98,7 @@ KaneAI supports various HTTP methods like POST, PUT, GET, and DELETE, allowing y
.default})
- .default})
This structure provides logical groupings for different aspects of API testing with KaneAI, making it easier to follow each type of action required for comprehensive API testing.
\ No newline at end of file
diff --git a/docs/kane-ai-jira-integration.md b/docs/kane-ai-jira-integration.md
index d0e8c9836..417bfd363 100644
--- a/docs/kane-ai-jira-integration.md
+++ b/docs/kane-ai-jira-integration.md
@@ -77,9 +77,9 @@ After you post the comment, Kane AI will process the request and respond with a
.default})
### Step 4: Review and Schedule the Test Case on LambdaTest
-- **Access the Test Case :** Click on the link provided by Kane AI in the Jira comment. This will direct you to the [Test Planner platform](/support/docs/kane-ai-test-plan/#step-2-define-your-state-outcomes-error-messages-constraints-and-user-inputs) where the test case has been created.
+- **Access the Test Case :** Click on the link provided by Kane AI in the Jira comment. This will create a [Test Plan](/support/docs/kane-ai-test-plan/#step-2-define-your-state-outcomes-error-messages-constraints-and-user-inputs) for you to review and execute via KaneAI.
- **Review Test Case Details :** Check the generated test case for accuracy. You can review test steps, expected outcomes, and conditions to ensure they align with your requirements.
-- **Schedule Test Execution :** Once verified, schedule the test case for execution.
+- **Schedule the Task for KaneAI :** Once verified, schedule the task for KaneAI to generate and automate the test case on its own.
### Step 5: Check the test execution
Click on the Live Preview button to enter the playground and check the live execution of your test based on your defined objective.
diff --git a/docs/kane-ai-using-variables.md b/docs/kane-ai-using-variables.md
new file mode 100644
index 000000000..476daba5a
--- /dev/null
+++ b/docs/kane-ai-using-variables.md
@@ -0,0 +1,89 @@
+---
+id: kane-ai-using-variables
+title: KaneAI - Using Variables in Test Cases
+hide_title: false
+sidebar_label: Variables Guide
+description: Learn how to use variables in the KaneAI test cases
+keywords:
+ - lambdatest automation
+ - lambdatest kaneai
+ - kaneai scroll elements
+ - kaneai sidebar scroll
+url: https://www.lambdatest.com/support/docs/kane-ai-using-variables/
+site_name: LambdaTest
+slug: kane-ai-using-variables/
+---
+
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+import CodeBlock from '@theme/CodeBlock';
+import {YOUR_LAMBDATEST_USERNAME, YOUR_LAMBDATEST_ACCESS_KEY} from "@site/src/component/keys";
+
+
+The new variable definition feature in KaneAI allows users to define reusable variables, assign them values, and use those values within test cases. This feature enhances flexibility, readability, and consistency across test cases, making it easier to maintain and modify them.
+
+## Why Use Variables?
+Using variables enables you to:
+- Avoid repetitive entries in test cases.
+- Update values in one place without needing to modify multiple test cases.
+- Increase the reusability and adaptability of test scripts, especially useful for parameters that might change frequently, such as URLs, credentials, or environmental settings.
+
+## Variable Syntax
+To work with variables in KaneAI, you need to follow these syntax rules:
+
+- Variables are defined using the `$` prefix
+- Variable names should follow the `$` symbol without any spaces
+- Example: `$username`, `$phoneNumber`, `$address`
+
+## Creating Variables
+To create a variable:
+
+- Navigate to the "Write a Step" text field
+- Type your instruction using the following format: *create a variable `$variableName`*
+
+Example:
+```bash
+create a variable $phoneNumber
+```
+
+## Using Variables
+To use a previously created variable in any subsequent step or test case, reference the variable using the same `$` syntax. Format: *use the value of `$variableName`*
+
+Example:
+```bash
+use the value of $phoneNumber in the given text field
+```
+.default})
+
+## Best Practices
+### Naming Conventions
+- Use descriptive names for your variables
+- Avoid special characters except for the required $ prefix
+- Use camelCase for multi-word variable names
+
+### Variable Management
+- Create variables at the beginning of your test case when possible
+- Document the purpose of each variable in comments
+- Verify that variables are defined before using them
\ No newline at end of file
diff --git a/docs/ui-inspector.md b/docs/ui-inspector.md
index c6ee81072..c0423d817 100644
--- a/docs/ui-inspector.md
+++ b/docs/ui-inspector.md
@@ -1,7 +1,7 @@
---
id: ui-inspector
title: UI Inspector
-hide_title: true
+hide_title: false
sidebar_label: UI Inspector
description: Learn real device app testing with LambdaTest across Android and iOS devices. Start testing effortlessly today!
keywords:
@@ -34,13 +34,8 @@ slug: ui-inspector/
})
}}
>
-
-# UI Inspector
-
LambdaTest UI App Inspector provides a graphical interface to inspect and interact with the elements of a mobile application. When you launch your mobile app, it retrieves the DOM (Document Object Model) of the app. This DOM includes various UI elements such as buttons, text fields, labels, etc., organised in a hierarchical structure.
-***
-
## Benefits of UI Inspector
- **DOM Representation:** It visually represents the DOM of the mobile application in a tree-like structure. This representation helps testers and developers understand the layout and structure of the app's UI.
@@ -85,8 +80,6 @@ Let's have a detailed look at each of these components:
- The Screenshot View provides a comprehensive overview of the mobile application's user interface elements, presented in a visual representation typically in the form of a screenshot dump.
- Users can click on individual elements within the screenshot dump, triggering simultaneous highlighting of the corresponding element in both the Hierarchy View and the Properties Table, facilitating quick navigation and detailed inspection.
-
-