tags:

views:

19

answers:

0
+1  Q: 

XCode 3.2.3 STILL does not mark unit test assert failures in the editor

I asked this question before and now the problem seems to have returned with XCode 3.2.3. When I run unit tests and I get an assertion failure I don't seem to get the little message bubbles in the left gutter like I used to. I can hit Cmd+plus to highlight the errant assert and get a partial status at the bottom of the window but I don't see an easy way to get the full assertion failure without digging through the build results window. has anyone else seen this? Did I miss a setting or config ption? What's going on? Other compile errors still show the message bubbles. Help!

related questions

Unit tests for deep cloning
What is the difference between integration and unit tests?
Unit test execution speed (how many tests per second?)
Run PHPUnit Tests in Certain Order
Testing a function that throws on failure
What do you use to Unit-Test your Web UI?
How do you test/change untested and untestable code?
How to make junior programmers write tests?
How do you mock a Sealed class?
RhinoMocks: How do you properly mock an IEnumerable<T>?
What is the best way to do unit testing for ASP.NET 2.0 web pages?
TDD and Mocking Frameworks
Unit testing with VSTest basics
How to set up unit testing for Visual Studio C++
What are the primary differences between TDD and BDD?
What is Your Experience with Unit Testing in Practice?
How can I unit test Flex applications from within the IDE or a build script?
C# Unit Testing Example
How do I unit test persistence?
.NET Unit Testing packages?
Integrating Visual Studio Test Project with Cruise Control
What is unit testing?
Best way to implement unit testing in PHP
.NET Testing Framework Advice
Using combinations of sets as test data