Does Software Development Speed Slow When Using Test-Driven Development (TDD) ?
Test driven development, or TDD, is a software development approach where you write tests first, then write code that makes the tests pass. This will ensure your tests are also tested, not just your code is tested. This is because you write test first (it fails as expected), and then you write just enough code to pass the test.
Yes, TDD slows software development speed in the beginning for both newbies and experienced developers. Newbies have to learn to do it fresh and Experienced have to unlearn old habits and learn to use it. But it is still used because as long term investment as it helps in writing and maintaining a higher software quality. The time and effort spent time now will payoff in the future once the software product grows in size, and complexity.
When you write tests first, you have already begun the process of making your code testable. This means that as you write the tests, you are also giving yourself a better chance of making the code work the first time. By definition, tests are there to serve as a contract with the code you are writing. Your tests should outline exactly how the code will behave, and when you write the tests first, you are closer to achieving that goal. Writing tests first also means you are creating value for yourself and your team rather than just handing over a code block.
TDD Benefits:
- Better designed and more stable software.
- Faster development cycles.
- Greater cohesion and less coupling between components.
- Clarity of purpose.
- Helps with domain driven design.
- Greater maintainability.
- Sharps your understanding of the business domain.
- Reduces the possibility of errors.
- Increases confidence in delivering value.
- Identifies and corrects bad code patterns earlier on.
- Higher quality software.
- More robust systems.
- Flexibility to evolve with the business.
