1. Cedar
Testing in iOS
Jeff Hui

2. WhyTest?

3. WhyTest?
•Catch regressions

4. WhyTest?
•Catch regressions
•Better design

5. WhyTest?
•Catch regressions
•Better design
•Refactor more confidently

6. Why Cedar?

7. Why Cedar?
•Cross-platform

8. Why Cedar?
•Cross-platform
•Fast

9. Why Cedar?
•Cross-platform
•Fast
•Elegant DSL

10. describe(@”bowler”, ^{
beforeEach(^{
// do stuff
});
describe(@”-score”, ^{
context(@”when having a perfect game”, ^{
it(@”should return a perfect score”, ^{
});
});
});
});

11. value should equal(@”someString”);

12. value should equal(5);

13. id runLoop = nice_fake_for([NSRunLoop class]);
// do stuff
NSTimer *expectedTimer = ....;
runLoop should
have_received(@selector(addTimer:forMode:))
.with(expectedTimer, NSDefaultRunLoopMode);
Fakes/Doubles

14. spy_on(controller.textField);
[controller.textField becomeFirstResponder];
controller.textField should
have_received(@selector(becomeFirstResponder));
Spies

15. sharedExamplesFor(@”showing an alert”, ^(NSDictionary*context){
it(@”shows an alert”, ^{...});
});
describe(@”tapping the submit button”, ^{
itShouldBehaveLike(@”showing an alert”);
});
describe(@”tapping another”, ^{
itShouldBehaveLike(@”showing an alert”);
});
Shared Examples

16. • Cedar (github.com/pivotal/cedar)
• PivotalCoreKit (github.com/pivotal/pivotalcorekit)
• CedarShortcuts (github.com/cppforlife/CedarShortcuts)
• BetterConsole (github.com/cppforlife/BetterConsole)