Typically, as developers we treat automated tests like an unwanted child or an unpleasant chore. We write them because Sonar requires minimal coverage, or because colleagues in the team will point out their absence in code review - but if these factors were not present, we would most likely give up on them altogether :) Meanwhile, it turns out that test code can become a starting point for improving the quality of legacy code - because we can afford to do more in tests than in production code. In my presentation, I want to show how to use this approach and prove that tests are not as black as they are painted :)