NorDev 2: Simon Elliston Ball: Glimpse & Phil Nash: Is it really possible to TDD iOS apps?

What: Simon Elliston Ball: Glimpse & Phil Nash: Is it really possible to TDD iOS apps?

When: Wednesday, July 10, 2013 @ 6:30p

Where: Virgin Wines, 4th Floor, St James' Mill, Whitefriars, Norwich, NR3 1TN

Sign-up: http://www.meetup.com/Norfolk-Developers-NorDev/events/119849182/

Phil Nash: Is it really possible to TDD iOS apps?
@phil_nash

How feasible is it to develop iOS (or any mobile) apps using Test Driven Development?

Mobile brings with it numerous challenges and differences in culture and mindset that have led some to question if it is worth even trying.

We'll look at some of those challenges and how to overcome them - as well as when it might be better to take a different approach.We'll be using iOS in our examples but many of the concepts generalise to other platforms. Some familiarity with iOS development will be needed in places, though. A basic understanding of TDD is also assumed.

All the principles discussed have been used in high-profile real-world applications.

Phil has spent much of the last three decades trying to work out how to transform percussive actions on a keyboard into patterns of electrical pulses that seem to make some people happy. Along the way he has discovered that sometimes you need to get other people involved too and generally tries to hang out with those that care about the craft as much as he does.

Outside of contract work, consulting, training and coaching he has authored open source projects such as Catch (a C++ & Objective-C test framework) and several iOS apps. If you're not careful he also speaks at conferences and events.

Simon Elliston Ball: Glimpse - Open Source diagnostics for the web
@sireb

Glimpse is an open source diagnostics framework which shows all the vital server-side info you need right in your browser. We’ll start with a tour, and then I will show you how easy it is to write your own plugins for Glimpse, both private to your project and public open source.

Comments

Write Your Own Load Balancer: A worked Example

I was out walking with a techie friend of mine I’d not seen for a while and he asked me if I’d written anything recently. I hadn’t, other than an article on data sharing a few months before and I realised I was missing it. Well, not the writing itself, but the end result. In the last few weeks, another friend of mine, John Cricket , has been setting weekly code challenges via linkedin and his new website, https://codingchallenges.fyi/ . They were all quite interesting, but one in particular on writing load balancers appealed, so I thought I’d kill two birds with one stone and write up a worked example. You’ll find my worked example below. The challenge itself is italics and voice is that of John Crickets. The Coding Challenge https://codingchallenges.fyi/challenges/challenge-load-balancer/ Write Your Own Load Balancer This challenge is to build your own application layer load balancer. A load balancer sits in front of a group of servers and routes client requests across all of the serv...

Catalina-Ant for Tomcat 7

I recently upgraded from Tomcat 6 to Tomcat 7 and all of my Ant deployment scripts stopped working. I eventually worked out why and made the necessary changes, but there doesn’t seem to be a complete description of how to use Catalina-Ant for Tomcat 7 on the web so I thought I'd write one. To start with, make sure Tomcat manager is configured for use by Catalina-Ant. Make sure that manager-script is included in the roles for one of the users in TOMCAT_HOME/conf/tomcat-users.xml . For example: <tomcat-users> <user name="admin" password="s3cr£t" roles="manager-gui, manager-script "/> </tomcat-users> Catalina-Ant for Tomcat 6 was encapsulated within a single JAR file. Catalina-Ant for Tomcat 7 requires four JAR files. One from TOMCAT_HOME/bin : tomcat-juli.jar and three from TOMCAT_HOME/lib: catalina-ant.jar tomcat-coyote.jar tomcat-util.jar There are at least three ways of making the JARs available to Ant: Copy the JARs into th...

RESTful Behaviour Guide

I’ve used a lot of existing Representational State Transfer (REST) APIs and have created several of my own. I see a lot of inconsistency, not just between REST APIs but often within a single REST API. I think most developers understand, at a high level, what a REST API is for and how it should work, but lack a detailed understanding. I think the first thing they forget to consider is that REST APIs allow you to identify and manipulate resources on the web. Here I want to look briefly at what a REST API is and offer some advice on how to structure one, how it should behave and what should be considered when building it. I know this isn’t emacs vs vi, but it can be quite contentious. So, as Barbossa from Pirates of the Caribbean said, this “...is more what you’d call ‘guidelines’ than actual rules.” Resources & Identifiers In their book, Rest in Practice - Hypermedia and Systems Architecture (‎ISBN: 978-0596805821), Jim Webber, Savas Parastatidis and Ian Robinson describe resour...

Paul Grenyer

Search This Blog