User interface visibility
You can choose to hide or show Thread Validator during the test, as well as the window of the target application.
Forces the Thread 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 thread tests.
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 Thread 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 Thread Validator user interface during the test.
-launchAppHidden (for backwards compatibility only)
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 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 Thread Validator via the -arg option.
Shows the target application during the test.
This is equivalent to setting the wShowWindow member of the STARTUPINFO struct to SW_SHOW when using the Win32 CreateProcess() function.
-launchAppShowMinimized
-launchAppShowMinNoActive
-launchAppShowNA
-launchAppShowNoActivate
-launchAppShowNormal
As well as the previous two options to show or hide the target application during the test there are other options equivalent to values that can be used in the STARTUPINFO struct.
The options are equivalent to the setting the wShowWindow member to the following values
Option |
wShowWindow member |
Launched application is shown... |
-launchAppShowMaximized |
SW_SHOWMAXIMIZED |
Maximized and activated |
-launchAppShowMinimized |
SW_SHOWMINIMIZED |
Minimized and activated |
-launchAppShowMinNoActive |
SW_SHOWMINNOACTIVE |
Minimized and not active |
-launchAppShowNA |
SW_SHOWNA |
Shown at current size and position but not activated |
-launchAppShowNoActivate |
SW_SHOWNOACTIVATE |
Show at most recent size and position but not activated |
-launchAppShowNormal |
SW_SHOWNORMAL |
Show at original size and position and activated |
-hideCommandPrompt
Causes any launched console window to be shown or hidden during the test.
If an error occurs when launching the application, the error will be reported on the command line.
Refreshing the interface after test completion
You can run automated tests that leave the user interface open after completion,
The following options are used to automatically refresh the main data tabs in Thread Validator once a test is complete.
-refreshLocks
-refreshPerThreadLocks
-refreshCurrentLocks
-refreshThreads
-refreshCoverage
-refreshActiveObjects
-refreshAnalysis
-refreshObjects
-refreshWaitChain
