Re: [Cedar] Test Case '-[Spec example]' started.

[Adam Milligan]

Usually if you don't get a line number with a failure it's because the spec failed due to an uncaught exception, rather than a failed expectation.  Cedar wraps each example in an exception handling block, and reports any exceptions that escape the example runs, but at that point it's impossible to show the line number of the code that actually caused the exception; that information has been lost.  If you find yourself in this situation you can set an exception breakpoint, which will trigger when the exception is thrown and highlight the line that is causing the failure.

Based on the snippet you pasted below it appears that you're running into some sort of problem with OCMock.  I can't give much more detail than that with what I know, but OCMock certainly does throw exceptions in a number of cases.

On Fri, Nov 2, 2012 at 1:19 AM, Mikhail Dikov <mdi...@gmail.com> wrote:

Hi All,

For some of my tests I get an error that's different than the rest and it is not linked to the file with the spec. So instead of just double-clicking on the test and getting to the spec you have to go hunt where the failed test is. 

Does anybody know why this happens?

The test's look tile this in the output and they always start with Test Case -[Spec example] which is not a spec name I use:

Test Case '-[Spec example]' started.

(null):0: error: -[Spec example] : TopicViewController content view should slide open # OCM