You have tests that are brittle, have complicated set-ups and are amenable to making mistakes in areas that have little to do with the tests - at first sight at least. Developers are loath to make changes, which makes the tests less relevant over time. We want to make our tests easier to handle, but where to start?
In this session you'll get some 'production code', with a challenge to make the tests (and possibly the code) more readable. We'll reflect on what you've done, and give you some pointers to make tests easier to understand - and, therefore, change, extend and reuse.
We'll bring a legacy Java code base for you to work on (since the code is there already, it is not a big problem if you don't program in Java - pair programming will probably work well enough).
This workshop is for developers who want to broaden their view on automated testing and test driven development. Prerequisites: some experience in automated unit / integration / end-to-end testing.
Willem is a software developer and consultant, always looking for better and more fun ways to develop software, and helping others do the same. He is a partner in QWAN and is based in Bath.
Marc Evers works as an independent coach, trainer and advisor on (agile) software development. Marc helps to develop learning organisations to focus on continuous reflection and improvement. Independent at piecemealgrowth.nl and partner in qwan.eu.