Extended settings - defaults args and configuration of layout

You can adjust TestExecWindow to your needs. More options for individual configuration are available via the button "..." in the upper right corner. Selecting it leads to a display of the following options:

Default args
define default args, which are used in addition to the args used for selecting a test suite or test case. This may be useful to activate some test behaviour common for all test suites or test cases.

List "only test groups"
decide whether to see both test suites and contained test cases or restrict visibility to one of them

List "sort as read"
choose an appropriate sort order

List "hide log"
hide the log pane if not needed

List "wait for test app max 10 min"
wait indefinitely for termination of a test or set one of several predefined time intervals

List "leak check"
activate or deactivate checking for memory leaks. The leak check assumes that your test app will use elementary memory leak detection facilities of C runtime ("_CrtSetDbgFlag(.._CRTDBG_LEAK_CHECK_DF)"). In case of leaks corresponding messages are written to stdout/stderr ("Detected memory leaks..."). TestExecWin will simply check test output from Visual Studio pane to decide whether leaks are existing or not. In combination with a separate run of each testcase you may identify the evil test cases.

List "regular output"
rise output level within log pane (may be useful when looking for problems)

When the changed options from above are hidden again the configured window will look like:

Advanced options

Additional options are available within the options section of Visual Studio. Navigate to menu "Tools" (or "Extras") / "Options" and then within the list on left side look for entry "TestExecWindow".

If there are no entries visible on the right side, please close the option window again and reopen it. Now the entries should be visible. This seems to be a bug in Visual Studio and may depend on the version you have installed.

Option: Build solution before starting test
If this option is active, then each time when you push one of the "Run" buttons within TestExecWindow first the current solution is built. If build fails then the test will not be started. Only if build succeeds the selected test cases are executed.

This has the following advantages:

You may have reasons for not activating this option:

In both cases you can think of using smaller test solutions where only such code is contained which is related to a specific topic or to a limited set of SW modules.

Option: Limit CPU for StdOut
If your test executable produces bursts of messages to stdout (which are directed to log pane of TestExecWindow) the Visual Studio GUI sometimes seem to hang. It is now possible to activate a yield for the thread receiving the output burst. A typical output burst may be caused by memory leak messages at program termination.