To enable more granular control of click step native/non-native configuration, we are introducing test-level click native control. Up until now, native/non-native click step config was set at the project level, but based on customer feedback, we understand the need for more granular control.
With this update, we are enabling users to control the native/non-native click step config directly within the test config. Full documentation may be found here.
This new feature allows customers to run the same test with different browsers, each utilizing its own native/non-native click config.
- Whether it's the test's untitled config or a selection from the config list, users can now customize the attribute to suit their specific needs
- After running such a test, there will be a clear indication that the native (or non-native) override was applied, providing transparency in the test execution process