Simplify Published App Testing with Login VSI: One Script to Rule Them All!

February 21, 2025

The Script Recorder is a powerful tool for capturing user interactions within an application. These recorded actions are then transformed into automated scripts that simulate real-world user behavior. By leveraging this feature, organizations can automate performance testing and monitoring across their IT environments, ensuring applications perform reliably under various conditions.

Step-by-Step Guide 

1. Introduction to Login VSI’s Script Recorder: Login VSI’s Script Recorder is a powerful tool that records user interactions with applications. This recording can be used to create scripts that simulate actual user behavior, helping you automate testing and performance monitoring. 

2. Recording Your First Script: Launch the Script Recorder and begin recording your interactions with the app. Ensure you cover all necessary steps and interactions to capture a comprehensive script. 

3. Saving and Exporting Your Script: Once you’ve finished recording, save and import the script to your Login Enterprise Virtual Appliance. This script will serve as the automated testing for both desktops and published apps. 

4. Benefits of Using a Single Script 

Using one script for both desktop and published applications offers several advantages:

• Efficiency: Reduces the time and effort needed to manage multiple scripts. 
• Consistency: Ensures uniform testing procedures across different environments. 
• Ease of Maintenance: The script can be updated once and applied universally, simplifying the maintenance process. 

5. Using the Script for Published Apps 

The beauty of Login VSI’s Script Recorder is its versatility. You can use the same script for published apps without needing modifications. There are a couple of ways to do this, giving you flexibility depending on how your environment is configured: 

• Publish the Login Executable and assign it to your virtual user(s). In this scenario, the Launcher will launch the published Login Executable app directly and then proceed with the actions defined in the test. Because the initial session starts seamlessly, all subsequent app launches within the test will also be seamless.  
• Pros: Easy to manage; can combine many actions within the same test; no need to execute scripts or login tasks to kick off the Login Executable. 
• Cons: Apps within the test actions must be present on the same session host 

• Launch the Published App with the assigned virtual user(s), then Start the Login Executable with a Logon Script. With this method, the launcher will launch the published application like a regular user. Afterward, a logon script will start the Login Executable. The script will detect that the app is already running and immediately begin the test. 
• Pros: No need to publish a separate application; better simulates the end-user calling the published app directly 
• Cons: Since Explorer isn’t initialized in a published app, some startup locations (e.g., shell: startup) aren’t processed to start the Login Executable 

Leveraging Login VSI’s Script Recorder significantly reduces the complexity of managing multiple scripts. This approach saves time and ensures consistency and ease of maintenance across your testing environments. 

Are you curious if your published applications perform as well as your desktop workloads? Try it and experience the ease of comparing reports for yourself. Get a demo today!