|
| 1 | +--- |
| 2 | +id: test-runs-configurations |
| 3 | +title: 'Configurations in KaneAI & Test Manager' |
| 4 | +hide_title: false |
| 5 | +sidebar_label: Configurations |
| 6 | +description: Learn how to levearge configurations to execute your tests in multiple environments. |
| 7 | +keywords: |
| 8 | + - lambdatest automation |
| 9 | + - kaneai |
| 10 | + - test manager |
| 11 | + - configurations |
| 12 | +url: https://www.lambdatest.com/support/docs/test-runs-configurations/ |
| 13 | +site_name: LambdaTest |
| 14 | +slug: test-runs-configurations/ |
| 15 | +--- |
| 16 | + |
| 17 | +import Tabs from '@theme/Tabs'; |
| 18 | +import TabItem from '@theme/TabItem'; |
| 19 | +import CodeBlock from '@theme/CodeBlock'; |
| 20 | +import {YOUR_LAMBDATEST_USERNAME, YOUR_LAMBDATEST_ACCESS_KEY} from "@site/src/component/keys"; |
| 21 | + |
| 22 | +<script type="application/ld+json" |
| 23 | + dangerouslySetInnerHTML={{ __html: JSON.stringify({ |
| 24 | + "@context": "https://schema.org", |
| 25 | + "@type": "BreadcrumbList", |
| 26 | + "itemListElement": [{ |
| 27 | + "@type": "ListItem", |
| 28 | + "position": 1, |
| 29 | + "name": "Home", |
| 30 | + "item": "https://www.lambdatest.com" |
| 31 | + },{ |
| 32 | + "@type": "ListItem", |
| 33 | + "position": 2, |
| 34 | + "name": "Support", |
| 35 | + "item": "https://www.lambdatest.com/support/docs/" |
| 36 | + },{ |
| 37 | + "@type": "ListItem", |
| 38 | + "position": 3, |
| 39 | + "name": "Configurations in KaneAI & Test Manager", |
| 40 | + "item": "https://www.lambdatest.com/support/docs/test-runs-configurations" |
| 41 | + }] |
| 42 | + }) |
| 43 | + }} |
| 44 | +></script> |
| 45 | +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 | + |
| 47 | +# Creation of Configuration |
| 48 | +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 | + |
| 50 | +::: tip |
| 51 | +Virtual device option will only be available for non-KaneAI generated test runs. |
| 52 | +::: |
| 53 | + |
| 54 | +## Desktop Configuration |
| 55 | + |
| 56 | +### How to create a new configuration? |
| 57 | +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 | +- Operating System |
| 59 | +- OS Version |
| 60 | +- Browser |
| 61 | +- Browser Version |
| 62 | +- Resolution |
| 63 | + |
| 64 | +<img loading="lazy" src={require('../assets/images/kane-ai/app-test/DesktopConfig.png').default} alt="kaneai-desktop-config" className="doc_img"/> |
| 65 | + |
| 66 | +--- |
| 67 | + |
| 68 | +## Real Device Configuration |
| 69 | + |
| 70 | +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 | + |
| 72 | +### Native Application |
| 73 | + |
| 74 | +#### How to select? |
| 75 | +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 | +- Device Type |
| 77 | +- Operating System |
| 78 | +- Manufacturer |
| 79 | +- Device |
| 80 | +- OS Version |
| 81 | +- App |
| 82 | + |
| 83 | +<img loading="lazy" src={require('../assets/images/kane-ai/app-test/RealDeviceConfig.png').default} alt="kaneai-real-device-config" className="doc_img"/> |
| 84 | + |
| 85 | +::: tip |
| 86 | +The following options are only available for only KaneAI generated test runs |
| 87 | +::: |
| 88 | + |
| 89 | +##### Device Type: Private Cloud vs Public Cloud |
| 90 | +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 | + |
| 92 | +#### Multi‑select for KaneAI configurations |
| 93 | +* 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 | + |
| 95 | +#### Application |
| 96 | + |
| 97 | +* **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 | + |
| 99 | +<img loading="lazy" src={require('../assets/images/kane-ai/app-test/UpdateApp.png').default} alt="kaneai-update-app-config" className="doc_img"/> |
| 100 | + |
| 101 | +* **Custom ID** – In case you are using [API](https://www.lambdatest.com/support/docs/application-setup-via-api/#upload-your-application) to upload your application and using the custom_id parameter, you can choose to add a custom ID while creating a configuration, so that the application gets updated automatically each time you upload a new app with the same custom_id. |
| 102 | + |
| 103 | +<img loading="lazy" src={require('../assets/images/kane-ai/app-test/CustomID.png').default} alt="kaneai-custom-id-app" className="doc_img"/> |
| 104 | + |
| 105 | +* **Private Device Type** - When private device type is chosen, you will get an option to `Select Pre‑Installed App in Session`; choosing it maps the app capability to `Stock` allowing you to proceed with creating a configuration without explicitly defining an application. This option should be used only when your test case has first step as "Open xyz application" where xyz is the application pre-installed in the device. |
| 106 | + |
| 107 | +<img loading="lazy" src={require('../assets/images/kane-ai/app-test/PreinstalledApp.png').default} alt="kaneai-preinstalled-app" className="doc_img"/> |
| 108 | + |
| 109 | +### Browser |
| 110 | + |
| 111 | +::: tip |
| 112 | +Available for only non-KaneAI generated test runs |
| 113 | +::: |
| 114 | + |
| 115 | +#### How to select? |
| 116 | +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 | +- Operating System |
| 118 | +- Browser |
| 119 | +- Manufacturer |
| 120 | +- Device |
| 121 | +- OS Version |
| 122 | + |
| 123 | +<img loading="lazy" src={require('../assets/images/kane-ai/app-test/RDWebBrowser.png').default} alt="kaneai-rd-web-config" className="doc_img"/> |
| 124 | + |
| 125 | + |
| 126 | +## Virtual Device Configuration |
| 127 | + |
| 128 | +::: tip |
| 129 | +Available for only non-KaneAI generated test runs |
| 130 | +::: |
| 131 | + |
| 132 | +### Native Application |
| 133 | +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 | +- Operating System |
| 135 | +- Manufacturer |
| 136 | +- Device |
| 137 | +- OS Version |
| 138 | +- App |
| 139 | + |
| 140 | +<img loading="lazy" src={require('../assets/images/kane-ai/app-test/VirtualWeb.png').default} alt="kaneai-virtual-web-config" className="doc_img"/> |
| 141 | + |
| 142 | + |
| 143 | +### Browser |
| 144 | + |
| 145 | +#### How to select? |
| 146 | +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 | +- Operating System |
| 148 | +- Browser |
| 149 | +- Manufacturer |
| 150 | +- Device |
| 151 | +- OS Version |
| 152 | +- URL (Optional) |
| 153 | + |
| 154 | +<img loading="lazy" src={require('../assets/images/kane-ai/app-test/VirtualApp.png').default} alt="kaneai-virtual-app-config" className="doc_img"/> |
| 155 | + |
| 156 | +--- |
| 157 | + |
| 158 | +# Addition of Configuration in Test Runs |
| 159 | + |
| 160 | +## Using the UI |
| 161 | +1. Open the **Add Configuration** dialog in a test run |
| 162 | +2. You can add configurations in two ways: |
| 163 | + - Create a new configuration |
| 164 | + - Select from existing configurations |
| 165 | + |
| 166 | +## Filtering and Selection Options |
| 167 | +* Use the filter chips to narrow down configurations by: |
| 168 | + - Operating System |
| 169 | + - Device Type |
| 170 | + - Browser |
| 171 | +* Use the search bar to find specific configurations |
| 172 | +* Use the **Select All** toggle to: |
| 173 | + - Select all configurations matching current filters |
| 174 | + - Mass assign configurations to test instances |
| 175 | + |
| 176 | + |
| 177 | +## Best Practices |
| 178 | +1. Use descriptive configuration names for easy identification |
| 179 | +2. Leverage filters to quickly find relevant configurations |
| 180 | +3. Use the **Select All** feature when you need to apply the same configuration to multiple test instances |
0 commit comments