Make it possible to add Keyboard Keypress steps against a target element from the Step Builder.
Currently the only way to add Keyboard Keypress actions is through a coded step that sends desktop actions.
Add functionality to delete all steps that do not match your filter.
After I filter out the unnecessary domains, I delete the individual steps. The primary reason that I perform this manual deletion is to detect extra Think Time steps which may linger after the filtering.
Add functionality to change all Think Times to the same value for the entire User Profile.
This would save having to go into each Think Time step and making a manual modification. This would save time and help ensure no stray values of Think Times (say 200 instead of 20) were entered.
Add a toggle functionality for custom dynamic targets in order to enable/disable each on or all of them.
In the current state, you have to delete your custom dynamic target in order to disable it from your User Profile. That way you lose the information there and if you need it again, you must create it from scratch.
Copy a User Profile with its current state of custom dynamic targets.
The existing workaround is to copy the whole load test, but that makes the project unnecessarily large and does not cover all scenarios. It would be helpful to be able to copy existing User Profile in its current state.
Group custom dynamic targets with the same source step and value.
That way you can make changes to a group of dynamic targets at once. In this regard, maybe it will be helpful to allow multiple destination steps for one custom dynamic target.
Currently the popup window for editing user profile, choosing dynamic target and adding new dynamic target are all opened on top of each other. This prevents the user from going back to the previous windows to view steps and request details.
It would be great improvement in usability to be able to switch back to the different windows while designing your load test.
At this point it is possible to run a WPF application with arguments only as a workaround - starting a separate process in a coded step as given in this example. It would be more useful if this feature is implemented when configure the WPF app in the test.