xctest

I am writing my first bigger iOS project and I want to use as much of Xcode 5 as possible. Now I want to use testing but I have never done it before. My project uses come Views and dynamic `TableViews. How could I implement the test in the code, so that it makes sense? Please start by watching WWDC '13 session 409 - Testing in Xcode 5 . It's a very good starting point. Next, if you're not feeling confident of your approach to unit testing, I'd recommend reading "Test-Driven iOS Development" by Graham Lee . For now, remember that a unit test tests single "unit" of functionality and does not

I'm trying to test my application using the XCTest framework. I want my single test case to fail if some logical condition holds (using an assertion). I don't want the rest of the code in the test case to run, because this might lead to problems (access to null pointers, for example) I also want the rest of the test case to run normally, and just the failed test to be marked as failed. I've noticed XCTestCase has a property called continueAfterFailure. However, setting it to YES caused the failed test to continue executing lines after the assertion, and setting it to NO caused the rest of the

I have recently updated my Xcode and started having this error. 2014-11-03 15:03:54.222 App[13141:60b] Error loading /private/var/mobile/Applications/677127BD-5230-4D5F-B70E-AF728439D34B/tmp/AppTests.xctest/AppTests: dlopen(/private/var/mobile/Applications/677127BD-5230-4D5F-B70E-AF728439D34B/tmp/AppTests.xctest/AppTests, 262): no suitable image found. Did find: /private/var/mobile/Applications/677127BD-5230-4D5F-B70E-AF728439D34B/tmp/AppTests.xctest/AppTests: code signature invalid for '/private/var/mobile/Applications/677127BD-5230-4D5F-B70E-AF728439D34B/tmp/AppTests.xctest/AppTests'

XCTests are failing with the message: *** Canceling tests due to timeout in Waiting for test process to check in... This just started coming up in the last few days. I'm using Xcode 7.3.1, with iOS 9.3.2 running on an iPhone 6. My app is written mostly in Swift. I've seen some similar posts: Unable to run XCTests on iOS device iOS tests will not run on simulator when using Jenkins through JNLP Those other posts talk about this issue as arising with code signing. Code signing does not seem to be my problem-- I've looked at the KeyChain Access utility and don't see any relevant expired

I’m using the new asynchronous testing capabilities of Xcode 6. Everything works fine when the asynchronous task ends before the timeout. But if the task takes longer than the timeout, things get more complicated. Here is how I’m doing my tests: @interface AsyncTestCase : XCTestCase @end @implementation AsyncTestCase // The asynchronous task would obviously be more complex in a real world scenario. - (void) startAsynchronousTaskWithDuration:(NSTimeInterval)duration completionHandler:(void (^)(id result, NSError *error))completionHandler { dispatch_after(dispatch_time(DISPATCH_TIME_NOW, (int64

One annoying thing when running tests in XCode 6.1 is that the entire app has to run and launch its storyboard and root viewController. In my app this runs some server calls that fetches API data. However, I don't want the app to do this when running its tests. With preprocessor macros gone, whats the best for my project to be aware that it was launched running tests and not an ordinary launch? I run them normally with CMD+U and on a bot. Pseudo code would be: // Appdelegate.swift if runningTests() { return } else { // do ordinary api calls } Eivind Rannem Bøhler Instead of checking if the

There is a cell contains a Collection View. I have set the cells within a Collection View using cell.accessibilityLabel = @"daren_shangjia_0001_add_new_photo_album"; and then in XCTest, I do print(app.debugDescription); I didn't see the accessibilityLabel that I have provided. Element subtree: →Application 0x608000367200: {{0.0, 0.0}, {414.0, 736.0}}, label: '纳豆行' Window 0x608000365e80: Main Window, {{0.0, 0.0}, {414.0, 736.0}} Other 0x608000365880: traits: 8589934592, {{0.0, 0.0}, {414.0, 736.0}} Other 0x608000365b80: traits: 8589934592, {{0.0, 0.0}, {414.0, 736.0}} Other 0x608000365700:

I have a unit test that tests if method throws an exception when condition is present, and method does throws exception as expected. - (void)testMethodThrowsWhenConditionIsPresent { XCTAssertThrows([Foo methodWithCondition: condition], @"Condition is true, method should throw exception"); } Here is the exception source: - (void)methodWithCondition:(someType)condition { if (condition) { [NSException raise: @"condition is true!" format: @"condition is true!"]; } } Why does the test stop at the line the exception is thrown? The test does not go on, it stops at that line, when I expect it to