Waitforexpectationswithtimeout

Last year I described a method to implement asynchronous unit testing in Xcode 5. Many APIs on the iOS platform themselves are asynchronous. They may make network requests or write to the local file system. These can be time-consuming tasks that need to run in the background. This creates a problem because tests themselves run synchronously.

So our tests need to wait until they are notified of when the running task has completed. I proposed a method that entailed setting a boolean flag in the unit test and looping in a while loop until the flag was set waitforexpectationswithtimeout false, allowing the test to complete properly. This method worked most of the time but I have never been happy with it, regarding it as a bit of a kludge.

In that blog post I concluded:. In fact, because I was re-using the same pattern in many of my tests, I converted parts of it to waitforexpectationswithtimeout Macro that had to be included in each header file. Well, the good news is that, less than a year later, Apple have delivered a means to implement asynchronous unit tests in an intelligent and offcially supported way. Furthermore, not only have they given us a new version of Xcode 6 still in beta at the time of writing with this new unit testing framework, waitforexpectationswithtimeout they have also delivered a brand new programming language, Swift.

From now on, waitforexpectationswithtimeout of my iOS coding is going to be done in Swift, so the examples below will be in Swift, too. So, how does it work? In line 6 we instantiate a new instance of XCTestExpectation, named readyExpectation.

This will be displayed in the test log to help diagnose failures. It is also possible to set more than one expectation as a condition. Then in line 9 we make the waitforexpectationswithtimeout to the code that needs to be tested. In the completion handler, after making our tests, we call waitforexpectationswithtimeout method fulfill on the expectation. This is equivalent to setting the flag to false in our earlier Objective-C implementation.

The last block of clode starting at line 18 runs waitforexpectationswithtimeout run loop while handling events until all expectations are fulfilled or the timeout is reached. I set the timeout to 5 seconds waitforexpectationswithtimeout be on the safe side. Finally, we have a proper framework for Asynchronous Unit Testing in Xcode!

Asynchronous Unit Testing in Xcode 6 July 13, In that blog post I concluded: You would think that Apple might have provided a solution in XCTest, perhaps similar to the implementation in GHUnit. STAssertTrue success"Should have been success! NSTimeIntervalhandler handlerOrNil: XCTAssertTrue success"saveToURL failed".

XCTAssertNil error waitforexpectationswithtimeout, "Error". September 4, at Asynchronous iOS Unit Tests using XCTestExpectation and waitForExpectationsWithTimeout iOS Unit Testing. Asynchronous unit tests using XCTestExpectation iOS Unit Testing. September 30, at Thank you very much. This article saved my day. Keep up the good work!!!! Recent Posts Hedvig Mollestad Change waitforexpectationswithtimeout Way You Speak to Your Customer Making friends with the Command Line Node Licensing Pedantry Senseless Figures in Front of a Mirror Popular Posts Creating Animated Custom waitforexpectationswithtimeout Unwind Segues in iOS Parsing JSON in iOS Asynchronous Unit Testing in Xcode 6 Documenting your code with comments in Xcode 5 Xcode and Asynchronous Unit Testing Objective-C Singletons — an alternative pattern Archives August July January October September Waitforexpectationswithtimeout July February January December November October September August July June May March February January Categories archi coding eclipse iOS web comment design musik Links My Musik Twitter Archi.