Multi-session Intelligent Smoke Test
The San Diego release makes the much-anticipated Rimo3 Multi-session Intelligent Smoke Test available to all customers. Building on the existing Intelligent Smoke Test (IST) the Multi-session smoke test launches applications concurrently in different user sessions on a multi-session capable version of Windows to provide the same revolutionary insights into the application’s behavior in each session as the existing IST.
These insights help customers moving to a multi-session OS for the first time understand which applications are suitable for concurrent use, such as when looking to leverage shared Windows 10/11 session hosts in AVD (Azure Virtual Desktops).
Discover applications in customer locations
It is now possible to configure the Discovery task to scan custom locations, in addition to the Program Files, Program Files (x86) and LocalAppData folders, for application executables. This enables executables installed to these custom locations to be selected for testing if they are not already targeted by a shortcut.
The Discovery task now also includes a configurable post install delay so that installers that run asynchronous post install activities have time to complete once the main installer has finished. This ensures that resources such as shortcuts that are created by separate processes post install are captured by the Discovery task to be included in the Intelligent Smoke Test.
Exclude Uninstall Shortcuts from the Intelligent Smoke Test
Some applications, when installed using an “all defaults” install, will include a shortcut to uninstall the application. This can potentially impact the automated Intelligent Smoke Test therefore if such shortcuts are detected during Discovery they will not be automatically selected for testing. If a legitimate shortcut is incorrectly identified as an uninstall shortcut it will be possible to edit the Package Detail in Rimo3 Cloud and reselect the shortcut for testing.
As can be seen in the screenshot above an uninstall shortcut was identified but it was not automatically selected for testing.
