It looks like we are almost there. It seems that normal test failures are
caught appropriately now. However, other exceptions are making there way up
there. Alas, OCMock checks and Hamcrest assertions are bubbling to the top
still -- this was working before.
Hamcrest: 2010-07-01 15:36:15.458 Tests[30200:903] *** Terminating app due
to uncaught exception 'SenTestFailureException', reason: 'Expected "world",
OCMock: 2010-07-01 15:39:30.206 Tests[30312:903] *** Terminating app due to
uncaught exception 'NSInternalInconsistencyException', reason:
'OCMockObject[NSString]: unexpected method invoked:
I imagine this is the result of some underlying changes in iOS4 in how
exceptions are handled via dynamic invocation. I.E., you can't catch some of
them. Frustrating, indeed. I have added these as tests cases to the project.
On another front. Removing the Main nib file base name entry in the tests
info property list avoids the problem of having to include all of your
You have been very helpful. I have 3-4 projects that went from being unable
to run any tests to at least being able to work through them.
read more »