Performing changes to your environment is a fact of life. It’s also a fact that not all changes are equally as good for the user experience. That is why we recommend you validate changes (or newly built environments) before you bring them to production. If you want to test these changes in an automated fashion our virtual user can help.
Of course, it does not stop there, after you have brought the changes to production, it’s important to track their performance over time. This can be done with a very low number of virtual users, without causing any impact on the performance on the system, and without installing any additional agents in the desktop.
Use case example: Let’s say you are upgrading Microsoft Office from version 2010 to Microsoft Office 2013 or 2016. While this sounds like a rather insignificant change, it does significantly impact the user experience, in some cases leading to 25% of the users not being able to log on anymore.