I don’t agree with the unit test suggestion. I would rather suggest using TDD instead, which is based on unit tests of course.
While it may be true that unit tests change often, especially in the important parts of the system, I’ve never face situations where this was a problem. On the reverse, working in TDD they become the first feedback of doing things right.
So I would definitely define the ROI of unit tests as HIGH. 🙂
I don’t agree with the unit test suggestion. I would rather suggest using TDD instead, which is based on unit tests of course.
While it may be true that unit tests change often, especially in the important parts of the system, I’ve never face situations where this was a problem. On the reverse, working in TDD they become the first feedback of doing things right.
So I would definitely define the ROI of unit tests as HIGH. 🙂