Download
TestExecWindow is available for free download:
For more info about recent changes, known problems and planned enhancements see
Installation
- Within your old version of "TestExecWindow" export your configured sets of test apps if desired.
- Within Visual studio deinstall your old version of "TestExecWindow" if already existing.
- Close Visual Studio.
- Double-Click downloaded installation file "TestExecWin.vsix". Confirm to install the extension.
- Restart Visual Studio.
- Within the newly installed version of "TestExecWindow" you now can import the saved sets of test apps.
Remark:
During installation files will be copied to C:/Users /[UserName] /AppData /Local /Microsoft /VisualStudio /14.0 /Extensions /[random name like 'sbmfwobd'].wfs. In case of problems deinstallation can be done by simply removing this directory.
Change History TestExecWin for Visual Studio 2022
Actual version is 2022.7.3
- Version 2022.7.3 (01/2024)
- Download TestExecWin_2022.7.3.vsix
- extended functionality: (optional) Run until failure
You can execute your test app repeatedly until a failure occurs. Then you have the chance to examine the test protocol and traces of a failed execution.
- extended functionality: BOOST test cases not belonging to a BOOST test suite are displayed as members of virtual test suite "[no-test-suite]"
- extended functionality: added support for BOOST macros BOOST_DATA_TEST_CASE, BOOST_DATA_TEST_CASE_F and corresponding TTB macro TTB_BOOST_DATA_TEST_CASE
- bugfix: an unmatched occurrence of BOOST_AUTO_TEST_SUITE_END caused incomplete parsing of test cases; now such lines will be ignored and a warning will be written to output pane
- Version 2022.7.2 (02/2022)
- Download TestExecWin_2022.7.2.vsix
- adjusted for Visual Studio 2022, using actualized extension framework
- extended functionality: (optional) Build solution before starting test
You have not to wait until build is completed before you can start your test manually. Simply edit and save your new code and push "Run" within TestExecWindow. If compile fails then test will not be started. Only if compile succeeds the selected test cases are executed.
- extended functionality: optional limit CPU for StdOut
If your test executable produces bursts of messages to stdout 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.
- Default args: added proposal "--log_sink =<PATH_TO_FILE>" for BOOST tests
Change History TestExecWin for Visual Studio 2019
Actual version is 2019.6.5
- Version 2019.6.5 (03/2019)
Change History TestExecWin for Visual Studio 2017
Actual version is 2017.6.4
- Version 2017.6.4 (10/2018)
- Download TestExecWin_2017.6.4.vsix
- extended functionality: now supporting macros BOOST_FIXTURE_TEST_CASE, TTB_BOOST_FIXTURE_TEST_CASE
- change: new default for memory leak checking is "switched off"
- bugfix: improved the way how the correct project configuration (VCConfiguration) is found; this solves following problems:
- "Import from solution" did not import all relevant projects from solution
- when opening Visual Studio directly by clicking on a solution file the current startup project could not be found
- bugfix: log files generated with option "shutdown" were not saved to target directory but to one directory level higher; when building log file path a missing path separator "\" was added
- Version 2017.6.3 (12/2017)
Change History TestExecWin for Visual Studio 2015
Actual version is 1.6.3. Older versions are no longer available online.
- Version 1.6.3 (12/2017)
- Download TestExecWin_1.6.3.vsix:
- improvement for automatic shutdown
- now using a forced shutdown (option "-f") to allow automatic shutdown also when the desktop is locked
- Version 1.6.2 (10/2017)
- improvement for test execution: log files and automatic shutdown
- you can decide to automatically shutdown your computer when all tests have terminated
- before shutting down results from log pane are automatically written to logfile
- logfiles are stored within target directory of current startup project or within temp directory
- Version 1.6.1 (05/2017)
- improvement for test execution: max execution time
- You can optionally define a max wait time interval. When time expires and the current call to your test has not yet terminated the test executable will be killed. The same timeout settings applies to all calls to your test app(s). When running a set of calls (e.g. within the tab with configured test apps or when choosing "Run each" for your test suites) after having killed the (possibly hanging) test app the next call will be started automatically.
- improvement for list of test groups and funcs:
- instead of selecting only a single list entry you now can select multiple entries. When clicking "Run selected" all selected test cases/suites will be executed within a single call to your test application.
- improvement for configured test apps:
- on button click you can scan your current solution and automatically add all found executables with their full execution path to the currently displayed test app set
- on button click you can copy the test suites from current startup project to the currently displayed test app set. When executing the test app set each of the imported test suites will be executed within a separate call of your test executable (similar as you have pushed "Run each" within test group tab)
- on button click you can copy the visible test cases from startup project to the currently displayed test app set. When executing the test app set each of the imported test cases will be executed within a separate call of your test executable (similar as you have pushed "Run each" within test func tab)
- within your configured sets of test apps you can use "//" comments to (temporarily) skip an app from execution or to add arbitrary notes
- when exporting a set of test apps the name of the set is used as default file name
- you can now store 8 sets with test apps instead of 3
- improvement for BOOST-Test:
- added support for macro BOOST_AUTO_TEST_CASE_TEMPLATE
- improvement for log list with test results:
- copy to clip board (e.g. for sending within Email)
- export as regular text file
- improvement for memory check:
- a string of "Object dump complete" within test output is also interpreted as memory leak. motivation: in case of really huge leak reports the limited buffer of output pane will no longer contain the initial message "Detected memory leaks"
- bugfix source file parsser: now macro TTB_TEST_FUNC_DESC will be correctly parsed. You can also use "," and ")" within your test case description
- Version 1.6 (04/2017)
- new feature: added second register card to support testing of a configurable set of test apps. You can define and save 3 different named sets of test apps directly within plugin settings. Additionally you can export and import your app sets (e.g. into next version of this plugin).
- improvement: optionally checks for memory leaks (i.e. checks for text "Detected memory leaks" within test output as written to Visual Studio output pane). Only works for properly configured test applications which have activated a final memory check by C runtime. You can switch off this check, if you are tired of solving leak errors.
- improvement: when started again, automatically restores last settings (e.g. last default args, last used set of test apps, last visibility of GUI controls)
- improvement: added support for nested BOOST test suites
- bugfix: test macros (e.g. BOOST_AUTO_TEST_CASE) which are commented out with "//" are ignored now
- Version 1.5.1 (12/2016)
- bugfix: input text within default args field and selection of several lists were reset when window was moved, docked or reopened
- improvement: When being opened TestExecWin now automatically checks for the current startup project and displays all found test cases.
- Version 1.5 (12/2016)
- Added "Src" buttons to directly jump to source code location of selected test function or test group
- Added additional proposals for default args supporting BOOST and TTB test frames
- Version 1.4 (11/2016)
- Running test application via Run button now causes dynamic color state for project name instead of changing background color of Run button
- bugfix: changing startup project while test is running will now be ignored to avoid inconsistent data state and a possible crash of Visual Studio
Features planned for future versions
- Currently there are no features planned. Let me know if you have special wishes which may be also useful for others.
Next step: Open TestExecWindow
1.8.17