addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwchatcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobegmailgoogleimageimagesinstagramlinklocation-pinmagnifying-glassmailminusmoremuplabelShape 3 + Rectangle 1outlookpersonplusprice-ribbonImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruseryahoo

Cocoa Komittee

CocoaPods is hosting a discussion panel.  The Komittee is an event where we will take people with strong opinions, and get them started on a contentious topic and see if we can learn something from the process. Testing in general is a hot topic. Mix that with a tight platform, closed tools and you've got a lot of flames.


• QA vs Automated Unit testing

• Testing units of code vs Testing behaviour

• Obj-C implementation strategies vs other ecosystems

• Time management

• Ways to improve testing for everyone


• @dblock

• @benjaminjackson

• @lazerwalker

• @klaaspieter

• @paulyoung

• @btgerst


Join or login to comment.

  • Frank R.

    I really like having tests to confirm that some sequence of events is happening like I think they are.

    One thing I was thinking about at the talk that I didn't hear mentioned was the appropriateness of automated testing to edge cases (out of space, something happening at just the vulnerable time, fillign the buffer just so full). It can be really difficult to create an edge case from the UI.

    My question is how much scaffolding people end up writing around their tests? Even using appropriate mocking and testing frameworks, I find that I end up writing quite a bit of code to create fake environments and perturb them in order to see that my code correctly perceives the environment. Technically this would be integration testing since I'm looking at how a system of actors behaves. Does this sound familiar at all to anyone else?

    March 1, 2014

  • Jeff B.

    Excellent discussion. I'd be interested in hearing more about people's strategies for testing — i.e., when you're creating a new view controller what are the first tests you write, how do you measure / think about test coverage, etc. I'd love to see a follow-up tied more directly to tools and approaches.

    February 26, 2014

  • Michael V.

    Awesome- like watching seven generals discuss battle tactics! I could listen to this all day :)

    2 · February 26, 2014

  • Nathaniel L.

    Awesome meetup. Learned a ton, great speakers and really well organized. Great vibe overall

    February 25, 2014

  • Daniel T.

    Nicely fueled discussion - thanks for organizing this Orta!

    February 25, 2014

  • Michael S.

    Fantastic panel discussion. Only comment for improvement would be that someone could ask for the definition of terms or names when thrown out- "smoke testing" was eventually, but also at one point talking about something called Hockey? Just an example. Still great.

    February 25, 2014

  • Justin M.

    Hands down the best iOS meetup I have attended. Thank you Orta, for organizing, and all the speakers for sharing your wisdom and experiences!

    3 · February 25, 2014

  • Orta T.

    I've added Landon Fuller to the panel. You might know him from his work on the Mike Ash blog, or from sharing how to run tests on iOS since 2008.

    4 · February 12, 2014

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy