pirafrank / google-toolbox-for-mac

Automatically exported from code.google.com/p/google-toolbox-for-mac
Apache License 2.0
0 stars 0 forks source link

Incorrect message with STAssertTrue and STAssertFalse #29

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Create a test case that uses STAssertTrue or STAssertFalse
2. Have the assertion fail

What is the expected output? What do you see instead?
For STAssertTrue:
The message should be something like expression should be TRUE.
Instead, the message says something like expression should be FALSE

What version of the product are you using? On what operating system?
SVN trunk as of 7/24/09. Mac OS 10.5.6 with iPhone OS 3.0 simulator

Please provide any additional information below.
Maybe I'm missing something, but it seems like the error messages for
STAssertTrue and STAssertFalse are reversed? I created the same tests with
OCUnit and the correct messages are displayed.

Original issue reported on code.google.com by tareca...@gmail.com on 27 Jul 2009 at 4:54

Attachments:

GoogleCodeExporter commented 9 years ago
This appears to have been fixed. Right no I'm seeing '"blah" should be true.' 
for a failing STAssertTrue.

Can you please verify this is true for you as well?

Original comment by dmaclach on 4 Sep 2009 at 9:50

GoogleCodeExporter commented 9 years ago
Hmm, I updated to svn revision 203 but I'm still seeing the same behavior. 
Here's a
new screen shot (from XCode 3.2). I can get the correct messages by changing the
value of isTrue in GTMSenTestCase.h but it seems strange that I'd have to do 
that if
it's working for other people...

Is it possible there's some misconfiguration on my side?

thanks,
cam 

Original comment by tareca...@gmail.com on 6 Sep 2009 at 8:30

Attachments:

GoogleCodeExporter commented 9 years ago
attachment messed up, trying again.

Original comment by tareca...@gmail.com on 6 Sep 2009 at 8:32

Attachments:

GoogleCodeExporter commented 9 years ago
here's a file that reproduces the error for me

Original comment by tareca...@gmail.com on 6 Sep 2009 at 5:08

Attachments: