Bug 357888

Summary: Unit test: No parsing of problems/failed unit tests
Product: [Applications] kdevelop Reporter: Sven Fischer <sven>
Component: generalAssignee: kdevelop-bugs-null
Status: REPORTED ---    
Severity: wishlist    
Priority: NOR    
Version First Reported In: 4.7.2   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

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.