A nice way to help you refactor legacy code is to use “Characterization Testing” or “Golden Master testing”. These approach provide a quick way to get cover legacy code with _some_ tests. There is a big catch though:<\/p>\n\n\n\n
Unlike regression tests, to which they are very similar, characterization tests do not verify the correct behavior of the code, which can be impossible to determine. Instead they verify the behavior that was observed when they were written.<\/p>https:\/\/en.wikipedia.org\/wiki\/Characterization_test<\/a><\/cite><\/blockquote>\n\n\n\n
You can use a tool like “Approval tests” to quickly set up “Characterization Testing”. Emily Bache has a nice introduction video about working with “Approval tests”.<\/p>\n\n\n\n
After you’ve covered the legacy code using “Characterization Testing”, you can start refactoring the legacy code. At this point, don’t forget to add unit tests for the new code you’re writing.<\/p>\n\n\n\n
For more info have a look at:<\/p>\n\n\n\n
- https:\/\/en.wikipedia.org\/wiki\/Characterization_test<\/a><\/li>
- https:\/\/approvaltests.com\/<\/a><\/li>
- https:\/\/youtu.be\/zyM2Ep28ED8<\/a><\/li><\/ul>\n","protected":false},"excerpt":{"rendered":"
A nice way to help you refactor legacy code is to use “Characterization Testing” or “Golden Master testing”. These approach provide a quick way to get cover legacy code with _some_ tests. There is a big catch though: Unlike regression … Continue reading