Wednesday 4th July, 2012
9:30am to 11:15am
One-line description: Add a new feature to our deliciously smelling legacy code. But... you have to write a test.
Session format: Tutorial (150 mins)
Abstract:When you start unit testing on an existing project, you are often confronted with code that is initially difficult to test. Dependencies are poorly managed and even writing the first unit test seems a sheer impossible task. Where and how do you start? Why is it your dirty job? Can you still leave before it is too late? Can anybody help?
In this hands on lab we will define the legacy problem – code without tests – and discuss the risks of making changes in such a code base. Then you can practice on real dirty legacy code, where we will guide you in some techniques to add features safely, avoiding pitfalls like task-scope creep.
Audience background: Developers. Experience with a curly brackets language (Java or C#)
Participants should bring laptops. We will work in pairs, only 1 laptop per pair is required. We will provide bootable USB sticks with a complete Java environment and exercises. We also have the exercise available in C#.
Benefits of participating: Get some concrete ideas to start doing test driven development and unit testing in existing code; practice some basic techniques for getting a first test in. When you succeed, the unshakable belief that anything is possible ;)
Materials provided:Handouts with some (UML :) ) diagrams of how the major pieces fit together. We will provide bootable USB sticks with a complete Java environment and exercises. Participants can choose to install on their own machine (and risk losing time. to each their own).
Process:Participants work in pairs. We'll have pairs explain their work on the projector.
Participants should bring laptops. We will work in pairs, only 1 laptop per pair is required. We also have the exercise available in C#.
Independent software developer, freestyle consultant, trainer and coach bio from Twitter
Sign in to add slides, notes or videos to this session