LoadGen is a load-testing tool that allows you to validate the performance of your Windows application or website under various levels of simulated user traffic. One key aspect of load testing is control validation, which involves verifying that the controls on your application or website are functioning as expected under the increased load.
A validation is a visual indication that a process has finished. We advise you to add as many validations as possible. As - under load, anything will break - a user action can take an extra amount of time as the load on a machine will increase. 
These indications are one of the following:

The caption of the foreground window

he appearance or disappearance of a window caption in the session; A window caption validation will look at the top-level window of a session. In the Studio options, you will find ways to control how to match a window caption. Options include the location of a match, whether a comparison should be case-sensitive, and whether to use regular expressions instead of a line of text.


Control in the foreground window

This feature is available for Fat Client, Citrix Enhanced, Remote Desktop, VMware Horizon, and Azure Virtual Desktop. The appearance of a control in the top foreground window; in Fat client, you are able to choose a control from the window, e.g. ok button, text, etc. Control validation is the most robust way of validating a user-specific action. With the LoadGen Q4-2022 release we go a step further. 
There are four methods of control validation that LoadGen offers:
  1. Full Visual Tree: This method involves validating a control within the full visual tree of the application or website. This is a comprehensive approach that ensures that the control can be found in the position it should be available. Keep in mind, that when the title of the application changes (i.e. Document1 - Word changes in My saved document - Word) the full visual tree will change and thus the control will not be found by our validation process.
  2. Subtree: This method involves validating a specific control with a subset of the visual tree. This can be useful if you only want to test a control from a specific location of your application or website.
  3. Name and type of a control at control's depth: This method involves validating a specific control based on its name and type, as well as its location (depth) within the visual tree. This can be useful if you want to focus on a specific control but don't want to add a specific visual tree to locate the control.
  4. Loose search: This method involves searching for a control using partial matches for its name and type. This can be useful if you are not sure of the exact location of the control you want to validate.
When using LoadGen's control validation feature, you have the option to specify which control to validate if multiple controls are found at the same level with the same name. By default, LoadGen will validate the first control found with the selected name (which is equivalent to specifying the Nth control as 0). However, you can change this behavior by specifying a different value for the Nth control.
For example, if you want to validate the second control found with a given name, you can specify the Nth control as 1. If you want to validate the third control, you can specify the Nth control as 2, and so on. This can be useful if you have multiple controls with the same name and you want to validate a specific one.
To specify the Nth control in LoadGen, you can use the "Nth control" parameter in the control validation settings. Simply enter the desired value for the Nth control, and LoadGen will validate the control at the specified position within the list of controls with the same name.
Overall, this option allows you to fine-tune your control validation strategy and ensure that you are testing the specific controls that are important to your application or website.


An image appears in an area of the session; An image search will repeatedly search an area of the session for a predefined image. When it finds the image the validation will succeed and the X and Y coordinates of the found location are available in the Last Validation>< and Last Validation Y variables.


Single Pixel

An RGB color of a specific pixel, with a tolerance margin for both color and location; RGB color validation will look at the RGB value of a pixel in the session. You can choose a pixel when you create a validation, and the script will wait for a match on RGB values when running. Options for RGB matching include a tolerance margin, in percentages, for each RGB value of a pixel. This percentage is calculated over the co or range of 0-255. Other options include a location margin; this is the number of pixels around the given coordinate that the script vvi1 00k for a match. The search pattern is snake-like, starting at the top left and walking around the pixel clockwise.


Was this article helpful?
2 out of 3 found this helpful