Over the weekend over 150 people met up in meetups, and many joined online, to try and improve the foundational libraries that the Cocoa community rely on. We made more than 30 pull requests and a lot of people got more exposure to testing in Xcode. Read on for stats.
The jam ran over a 14 hour timespan from 12pm GMT to 6pm PST. We had an active IRC with random banter and people asking useful questions. Twitter too.
One of the greatest things about @CocoaPods test jam is seeing different peoples approaches to testing legacy code.— squarefrog (@squarefrog) April 18, 2015
We’ve wrapped up our first test jam pod: https://t.co/tBNlwUgP6z— Ørta (@orta) April 18, 2015
@robbiehanson_15 Gotcha, yeah, you maintain some seriously popular stuff! I set up some unit test for Cocoapods test jam, nothing critical.— Stepan Hruda (@StepanHruda) April 18, 2015
Every meetup had the freedom to run it however they like, ranging from two people in a room to speakers known for their testing prowess. Interestingly enough, both talked about adding tests to untested code. Hint: you might be interested in their source material: Working Effectively with Legacy Code
We changed the plan on the day to avoid needing a bot. In this case jammers would assign themselves a pod from a big Spreadsheet and this gave people a chance to find libraries that interested them. Here's a collection of the work done, with more probably happening over a longer time frame. Very cool.
As the organiser, I can't be happy enough with how it went. The NYC event helped a lot of people actually start testing. It helped me start to use code coverage as a metric for libraries. It's super easy to add. Hopefully events like this move the baseline of expectations forward a little bit. 👍
If you're interested in doing community work with CocoaPods we're always interested in working with more people on ideas like this. You can get in touch with us via [email protected] ( this goes to Kyle, Samuel, Eloy and myself.)