003 iPhreaks Show – Testing Your Application

Panel

Pete Hodgson (twitter github blog)
Ben Scheirman (twitter github blog NSSreencast)
Rod Schmidt (twitter github infiniteNIL)
Charles Max Wood (twitter github Teach Me To Code Rails Ramp Up)

Discussion
03:00 - Why don’t people test in iOS?
06:12 - Testing Definitions and the Mechanics of Testing

Instruments User Guide
TestPyramid

13:00 - Why do we test our code? Why is it worth it?

Feedback
Communication

19:28 - Practicing TDD (Test-driven development)

UI View Controllers

25:33 - Unit Testing is hard
28:01 - Tools

Send Testing Kit aka OCUnit
Application and Logic Tests
Running objective-c tests from the command line (with color) (Ben’s Script based on Eloy Durán’s)
Continuous Integration
Code Coverage
Git Hooks
gh-unit
Kiwi
Cedar
RubyMotion
Writing Tests for RubyMotion Apps
Bacon

42:00 - Frank

Selenium
Zucchini
appium
bwoken
KIF
Calabash
Jenkins
Writing iOS acceptance tests using Kiwi: Pete Hodgson
PublicAutomation

Picks

TextExpander (Ben)
Alfred (Ben)
Jenkins (Ben)
Oban Scotch (Ben)
NSScreencast: Automated Testing with Kiwi (Pete)
Rock Climbing (Pete)
Scarlett Red (Pete)
Test-Driven iOS Development by Graham J. Lee (Rod)
42 (Rod)
Test iOS Apps with UI Automation: Bug Hunting Made Easy by Jonathan Penn (Pete)
Backbone.js (Chuck)
LaunchBar (Chuck)

Next Week
iOS/Mac & differences with Josh Abernathy

Transcript
PETE: So what are we talking about this Tuesday morning?

CHUCK: I'm not sure, but I think we should write a test for it first.

CHUCK: Hey everybody and welcome to Episode 3 of iPhreaks! This week on our panel we have, Pete Hodgson.

PETE: Hello from Butte Lake!

[Ben laughs]

CHUCK: Ben Scheirman...Butte Lake...

BEN: Very well done. Very well done.

[Ben laughs]

CHUCK: Ben Scheirman.

BEN: Hello from Houston!

CHUCK: We also have, Rod Schimdt.

ROD: Hello from Salt Lake City!

CHUCK: Sorry, Rod. I was looking at Pete's picture and I was like "No, I already said Pete".

[laughter]

BEN: Yeah, for those who didn't get the joke we were looking at the transcription from last episode, or from episode 1. And --

CHUCK: Did that get fixed?

PETE: It got fixed, yeah.

BEN: Okay. So originally, Pete said he's from Berkeley and it came through as Butte Lake, which I thought was hilarious.

PETE: I was pretty -- I was looking for the transcript -- it's pretty hilarious how much my accent has closed issues. For whatever personal machine is doing that transcription is definitely challenged by my accent.

CHUCK: We're really sorry to the transcriptionist.

PETE: Yeah.

[laughter]

CHUCK: We will pick our panelist more carefully next time.

PETE: Oh! It's my fault, huh?

[laughter]

CHUCK: Anyway...And you can tell I had to ask if it got fixed because I just asked Mandy to do it and assume it's done.

PETE: Yeah. No, she fixed it. She fixed it very very quickly.

CHUCK: Yeah.

PETE: And I'm used to that. I'm living in a [inaudible] when you found out like you have automated voice systems. They often don't work with British accent so I have to put on like a stupid American accent when I'm...operator!

[laughter]

PETE: Reservations.

[laughter]

CHUCK: It's funny, too, because a lot of times on those automated systems, they have somebody with a British accent or a fake British accent like speaking.

BEN: Yeah.

PETE: Yeah. But they didn't understand British. Siri didn't understand British for a very long time because you couldn't get like, if you lived in the US, you couldn't get American, so you couldn't get British Siri to work with like American information. So if I wanted to actually know about anything about America like where I live, I'd have to use the American version Siri, but she couldn't understand my pronunciation.

[Ben laughs]

CHUCK: So is the British Siri more polite?