The paradox: I can't test this code because it's legacy. I need to refractor the code to make it testable. How can I manage that, without breaking existing functionality? I'll need to write some tests, but... argh!

We've all been there! In this talk we'll look at safe ways to refactor and test 'untestable' code - without breaking any existing functionality. Promise!


Please login to leave a comment

Andy Gaskell at 15:10 on 9 Nov 2019

Great talk from Katy with lots of practical notes

Adam Cooper at 15:37 on 9 Nov 2019

Loads of great examples and some good points made!

Great examples and way of leading the presentation. It was technical knowledge with artistic sprincles for me which make it really enjoyable.

Great talk with lots of specific examples

Tim Swann at 14:29 on 12 Nov 2019

I relaly enjoyed this talk and teh code samples; very useful short examples of problems and how to get around them

I did feel that it wasn't quite on the money with the talk title; it was more a How To intro for phpUNIT and didn't really cover refactoring as such, or how to "refacator just enough" to enable testing.

The examples that were provided were brilliant, and oh so well named.. i'd just liked to have seen an example of a first step that removes any fear factor of going from spaghetti code to something testable. For me, I think that bit is missing and would be a very valuabe addition.