Please log in to watch this conference skillscast.
When Graham adopted Test-Driven Development, he turned his back on testing. People think that if they write a couple of tests that show the happy path and the error path, then they have "100% coverage" and are done. If they add those tests to their continuous delivery pipeline, running with the same inputs on every build, then they get "a full regression suite" and can be confident in that they did not break anything. In this talk, Graham will explore techniques that demonstrate that his software works not just for the few examples he thought of when designing it, but for _all_ inputs.
YOU MAY ALSO LIKE:
Graham first learned Objective-C while sat in front of a NeXT Turbostation, and was hooked on its power and simplicity. His career has seen him writing Mac and iOS apps, Java software for particle accelerators, node.js microservices and more. He has written books and given talks for Cocoa developers on application security and test-driven development, and more generally on object-oriented and functional programming, and the skills a programmer needs that aren't programming.