Unexpected behaviour when trying to touch something which doesn't exist

[Matthew Flint]

Hey,

I have a tab-bar app, where there is no "Third" tab. If I do this:

[[app.tabBarButton.label text:@"Third"] should].exist;

... then the test fails as expected, so there is a call to
"UILog.onExampleException:". The exception is raised in
"UIQueryExpectation.exist:" (line 18 in SVN revision 82). But if I do
this:

[[app.tabBarButton.label text:@"Third"] touch];

... then the very same exception is raised - but this time it is
dumped to the console and the Xcode debugger halts the thread. If I
choose to run on, then the app is terminated.

What would explain this difference of behaviour?

I wouldn't expect to have to check "exist" explicitly before calling
"touch" each time.

Thanks!
Matthew

[Pete Hodgson]

Not sure, but it might be that you're seeing a side-effect of the bug in 4.x iOS running in the simulator where exceptions thrown within an NSInvocation are not catched and instead crash the app.

http://pivotallabs.com/users/amilligan/blog/articles/1302-objective-c-exceptions-thrown-inside-methods-invoked-via-nsinvocation-are-uncatchable

--
You received this message because you are subscribed to the Google Groups "UISpec" group.
To post to this group, send email to uis...@googlegroups.com.
To unsubscribe from this group, send email to uispec+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/uispec?hl=en.