Working with legacy code can be a daunting task, but Test Automation could make it manageable.

By taking a slightly more pragmatic approach (rather than holding on to a traditional one) on Test Automation, we could breathe new life into legacy code and keep it running smoothly for years to come. Being pragmatic implies sometimes having to let go of best practices like upholding certain standard and metric like code- and test coverage that in some cases are just not realistic given the essence of time in a revival/survival situation.

In this talk, we'll discuss strategies like TDD (amongst other things) that, if applied with a little bit of pragmatism, are perfect for the revival of your legacy project. Also I'll give you some tips on figuring out where to start (and stop) in a 'low-coverage-situation' and how to identify the low-hanging fruit to quickly build an effective test suite to reduce the biggest risks.

Whether you're a seasoned engineer or just starting out, this talk will offer valuable tips for reviving legacy code with Test Automation. Sooner or later, you'll have to deal with legacy!

preferred session duration: 40 - 50 min