Comments on: Day 5: Write a Unit Test Before Coding

By: Mangola

Mangola — Sun, 12 Jul 2009 08:11:58 +0000

Thanks for the interesting information.

By: Bharat Kondeti

Bharat Kondeti — Sun, 07 Jun 2009 00:31:38 +0000

This is where many people miss the point. Tests are not written for Test Coverage, Tests are written to test the actual functionality of the code. This can only be achieved by writing tests first.
Writing tests first will make you write only necessary code.
Writing tests first and giving proper names will help you write less/no comments in the code. Just by reading test case names you should be able to understand functionality of the code.
Writing code is different from writing testable code. Its a different mind set and writing tests first will help you to write testable code.
Writing tests first will help you to refactor code with confidence.
Just remember the mantra ‘Red Green Refactor, Red Green Refactor………’

By: Alex

Alex — Thu, 04 Jun 2009 23:17:12 +0000

I still think it is necessary to write tests, at the same time as coding. One of the aims of unit tests is code coverage, particularly decision coverage. You can’t really achieve this if unit tests are written prior to coding.

By: Ondra "Satai" Nekola

Ondra "Satai" Nekola — Thu, 04 Jun 2009 20:56:57 +0000

…and write your tests after coding. When you discover a bug, write a test scenario, that fails for such a situation. When the bug is fixed, you are safe from regression.