TDD is just about writing the test before the program. In other words, first think about “how to use” any component, why do we need this component or what’s it for? And only then think “how to implement”. Hence we can say, it’s a testing techniques as well as design techniques. Below are the advantages of it, It results into components that are easy to test. It results into components that are easy to enhance and adapt. In the end, there is no code without a test. We can tell at any time, whether everything still works as it should, or what exactly does no longer work as it once did. Complex things won’t fear us, execute the test and get positive feedback. You can re-use the unit test in accessing the performance of your system early stage of software lifecycles. Why test first? The test is the executable specification…. Read more“Test Driven Development”