Bug 567350 - Error in Red bar display and failure indication in test cases, when used C/C++Unit(Cpputest plugin) with eclipse platform for unit testing.
Summary: Error in Red bar display and failure indication in test cases, when used C/C+...
Status: NEW
Alias: None
Product: PDE
Classification: Eclipse Project
Component: Build (show other bugs)
Version: 4.16   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: pde-build-inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2020-09-25 07:40 EDT by Meghana G M CLA
Modified: 2022-09-16 11:05 EDT (History)
1 user (show)

See Also:

Attachments
There are 18 test cases, but only 15 have been listed under the test run. Evidenetly neither are the failures indicated nor is the red bar displayed. (318.47 KB, image/png)
2020-09-25 07:40 EDT, Meghana G M CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Meghana G M CLA 2020-09-25 07:40:41 EDT 
Created attachment 284265 [details]
There are 18 test cases, but only 15 have been listed under the test run. Evidenetly neither are the failures indicated nor is the red bar displayed.

I have downlaoded the CppuTest pacakage from the link;"https://github.com/cpputest/cpputest " and i have set it up in eclipse 4.16 for unit testing in eclipse platform using cygwin.

As i started integrating the unit test for our project, i noticed that only the test cases which were passing were listed under the test runs and neither is the red bar displayed indicating that some test cases have failed.

So, kindly help me find a reason behind this.

I have attached a picture which would pretty much explain what is the bug i am referring to.
Comment 1 Eclipse Genie CLA 2022-09-16 11:05:53 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.