TDD : Test Driven Development

 Red -->Green --->Refactor

 Write the tests first.fail the test cases. This is what the main philosophy of TDD This paradigm can also be used in debugging legacy code.In this Blog we are going to talk about TDD methodology.

 Following are the steps for following TDD:

• Add a test
• Run all tests and see if the new one fails
• Write some code
• Run the automated tests and see them succeed
• Refactor code
• Repeat
• Keep the unit small.
• If require we can mock objects for eg sum third party services, DB we may use a mocking framework like EasyMock,Jmockit, Mockito.

What are the benefits of TDD?

• Test Coverage.
• Test Repeatability.
• Documentation
• API Design
• System Design
• Reduced Debugging.
• Your code worked a minute ago

Now the question is what are the costs of TDD?

•  Programming in tiny cycles can seem inefficient
•  A lot of test code is produced
•  A lot of time is spent keeping the tests in sync with the production code

 Some time people says  'SPECIFY FIRST' which means the specify the desired behavior in testms of test case.In the next blog TDD:Most Suitable Scenarios we will see some practical example where TDD suits best.