Ever seen a code that needs modifications, lack tests and you fear touching would break the working software somewhere else? In this hands-on lab, we learn a way to take a mess - a working code that does provide value every single day - turn that code into testable, cover it with tests and then to use a counter-intuitive way to refactor that code into something where domain concepts find their own places while making modifications easy.

The legacy code dilemma is real - When we have to change code, we should have tests in place. To put tests in place, we often have to change code.

Thus, taking an untested mess is a challenge we face in real life. In this hands-on lab, we go learn thinking on how to approach such a challenge, safely. It also covers why is it important to add test cases - and when? In the lab, we also learn about test readability - and finally how to make a (different) mess to let the design to find it’s shape.

This lab is has 3 steps:
- Turn hard-to-test code into easy-to-test code
- Write test cases
- Find a business abstraction thinking outside-in