This section lists usability enhancements that have been made in Silk Test 17.5.
Silk Test enables you to record the default action for an object without having to choose. This makes action recording faster and easier. While recording actions against a mobile application or a web application in Microsoft Edge, Mozilla Firefox, Google Chrome, or Apple Safari, you no longer have to select every action in the Choose Action dialog. However, the Choose Action dialog continues to open for objects that do not offer a default action, for example text fields, and you can still open the Choose Action dialog by right-clicking on any object.
Testing a workflow in the UI of your application can often involve UI elements that not always exist. For example, a confirmation button that only needs to be pressed the first time a specific action is executed. In Silk Test Workbench, you can now add decision logic, repetition logic, or verification logic to a test based on whether a control exists or does not exist.
To baseline or store a specific state of a project, including all assets, you can now duplicate the project in Silk Test Workbench.
If your application under test has changed significantly since the last time you have successfully ran a specific visual test against it, you might want to update all screens in the test from the application. With Silk Test 17.5 you can open a result file and simply update all screens in the test.
To decrease the amount of browsers and devices displayed in the Select Application dialog, you can now enable or disable the remote locations in the Edit Remote Locations dialog. When disabling a location, the installed browsers and connected devices are no longer displayed in the Select Application dialog.
Multi application domain enables you to design and implement secure .NET WPF applications. Silk Test Workbench now supports testing WPF applications that use multiple application domains.
To generate compact and easy to read locators for WPF controls, you can now specify any WPF classes that Silk Test Workbench should ignore as transparent classes.