After going through this process four times now, I found that any introduction of TDD would not be completed without any control. Programmers do not want to switch the style and will not write their first unit test and suddenly they see the light.
You can apply at the management level, but it takes a lot of time for all participants. Some level of this is necessary in any case, but ultimately you will need automatic enforcement. The answer to this question is the introduction of continuous integration.
I have found that the CI server is the main cornerstone for any TDD environment. If the developers do not know that something bad will happen if they do not write tests, you will always have cowboys who feel this under them.
source
share