Runner reports all is well when <cassert> assert() fails

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Write a test case:
  TEST_F(Foo, Bar)
  {
    assert(false);
  }

What is the expected output? What do you see instead?
Expected result:
An error message and the assertion failure to be displayed.

Actual result:
All is well. Done x of y. z are disabled.

What version of the product are you using? On what operating system?
1.2.2, Windows 7 x64

Please provide any additional information below.

Original issue reported on code.google.com by [email protected] on 27 Apr 2012 at 7:56

[GoogleCodeExporter]

Runner should verify the exit code of the application and signal if it is 
non-zero.

Original comment by [email protected] on 27 Apr 2012 at 8:00

[GoogleCodeExporter]

I will consider this problem

Original comment by [email protected] on 30 Apr 2012 at 2:10

• Changed state: Started

[GoogleCodeExporter]

The exit code is checked now and an error message is displayed if the error 
code is non-zero 

Unfortunately I see no possibility to find out which assertion failed - gtest 
only outputs:

[==========] Running 1 test from 1 test case.
[----------] Global test environment set-up.
[----------] 1 test from Testbed
[ RUN      ] Testbed.Test1

Original comment by [email protected] on 21 May 2012 at 7:27