Saturday, March 2, 2019

Test-Driven iOS Development

File Size: 4.19 Mb

My experience of telling other developers about test-driven development for Objective- C came about almost entirely by accident. I was scheduled to talk at a conference on a different topic, where a friend of mine was talking on TDD. His wife had chosen (I assume that’s how it works; I’m no expert) that weekend to give birth to their twins, so Chuck—who commissioned the book you now hold in your hands—asked me if I wouldn’t mind giving that talk, too.Thus began the path that led ultimately to the yearlong project of creating this book.

It’s usually the case that reality is not nearly as neat as the stories we tell each other about reality. In fact, I had first encountered unit tests a number of years previously. Before I was a professional software engineer, I was a tester for a company whose product was based on GNUstep (the Free Software Foundation’s version of the Cocoa libraries for Linux and other operating systems). Unit testing, I knew then, was a way to show that little bits of a software product worked properly, so that hopefully, when they were combined into big bits of software, those big bits would work properly, too.

I took this knowledge with me to my first programming gig, as software engineer working on the Mac port of a cross-platform security product. (Another simplification— I had, a few years earlier, taken on a six-week paid project to write a LISP program. We’ve all done things we’re not proud of.) While I was working this job, I went on a TDD training course, run by object-oriented programming conference stalwart Kevlin Henney, editor of 97 Things Every Programmer Should Know, among other things. It was here that I finally realized that the point of test-driven development was to make me more confident about my code, and more confident about changing my code as I learned more.The time had finally arrived where I understood TDD enough that I could start learning from my own mistakes, make it a regular part of my toolbox, and work out what worked for me and what didn’t.After a few years of that, I was in a position where I could say yes to Chuck’s request to give the talk.

1. About Software Testing and Unit Testing
2. Techniques for Test-Driven Development
3. How to Write a Unit Test
4. Tools for Testing
5. Test-Driven Development of an iOS App
6. The Data Model
7. Application Logic
8. Networking Code
9. View Controllers
10. Putting It All Together
11. Designing for Test-Driven Development
12. Applying Test-Driven Development to an Existing Project
13. Beyond Today’s Test-Driven Development

Author Details
"Graham Lee"

Download Drive-1

You May Also Like These E-Books:-

Programming Android

No comments:

Post a Comment