如果你使用Eclipse，还有一个非常好的插件叫做 TestRunner 用于运行CDT单元测试，很像Java或Python单元测试。它为你处理单元测试解析。你将得到一个单独的控制台窗口进行单元测试，并使用级别过滤器来排列它们。单击错误/警告可以转到编辑器中的单元测试行号。您还可以在Eclipse中设置详细程度级别以及其他一些设置。

您可以使用Eclipse更新中的以下链接直接安装插件 https：// raw。 github.com/xgsa/cdt-tests-runner/tests_runner_demo/testsrunner/org.eclipse.cdt.testsrunner-updatesite/site.xml

There is already a thread here that partially answers my question .

On Eclipse 3.7.2 I followed the approach provided there and I could successfully accomplish the steps creating and setting up a new error parser and adding it to my current project. After executing my Boost.Test (boost rel. 1.48.0) Unit Test, on the Eclipse console I get the same output as the output I get when no parsing is done (e.g. when executing the Unit Test outside Eclipse (e.g. on a Linux terminal)). I searched for a new Eclipse console where the parsed Unit Test output could be displayed (similar to the consoles by e.g. gcov, gprof or cppcheck in Eclipse) but found nothing alike.

Where should the parsed unit test output be displayed? In case the parsed output shall be displayed in the Eclipse Console view, are there any suggestions what might have gone wrong with the parsing in my case?

Thanks in advance.

P.S.: Thanks to casperOne and kleopatra for teaching me manners.

If you're using Eclipse there is also a really nice plugin called TestRunner for running CDT unit tests much like Java or Python unit tests. It handles the unit-testing parsing for you. You'll get a separate console window for your unit tests and it arranges them with level filters. Clicking on an error/warning takes you to the unit-test line number in your editor. You also can set the verbosity level as well as a few other settings from inside Eclipse.

You can directly install the plugin by using the following link in Eclipse updates https://raw.github.com/xgsa/cdt-tests-runner/tests_runner_demo/testsrunner/org.eclipse.cdt.testsrunner-updatesite/site.xml