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
@@ -42,18 +37,19 @@ import {YOUR_LAMBDATEST_USERNAME, YOUR_LAMBDATEST_ACCESS_KEY} from "@site/src/co
42
37
})
43
38
}}
44
39
></script>
40
+
# Configurations in KaneAI & Test Manager
45
41
This document explains how application and environment configurations behave across **Test Manager (TM)** and **KaneAI** for **Desktop**, **Real Device** and **Virtual Device** within test runs.
46
42
47
-
# Creation of Configuration
43
+
##Creation of Configuration
48
44
A new configuration can be created during creation or edit of a test run. While creating a configuration, users can choose either Desktop, Virtual Device or Real device.
49
45
50
-
::: tip
46
+
:::info
51
47
Virtual device option will only be available for non-KaneAI generated test runs.
52
48
:::
53
49
54
-
## Desktop Configuration
50
+
###Desktop Configuration
55
51
56
-
### How to create a new configuration?
52
+
####How to create a new configuration?
57
53
Within a test run, while adding configuration to a test instance, you can choose to create a new configuration. By default, a desktop configuration is selected. You can then add the `Configuration Name` and the `Configuration Details`. You need to add the following fields:
58
54
- Operating System
59
55
- OS Version
@@ -65,13 +61,13 @@ Within a test run, while adding configuration to a test instance, you can choose
65
61
66
62
---
67
63
68
-
## Real Device Configuration
64
+
###Real Device Configuration
69
65
70
66
Real device configuration supports two options for `native app` and `mobile browser` configurations. The option for `native app` is supported for only KaneAI test runs, while `mobile browser` is supported for both KaneAI and non-KaneAI test runs.
71
67
72
-
### Native Application
68
+
####Native Application
73
69
74
-
#### How to select?
70
+
#####How to select?
75
71
Within a test run, while adding configuration to a test instance, you can choose to create a new configuration and select the `Real Device` section from the top navigation. You can then add the `Configuration Name` and the `Configuration Details`. You need to add the following fields:
76
72
- Device Type
77
73
- Operating System
@@ -82,17 +78,17 @@ Within a test run, while adding configuration to a test instance, you can choose
The following options are only available for only KaneAI generated test runs
87
83
:::
88
84
89
-
##### Device Type: Private Cloud vs Public Cloud
85
+
######Device Type: Private Cloud vs Public Cloud
90
86
Available for organisations with a private cloud real device plan with LambdaTest. The option allows for users to choose from set of public pool of devices vs private pool dedicated specifically for that organisation.
91
87
92
-
#### Multi‑select for KaneAI configurations
88
+
#####Multi‑select for KaneAI configurations
93
89
* KaneAI allows multi‑select for Manufacturer, Device, and OS Version to allow for larger set of device pool for any configuration. Using multiple devices ensures that you always are able to proceed with executions on HyperExecute.
94
90
95
-
#### Application
91
+
#####Application
96
92
97
93
***Auto Update** – If you have new builds for application being uploaded quite frequently, ensure to check the `Update automatically when a new version is uploaded` option while selecting application in the configuration. This ensures that based on `appPackage` or `bundleId`, we automatically update your configuration with the latest build.
98
94
@@ -106,13 +102,13 @@ Available for organisations with a private cloud real device plan with LambdaTes
Within a non-KaneAI generated test run, while adding configuration to a test instance, you can choose to create a new configuration and select the `Real Device` section from the top navigation. The choose the `Web Browser` option. You can then add the `Configuration Name` and the `Configuration Details`. You need to add the following fields:
117
113
- Operating System
118
114
- Browser
@@ -122,14 +118,14 @@ Within a non-KaneAI generated test run, while adding configuration to a test ins
Within a non-KaneAI generated test run, while adding configuration to a test instance, you can choose to create a new configuration and select the `Virtual Device` section from the top navigation. The choose the `Mobile App` option. You can then add the `Configuration Name` and the `Configuration Details`. You need to add the following fields:
134
130
- Operating System
135
131
- Manufacturer
@@ -140,9 +136,9 @@ Within a non-KaneAI generated test run, while adding configuration to a test ins
Within a non-KaneAI generated test run, while adding configuration to a test instance, you can choose to create a new configuration and select the `Virtual Device` section from the top navigation. The choose the `Web Browser` option. You can then add the `Configuration Name` and the `Configuration Details`. You need to add the following fields:
147
143
- Operating System
148
144
- Browser
@@ -155,15 +151,15 @@ Within a non-KaneAI generated test run, while adding configuration to a test ins
155
151
156
152
---
157
153
158
-
# Addition of Configuration in Test Runs
154
+
##Addition of Configuration in Test Runs
159
155
160
-
## Using the UI
156
+
###Using the UI
161
157
1. Open the **Add Configuration** dialog in a test run
162
158
2. You can add configurations in two ways:
163
159
- Create a new configuration
164
160
- Select from existing configurations
165
161
166
-
## Filtering and Selection Options
162
+
###Filtering and Selection Options
167
163
* Use the filter chips to narrow down configurations by:
168
164
- Operating System
169
165
- Device Type
@@ -173,6 +169,7 @@ Within a non-KaneAI generated test run, while adding configuration to a test ins
173
169
- Select all configurations matching current filters
174
170
- Mass assign configurations to test instances
175
171
172
+
---
176
173
177
174
## Best Practices
178
175
1. Use descriptive configuration names for easy identification
0 commit comments