Downloaded 52 times
![New test: CMD+N Objective-C Test Case You get something like this: - (void)testAppDelegate { id yourApplicationDelegate = [[UIApplication sharedApplication] delegate]; STAssertNotNil(yourApplicationDelegate, @"UIApplication failed to find the AppDelegate"); }](https://image.slidesharecdn.com/unit-testing-in-ios-111023232804-phpapp02/85/Unit-Testing-in-iOS-Ninjava-Talk-22-320.jpg)
![Deinflector *bulldog = [[Deinflector alloc] init]; NSArray *results; NSString* msg = @"expected deinflected string did not match!”; // Check deinflection types results = [bulldog go:@" かけた "]; STAssertEqualStrings([[results objectAtIndex:0] word], @" かけた ", @"1st %@"); STAssertEqualStrings([[results objectAtIndex:1] word], @" かける ", @"2nd %@", msg); STAssertEqualStrings([[results objectAtIndex:2] word], @" かく ", @"3rd %@", msg);](https://image.slidesharecdn.com/unit-testing-in-ios-111023232804-phpapp02/85/Unit-Testing-in-iOS-Ninjava-Talk-23-320.jpg)
![CMD + U Xcode will build & run the test suite You get in console: Test Case '-[CardTagTest testUpdateLevelCounts]' passed (0.345 seconds). Test Suite 'CardTagTest' finished at 2011-10-20 05:44:39 +0000. Executed 3 tests, with 0 failures (0 unexpected) in 1.528 (1.529) seconds](https://image.slidesharecdn.com/unit-testing-in-ios-111023232804-phpapp02/85/Unit-Testing-in-iOS-Ninjava-Talk-24-320.jpg)
![New test: CMD+N Objective-C Test Case You get something like this: - (void)testAppDelegate { id yourApplicationDelegate = [[UIApplication sharedApplication] delegate]; STAssertNotNil(yourApplicationDelegate, @"UIApplication failed to find the AppDelegate"); }](https://image.slidesharecdn.com/unit-testing-in-ios-111023232804-phpapp02/75/Unit-Testing-in-iOS-Ninjava-Talk-22-2048.jpg)
![Deinflector *bulldog = [[Deinflector alloc] init]; NSArray *results; NSString* msg = @"expected deinflected string did not match!”; // Check deinflection types results = [bulldog go:@" かけた "]; STAssertEqualStrings([[results objectAtIndex:0] word], @" かけた ", @"1st %@"); STAssertEqualStrings([[results objectAtIndex:1] word], @" かける ", @"2nd %@", msg); STAssertEqualStrings([[results objectAtIndex:2] word], @" かく ", @"3rd %@", msg);](https://image.slidesharecdn.com/unit-testing-in-ios-111023232804-phpapp02/75/Unit-Testing-in-iOS-Ninjava-Talk-23-2048.jpg)
![CMD + U Xcode will build & run the test suite You get in console: Test Case '-[CardTagTest testUpdateLevelCounts]' passed (0.345 seconds). Test Suite 'CardTagTest' finished at 2011-10-20 05:44:39 +0000. Executed 3 tests, with 0 failures (0 unexpected) in 1.528 (1.529) seconds](https://image.slidesharecdn.com/unit-testing-in-ios-111023232804-phpapp02/75/Unit-Testing-in-iOS-Ninjava-Talk-24-2048.jpg)
More Related Content
Similar to Unit Testing in iOS - Ninjava Talk
![UiPath Automation Suite Installation (Hands-On) [2/3]](https://cdn.slidesharecdn.com/ss_thumbnails/automationsuitecommunitysession2-251015095633-a6d862f1-thumbnail.jpg?width=600ounds&width=560&fit=bounds)
Unit Testing in iOS - Ninjava Talk
- 1. Presented by: RossSharrott Long Weekend KK Follow me/us: @rsharrott @long_weekend
- 2. IT & SalesManagers Entrepreneurs Geeks Tokyo, Melbourne, New York
- 3.
- 4. B2C Apps ContractDevelopment Specialize in iOS & Android Consulting Training Mobile Strategy for Enterprise App Development strategy & implementation
- 5. Practical > TheoreticalThe world is not perfect. We are lazy.
- 6. Why Unit Test?Why don’t iOS Devs Do It? The Tools Q&A
- 7. Why Unit Test?Why don’t iOS Devs Do It? The Tools Q&A
- 8.
- 9. It takes longerto write tests. I’m the only developer (and I’m amazing) That’s QA’s job (I’m a developer ) My code takes input from someone else. My boss doesn’t give me enough time to test.
- 10.
- 11. Tests save time.Your own code looks like new code after 6 months. QA is there to help you find real / obscure problems, not regressions. Unit testing is for what you do with inputs. Your boss will give you some time to get started, just ask.
- 12. Why Unit Test?Why don’t iOS Devs Do It? The Tools The future?
- 13. < SDK 2.2had no unit testing at all. Then Unit testing in Xcode, frankly, sucked. Sentest reported the unit tests at build time. Application State was inaccessible. Logic tests only. Hard to debug tests. IDE integration was poor – non-existent.
- 14. Functional & Applicationtesting basically did not exist. Continuous Integration was nigh impossible. We are all spoiled by the tools in most other worlds – selenium, _test, _cover, _mock
- 15. GHUnit Made testingon the device & with state possible FoneMonkey Made selenium like testing possible Various Others… The problem: No IDE integration, somewhat annoying to run.
- 16.
- 17. Why Unit Test?Why don’t iOS Devs Do It? The Tools Q&A
- 18. Unit Testing: GHUnitOCUnit Continuous Integration UI & Integration: Automator, FoneMonkey iCuke, UISpec, etc.
- 19. Pros Running asubset of tests. Nice viewer to see the test results. Setup/Teardown on class or methods Can run on Continuous Integration Can read Sentest so you can switch later Con Additional setup, required for every project New versions of Xcode can break this setup
- 20.
- 21. Pros Easy torun with Xcode (CMD + U) Easy to create new tests (CMD + N) (Almost) no setup Can be run on Continuous Integration Cons No class setup/teardown Must run the entire suite every time
- 22. New test: CMD+NObjective-C Test Case You get something like this: - (void)testAppDelegate { id yourApplicationDelegate = [[UIApplication sharedApplication] delegate]; STAssertNotNil(yourApplicationDelegate, @"UIApplication failed to find the AppDelegate"); }
- 23. Deinflector *bulldog = [[Deinflector alloc] init]; NSArray *results; NSString* msg = @"expected deinflected string did not match!”; // Check deinflection types results = [bulldog go:@" かけた "]; STAssertEqualStrings([[results objectAtIndex:0] word], @" かけた ", @"1st %@"); STAssertEqualStrings([[results objectAtIndex:1] word], @" かける ", @"2nd %@", msg); STAssertEqualStrings([[results objectAtIndex:2] word], @" かく ", @"3rd %@", msg);
- 24. CMD + UXcode will build & run the test suite You get in console: Test Case '-[CardTagTest testUpdateLevelCounts]' passed (0.345 seconds). Test Suite 'CardTagTest' finished at 2011-10-20 05:44:39 +0000. Executed 3 tests, with 0 failures (0 unexpected) in 1.528 (1.529) seconds
- 25. Good News: Itcan be done using xcodebuild & the simulator Most of the popular CI’s can work Bad News: Must have xcode installed – so need a mac OCUnit doesn’t put out junit output by default Tools exist for this Not a lot of Code Coverage tools available yet
- 26. Automator Test automator,uses javascript Included in Instruments iCuke New to the scene, seems like a good start but we haven’t jumped in yet. Future (testing) proof your projects: Set accessibility tags in your apps
- 27. Follow me/us: @rsharrott@long_weekend