Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • Previously I had added tests before the code so aware how important that habit is... @Robbie I agree whole heartedly with your answer, and thank you very much for the advice. Commented Feb 3, 2016 at 15:27
  • 2
    You are intermixing the terms "TDD" and "Unit tests", just as the OP. Commented Feb 3, 2016 at 17:01
  • @DocBrown To be clear - retro-fitting unit tests isn't TDD, but it does deliver value if done correctly. As outlined in Philipp's answer, it is by no means straight forward. Commented Feb 3, 2016 at 17:07
  • 1
    Did I wrote something different? I am just saying you are using the terms wrong, just as the OP. Someone should tell the OP he is not adding "TDD tests" to the project, that makes no sense. Commented Feb 3, 2016 at 17:19
  • @DocBrown Fair enough - I've tidied my answer a little. Commented Feb 3, 2016 at 17:39