Open Radar

 
Summary:

For full details, see this blog post:
http://www.bornsleepy.com/bornsleepy/mysterious-case-unit-tests-ran-speed-light

Essentially, when a unit test bundle fails to load because of a missing shared library, otest crashes and displays some spurious advice about garbage collection.

XCode then compounds this problem by presenting the user with a UI which suggests that all tests have run successfully.

Steps to Reproduce:

Make a unit test that relies on a custom shared library which isn't present when the test runs.

Expected Results:

Xcode should report that your tests failed to run. If possible it should indicate that the unit test bundle failed to load because of a missing library. In an ideal world it should tell you which library, and which library was trying to load it (ie it may be a dependency of a dependency).

Actual Results:

Xcode reports that otest crashed, but only in the console. In the Log Navigator Xcode shows a successful (green) banner, even though no tests actually ran.

Regression:

Notes: