Bug 357888 - Unit test: No parsing of problems/failed unit tests
Summary: Unit test: No parsing of problems/failed unit tests
Status: REPORTED
Alias: None
Product: kdevelop
Classification: Applications
Component: general (show other bugs)
Version: 4.7.2
Platform: Other Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-12 13:58 UTC by Sven Fischer
Modified: 2016-01-12 13:58 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sven Fischer 2016-01-12 13:58:11 UTC
My unit tests are using cpptest, the tests are running based on CTest rules. When an assertion fails, the source file and line with the failed test is displayed in the console output, but not parsed into the problem view.


Reproducible: Always

Steps to Reproduce:
1. Use a framework-based unit test
2. Use a failing assertion, e.g. CPPUNIT_ASSERT_EQUAL(1,2)
3. Run the unit test under kdevelop.

Actual Results:  
 The failing assertion is displayed in the CTest output, but not parsed and there is no output in the problem view

Expected Results:  
The output of the tests are parsed like compiler output for errors and the result is put into the problems view, so that e.g. jumping with F4 to the next problem is possible.