Journey to TDD - Untested Environment

If you found this article and want to start at the beginning, this series starts here.

I talked about a legacy system is a system that does not have any tests, even if you wrote it!

There are good reasons to not have tests in a system, one thing you must have is know how to create tests. You must go through the pain of creating a system tests, especially test first.

The way you code after test driven, even without tests is different than just “coding first”. You will setup functions that is easier to test later when the project takes off and adding more features.

You must be vigilant about testing in an untested environment. Untested code is a slippery slope because external factors will make you continue “fast” without tests - because it’s working, why not do more?

I learned this vigilance when I inherited a code base