Settings For Web, Mobile, Desktop and Hybrid Automation
Field by field reference for the Settings page of a web, mobile, desktop, or hybrid projects. The Settings page allows you to configure and manage settings for your project, including Project Information, Backup & Restore, and Feature File Settings. Select a project and navigate to settings in the left pane.
Summary Description of Project Settings Page
Navigate to Settings > Configuration Settings to view the project settings.
The following table provides a summary of Project Settings fields:
| Field | Description |
|---|---|
| Project Name | Displays the Project name entered during project creation. |
| Automation Type | Displays the Automation type entered during creation of the project. By default, this textbox is not editable. |
| Application URL | Displays the Application URL. You can modify the existing URL to access a specific application. |
The following table provides a summary of Backup and Restore Settings Fields:
| Field | Description |
|---|---|
| Daily Auto Backup | Auto-backup is enabled by default for all projects, and the auto-backup checkbox is disabled on the project settings page, if the project is assigned to you, these fields will not be available. |
Summary Description of Feature File Settings Page
Navigate to Settings > Configuration Settings to view the Feature File settings, available below the project settings.
The following table provides a summary of Feature File Settings Fields:
| Field | Description |
|---|---|
| Group By Module | Check this check box to generate a separate module, folder structure, and update. For more information, see Generating separate Feature File in separate folder. |
| Remove Default Tags | Check this check box to Remove Default Tags from the generated Feature file and update, if you choose to add custom tags. The following screenshot represents the original Feature File with this option unchecked:    |
| Application Name | You can enter a Given Application Name in this text box. After generating the test cases, Application Name will be available in feature file or .txt file |
| Data Decoupling | Check this check box and update to generate a separate YAML file in the Test cases Folder. To access TestData.Yml file, navigate to the Test Cases, expand the appropriate folder to view the YAML file. |
| Data Masking | Check this checkbox to encrypt sensitive data, such as passwords, OTPs, and other confidential information. The data remains encrypted throughout the process, from test case generation to script execution and reporting.  |
| Action | You can enter an appropriate action for the Given condition. After generating the test cases, Action will be available in feature file or .txt file |
| Default Screen Title | You can enter or modify a Default Screen Title. After generating the test cases, the pre-condition will be available in _updated.xlsx. Note: The Default Screen Title field is mandatory. |
| Scenario Input | You can add input for the GWT line, which will be automatically applied across the project. |
The data masking feature is currently available for the following frameworks:
- Web Automation: Java Selenium
- Desktop Automation: Python Squish and Python TestComplete
Summary Description of Data Generation Settings Page
Navigate to Settings > Configuration Settings to view the Data Generation settings, available below the Feature File settings.
Correct Values is selected by default. Enable the rest of the required options and click Update.
| Field | Description |
|---|---|
| Correct Values | This checkbox is selected by default. To allow correct control values in the test design, keep this checkbox selected and update. |
| Incorrect Values | To allow incorrect control values in the test design, select this checkbox and update. |
| Illegal Values | To allow illegal values in the test design (e.g., no digits, no special characters, all uppercase, all lowercase, no spaces), select this checkbox and update. |
| Invalid Values | To allow invalid values in the test design (e.g., ends with space, starts with space, space only, or empty), select this checkbox and update. |
| Boundary values | To allow boundary values in the test design (e.g., maximum value +1, maximum value, maximum value −1, minimum value +1, minimum value, minimum value −1), select this checkbox and update. |
| Edge Cases | To allow edge cases in the test design, select this checkbox and update. |
| Full Object Repository | To include all controls in the Object Repository, select the Full Object Repository checkbox and click Update. |
You can set the value range for your project from Business Rules. To learn more, navigate to Business Rules.
Summary Description of Script Generation Settings Page
You can change the Script Generation settings by clicking the Settings > Script generation settings. You can change the language and framework for a particular automation type.
Perform the following:
Navigate to the Settings.
Click the Script Generation Settings.
In the Script Generation screen, you can update the language and frameworks of a specific automation type.
You can choose whether to include common dependencies when generating the script.
Before generating the script, go to Script Generation Settings and select the Download Common Dependency checkbox to include them, or clear the checkbox if they are not required.
Click the Update button.
If you choose to revert to the original changes, then click the Reset button if you have already updated and click Cancel if not updated.
Refer to the table below to know the frameworks for which Common Dependency Download support is available.
| Automation Type | Framework | Support Available | Checkbox Required |
|---|---|---|---|
| Web Automation | Java Selenium | Yes | Yes |
| Web Automation | Java Karate | Yes | Yes |
| Web Automation | Python Selenium | Yes | Yes |
| Web Automation | JavaScript Selenium | Yes | Yes |
| Web Automation | JavaScript Cypress | No | No |
| Web Automation | JavaScript WebdriverIO | Yes | Yes |
| Web Automation | TypeScript Playwright | Yes | Yes |
| Web Automation | C# Selenium | Yes | Yes |
| Mobile Automation | Java Appium | Yes | Yes |
| Mobile Automation | Python Appium | Yes | Yes |
| Mobile Automation | Playwright TypeScript | No | No |
| Hybrid Automation | Python Selenium Appium | Yes | Yes |
| Hybrid Automation | Java Selenium Appium | Yes | Yes |
| Hybrid Automation | Java Selenium WinAppDriver | No | No |
| Desktop Automation | All Frameworks | No | No |
| API Automation | All Frameworks | No | No |
Application Settings for Script Generation
The Application Settings panel appears on the right side of the Script Generation Settings page. It groups settings into collapsible sections that control how the generated script runs. The available settings vary by automation type and framework.
Navigate to Settings > Script Generation Settings. In the Application Settings panel, click a section name to expand it, update the required settings, and click Update. To revert changes, click Reset (if already updated) or Cancel (if not updated). Use the Search field at the top to find a setting quickly, or the Expand/Collapse icon to toggle all sections.
Web Automation
Application Configuration
| Field | Description |
|---|---|
| Application URL | The URL of the application under test. The script opens this URL when execution starts. |
| Browser Type | Select the browser in which the script has to run, for example, Chrome. |
| WebDriver Path | Turn on this toggle to use a browser driver from a specific location instead of the default driver. |
| Download in Current Directory | Turn on this toggle to save files downloaded during execution in the current directory. |
| Incognito | Turn on this toggle to launch the browser in incognito mode, so cached data and cookies from earlier sessions are not used. |
| Auto Healing | Turn on this toggle to heal locator changes when a UI element changes during execution. For more information, see Auto-Healing. |
| AI Recovery | Turn on this toggle to allow AI-assisted recovery when a step fails during execution. |
| Failure Analysis | Turn on this toggle to get an analysis of the reasons for failed test cases after execution. |
Silicon Grid (Remote Execution)
Silicon Grid is available only for Web Automation. Use these settings to run the script on a remote grid.
| Field | Description |
|---|---|
| Remote URL | Enter the URL of the remote grid hub, for example, http://<host>:4444/wd/hub. |
| Grid Type | Select the type of grid, for example, Selenium Grid. |
External Integrations
External Integrations is available only for Web Automation. Use these settings to connect the script with Jira, Azure TFS, and LambdaTest. These fields will be different for each frameworks.
| Field | Description |
|---|---|
| Enable Jira Integration | Turn on this toggle to integrate with Jira. The Jira fields below are available only when this toggle is on. Jira Integration |
| Jira Server / Cloud URL | Enter the URL of your Jira instance, for example, https://your-domain.atlassian.net. |
| Jira Username / Email | Enter the username or email address of the Jira account. |
| Jira API Token / Personal Access Token | Enter the API token or personal access token. The value is masked. |
| Jira Project Key | Enter the key of the Jira project. |
| Issue Type | Select the type of issue, for example, Bug. |
| Enable Azure TFS Integration | Turn on this toggle to integrate with Azure TFS. |
| Azure TFS Credentials | Enter the credentials used to connect to Azure TFS. The value is masked. |
| Submit Result to TFS | Turn on this toggle to submit execution results to Azure TFS. Available only when Azure TFS integration is enabled. |
| LambdaTest Build Name | Enter the build name under which the run appears in LambdaTest. |
| LambdaTest Cloud Hub URL | Enter the hub URL of the LambdaTest cloud grid, for example, https://hub.lambdatest.com/wd/hub. |
Desktop Automation
Silicon Grid (Remote Execution) and External Integrations sections are not available for Desktop Automation.
Application Configuration
| Field | Description |
|---|---|
| Application / Executable Path | Enter the full path of the executable (.exe) file of the desktop application. |
| Application ID | Enter the ID of the application to launch, for example, a UWP application. |
| Application Driver URL | Enter the URL at which the application driver server runs, for example, http://127.0.0.1:4723. |
| WinAppDriver Path | Enter the location of the WinAppDriver.exe file, for example, C:\Program Files (x86)\Windows Application Driver\WinAppDriver.exe. |
| Application Name | Enter the name of the application under test. |
| Element Name | Enter the name of the UI element that the script uses to identify the application window. |
| Download in current directory | Turn on this toggle to save downloaded files in the current directory. |
| Auto Healing | Turn on this toggle to heal locator changes when a UI element changes during execution. |
Mobile App Automation
Silicon Grid (Remote Execution) and External Integrations sections are not available for Mobile App Automation.
Application Configuration
| Field | Description |
|---|---|
| Device Name | Enter the name of the device or emulator, for example, generic_x86. |
| Platform Name | Select the operating system of the device, for example, Android. |
| Platform Version | Enter the operating system version, for example, 9.0. |
| Automation Engine | Select the automation engine, for example, uiautomator2. |
| Device UDID | Enter the unique device identifier, for example, emulator-5554. |
| App Package | Enter the package name of the Android application. |
| App Activity | Enter the name of the Android activity that launches the application. |
| Bundled Id | Enter the bundle identifier of the iOS application. |
| Appium / Remote URL | Enter the URL of the Appium server or remote hub, for example, http://127.0.0.1:4723/wd/hub. |
| Real Mobile Device | Turn on this toggle to run on a physical device instead of an emulator or simulator. |
| Xcode Org ID | Enter the development team ID used to sign WebDriverAgent for real iOS devices. |
| Xcode Signing ID | Enter the signing identity used with the Xcode Org ID, for example, iPhone Developer. |
Mobile Site Automation
Silicon Grid (Remote Execution) and External Integrations sections are not available for Mobile Site Automation.
Application Configuration
| Field | Description |
|---|---|
| Device Name | Enter the name of the device or emulator, for example, generic_x86. |
| Platform Name | Select the operating system of the device, for example, Android. |
| Platform Version | Enter the operating system version, for example, 9.0. |
| Automation Engine | Select the automation engine, for example, uiautomator2. |
| Device UDID | Enter the unique device identifier, for example, emulator-5554. |
| Application URL (M-site) | Enter the URL of the mobile website under test. |
| Browser Name | Select the browser on the device, for example, Chrome. |
| Appium / Remote URL | Enter the URL of the Appium server or remote hub, for example, http://127.0.0.1:4723/wd/hub. |
| Real Mobile Device | Turn on this toggle to run on a physical device instead of an emulator or simulator. |
| Xcode Org ID | Enter the development team ID used to sign WebDriverAgent for real iOS devices. |
| Xcode Signing ID | Enter the signing identity used with the Xcode Org ID, for example, iPhone Developer. |
Settings common to all automation types
The following sections are available across all automation types with similar fields.
Timeouts and Retry Logic
| Field | Description |
|---|---|
| Maximum Time In Seconds To Wait For Control | The maximum time, in seconds, that the script waits for a UI element before the step fails, for example, 30. |
| Retry Failed Test Case Count | The number of times a failed test case is retried automatically, for example, 1. |
| Maximum Time In Milliseconds To Wait For Page | The maximum time, in milliseconds, that the script waits for a page to load, for example, 15000. Not available for Desktop Automation; replaced by Maximum Time In Milliseconds To Wait For Application. |
| Time Interval In Milliseconds To Wait For Page | The interval, in milliseconds, at which the script checks whether the page has loaded, for example, 500. Not available for Desktop Automation; replaced by Time Interval In Milliseconds To Wait For Application. |
| Maximum Time In Milliseconds To Wait For Application | Desktop only. The maximum time, in milliseconds, that the script waits for the application to launch, for example, 5000. |
| Time Interval In Milliseconds To Wait For Application | Desktop only. The interval, in milliseconds, at which the script checks whether the application has launched, for example, 500. |
Logging and Debugging
| Field | Description |
|---|---|
| Log Level | Select the level of detail written to the execution log, for example, INFO. |
| Enable Debug Log | Turn on this toggle to capture detailed debug information. Not available for Desktop Automation. |
| Highlight Web Element | Turn on this toggle to highlight each UI element in the browser as the script interacts with it. Web only. |
| Network Log | Turn on this toggle to capture browser network activity. Web only. |
| Print Text In Console | Turn on this toggle to print log text in the console. Not available for Desktop Automation. |
| Attach Logs to Test Report | Turn on this toggle to attach execution logs to the test report. Web only. |
| Capture XPath | Turn on this toggle to capture the XPath of elements the script interacts with. Web only. |
Notifications and Email Reporting
| Field | Description |
|---|---|
| To Email | Enter the email address that receives the execution report. |
| From Email | Enter the email address from which the report is sent. |
| From Password | Enter the password of the sender email account. The value is masked. |
| Test Status For Email Alert | Select the test status for which an email alert is sent, for example, Passed. |
| To Email Additional Receiver List | Web only. Enter additional email addresses that should receive the report. |
| Send Email For Failure Percentage | Web only. Enter the failure percentage at which an email is sent. |
Screenshots and Video Recording
| Field | Description |
|---|---|
| Screenshot on Success | Turn on this toggle to capture a screenshot when a step passes. |
| Screenshot on Failure | Turn on this toggle to capture a screenshot when a step fails. |
| Screenshot on Every Step | Turn on this toggle to capture a screenshot for every step. |
| Full Page Screenshot | Turn on this toggle to capture the entire page instead of only the visible area. Not available for Mobile App Automation. |
| Desktop Screenshot | Turn on this toggle to capture the entire desktop screen. Not available for Mobile App and Mobile Site Automation. |
| Store Screenshot | Turn on this toggle to save captured screenshots as files. Not available for Mobile App and Mobile Site Automation. |
| Video Recording on Success | Turn on this toggle to record a video for passed test cases. |
| Video Recording on Failure | Turn on this toggle to record a video for failed test cases. |
| Enable Separate Failure Report | Turn on this toggle to generate a separate report containing only failed test cases. |
| Report Folder | Displays the folder where reports are stored. Not editable. Web and Desktop only. |
Visual Validation and Assertions
| Field | Description |
|---|---|
| Enable Soft Assertion | Turn on this toggle to continue execution when an assertion fails. All failures are reported at the end instead of stopping at the first failure. |
| Enable Compare Image | Turn on this toggle to compare captured images with expected images. |
User Authentication and Security
| Field | Description |
|---|---|
| Username | Enter the username used for authentication. |
| Password / Token | Enter the password or token. The value is masked. |
| Project Name | Enter the name of the project, for example, Amazon. |
Custom Inputs
Use Custom Inputs to add your own name-value pairs, for example, WebdriverPath.
Add a custom input.
Click the plus icon next to Custom Inputs, then enter the Input Name and Value. The input appears in the table.
Edit or delete a custom input.
Use the edit and delete icons in the Actions column to modify or remove an entry.
The custom input will then appear in application settings.
| Column | Description |
|---|---|
| Input Name | The name of the custom input, for example, WebdriverPath. |
| Value | The value of the custom input. |
| Actions | Edit or delete the custom input. |
Summary Description of Access Settings Page
In Access Settings, as an admin, you can assign permissions to users to perform the tasks.
Perform the following:
Select a project created by you and navigate to the settings.
Select the Access Settings.
In this Access Settings page, you can assign permissions to add, edit and delete the capabilities by selecting the relevant checkbox.
For example, as an admin, if you uncheck the permissions for generating Auto Generate Test Cases, then the team member will not have access to use Auto Generate Test Cases feature.
The following table provides the available access settings options that an administrator can assign to a user.
This applies to web and mobile automation:
| Access Settings option | Description |
|---|---|
| Node Feature Permission | As an admin, you can assign access to the user to add, edit, and delete a feature associated with a node. As a user, when the admin removes access to add a node, the Add Features button will be disabled, preventing you from adding new features. However, you will still be able to modify existing features. Similarly, when access to edit or delete is removed, you will be restricted from performing those actions. |
| Record Scenario/Scenario List | As an admin, you can assign access to the user to record a scenario by selecting or unselecting the 'Can add' checkbox. By doing this, Record Scenario button is enabled or disabled in the Main Canvas. Additionally, you can provide access to the user to add, edit and delete a test case in the Edit Scenario window. |
| Auto Test Cases | As an admin, you can assign or unassign access to the user to use Auto Generate Test cases feature by enabling and disabling this feature. |
| Node Controls Permission | As an admin, you can assign access to a user to add, edit and delete a UI element (control) associated to a feature. |
| Canvas Save Permission | As an admin, you can assign or unassign access to a user to save the modifications made in Canvas. |
| File Permission | As an admin, you can remove access to a user to upload or create any file. Upload file or create file option will be disabled for a particular project. As a user, you will be still be able to edit and delete an uploaded or created file. Additionally, as an admin, you can also restrict the access to edit and delete a file by removing access to edit and delete options. |
| Project Permission | As an admin, you can remove access to a user to delete a created project. Delete button will be disabled when you access as a user. Also as an admin, you can remove access to a user to edit a project. Update button of project settings will be disabled when you access as a user. |
| Upload File in Customize Script | As an admin, you can grant a user access to edit the generated scripts for a specific project. |
| Multiple Files Delete Permission | As an admin, you can assign access to a user to delete multiple files from the project folder. By default, Delete all option will be disabled to prevent any unintended file deletion from a user. |
| Script Execution Permission | As an admin, you can grant a user access to Execute the generated scripts for a specific project. |
| Update Customize script with latest Global Changes | Allows users to compare a project's customized script with the latest global script, review differences, and selectively apply updated sections or add missing files. |