User interface visibility
You can choose to hide or show Memory Validator during the test, as well as the window of the target application.
Forces the Memory Validator user interface to be displayed during the test.
This is useful for debugging a command line session that is not working, for example inspecting the Diagnostic tab for messages related to the test.
You wouldn't normally use this option when running unattended regression tests.
This causes Memory Validator to never display dialog boxes in the target application that is being profiled.
This applies even for warning and error dialog boxes.
The intended use for this option is for when you are running command line sessions on unattended computers and you have automated processes that may kill the Memory Validator user interface if something goes wrong. Actions such as this then cause the stub to recognise the user interface has gone away and display an error warning.
Hides the Memory Validator user interface during the test.
-launchAppHidden
Hides the target application during the test.
Depending on your application, this may not work and may not even be suitable.
This is equivalent to setting the wShowWindow member of the STARTUPINFO struct to SW_HIDE when using the Win32 CreateProcess() function.
It's useful if you're testing console applications that have no user interaction, as it prevents the console/command prompt from being displayed.
For GUI applications this option very much depends on how your application works.
For interactive applications, it's clearly has no use, but for some, hiding the GUI may help prevent various windows messages from being processed.
Typically, for complex applications, it's better to design this capability into your application and control it via a command line, which can be passed in from Memory Validator via the -arg option.
