Overview

The flags in the Advanced section of a test step of our application offer users granular control over specific functionalities that can impact the behavior and performance of the application. These flags are designed for advanced users who need to customize the application’s behavior for specific scenarios, debugging, or performance optimization.

The flags available in the Advanced section, as depicted in the provided image, include:

1. Skip Screenshot
2. Clear Cookies
3. Skip Scroll
4. Enable Force React
5. Positional Selection
6. Override Default Self-Heal
7. Enable Timing Model Override

Accessing and Enabling/Disabling Flags

1. Accessing the Advanced Setting:

   • Expand  any action to see Action Settings with options for editing, deleting, and more.
     
   • Locate the Advanced button and click on it and now we will get the advanced setting Flags, where these flags are displayed.
     

Purpose and Usage

1. Skip Screenshot:

   • Purpose: This flag allows the user to disable the automatic screenshot functionality during a test or process.
   • Usage: Enable this when you want to skip taking screenshots, which can help in scenarios where screenshots are unnecessary and may slow down the process.

2. Clear Cookies:

   • Purpose: This option clears cookies before starting the next session or process, ensuring a clean environment.
   • Usage: Useful when testing login flows or other scenarios where cookies might impact the outcome. Enabling this ensures each session starts with no residual data from previous sessions.

3. Skip Scroll:

   • Purpose: Prevents the application from automatically scrolling to elements during interactions.
   • Usage: Enable this when you are certain that all elements are within the viewport and scrolling is unnecessary. This can help reduce the time taken for operations.

4. Enable Force React:

   • Purpose: Forces the React application to re-render components during tests.
   • Usage: Useful in scenarios where dynamic changes need to be tested, ensuring that components reflect the latest state after each interaction.

5. Positional Selection:

   • Purpose: The Positional Selection Flag enables you to select positions even when the data is dynamic. For instance, if there’s a table in the application where you need to select the first row's data during each execution, but the data shifts to the next row with every run, the ML selection system typically chooses based on the available data in any row. In such cases, the Positional Selection Flag ensures that the first-row element is consistently selected during each execution based on its longitude and latitude coordinates
   • Usage: This is helpful when dealing with dynamic content where element attributes may change frequently, but their position in the DOM remains consistent.

6. Override Default Self-Heal:

   • Purpose: Disables or overrides the self-healing mechanism that automatically adjusts to minor changes in the application’s UI.
   • Usage: Use this option if you want to strictly adhere to the initial test configurations without allowing automatic adjustments, which might be necessary for precise test validation.

7. Enable Timing Model Override:

   • Purpose: Overrides the default timing model used for synchronizing operations.
   • Usage: This is useful for advanced users who need to customize timing settings for specific performance tuning or debugging.

Conclusion

The flags in the Advanced section are powerful tools for users who require more control over the application's behavior. Understanding when and how to use these flags can significantly improve testing accuracy, performance, and overall user experience.

For further assistance, please refer to the application’s user manual or contact support.