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
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.
41
42
42
-
# Creation of Configuration
43
+
##Creation of Configuration
43
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.
44
45
45
46
:::info
46
47
Virtual device option will only be available for non-KaneAI generated test runs.
47
48
:::
48
49
49
-
## Desktop Configuration
50
+
###Desktop Configuration
50
51
51
-
### How to create a new configuration?
52
+
####How to create a new configuration?
52
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:
53
54
- Operating System
54
55
- OS Version
@@ -60,13 +61,13 @@ Within a test run, while adding configuration to a test instance, you can choose
60
61
61
62
---
62
63
63
-
## Real Device Configuration
64
+
###Real Device Configuration
64
65
65
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.
66
67
67
-
### Native Application
68
+
####Native Application
68
69
69
-
#### How to select?
70
+
#####How to select?
70
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:
71
72
- Device Type
72
73
- Operating System
@@ -81,13 +82,13 @@ Within a test run, while adding configuration to a test instance, you can choose
81
82
The following options are only available for only KaneAI generated test runs
82
83
:::
83
84
84
-
##### Device Type: Private Cloud vs Public Cloud
85
+
######Device Type: Private Cloud vs Public Cloud
85
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.
86
87
87
-
#### Multi‑select for KaneAI configurations
88
+
#####Multi‑select for KaneAI configurations
88
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.
89
90
90
-
#### Application
91
+
#####Application
91
92
92
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.
93
94
@@ -101,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:
112
113
- Operating System
113
114
- Browser
@@ -117,13 +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:
128
130
- Operating System
129
131
- Manufacturer
@@ -134,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:
141
143
- Operating System
142
144
- Browser
@@ -149,15 +151,15 @@ Within a non-KaneAI generated test run, while adding configuration to a test ins
149
151
150
152
---
151
153
152
-
# Addition of Configuration in Test Runs
154
+
##Addition of Configuration in Test Runs
153
155
154
-
## Using the UI
156
+
###Using the UI
155
157
1. Open the **Add Configuration** dialog in a test run
156
158
2. You can add configurations in two ways:
157
159
- Create a new configuration
158
160
- Select from existing configurations
159
161
160
-
## Filtering and Selection Options
162
+
###Filtering and Selection Options
161
163
* Use the filter chips to narrow down configurations by:
162
164
- Operating System
163
165
- Device Type
@@ -167,6 +169,7 @@ Within a non-KaneAI generated test run, while adding configuration to a test ins
167
169
- Select all configurations matching current filters
168
170
- Mass assign configurations to test instances
169
171
172
+
---
170
173
171
174
## Best Practices
172
175
1. Use descriptive configuration names for easy identification
0 commit comments