My Experience with Test-Driven Development (TDD)

Anyone who has worked on an I.T. project will know this familiar scenario: a project with a tight timeline has a bug that needs fixing before deployment. Once the code has been written, manual testing is performed before the code review is done, and the code is merged to the source control. You then run the risk that more bugs and issues may have been introduced from the code merge; meaning that you’ll either need to write more tasks to resolve this issue or the new code changes will need to be reverted in source control.

A lot of things could lead to problematic code. The following are a few main reasons for this:

• Lack of test cases written for the application
• The tests were written after writing the functional code
• Failing to regression test

So how might be avoid this scenario? I suggest using Test-Driven Development (TDD).

What is TDD

TDD is an approach to development that emphasizes testing code before the code is written.

In the first step, the developer writes the test. Then, the test is run to see if it…