In test development, do you write all possible tests first, then code?

Question

During the test-based development process, I got used to writing the first unit test for the new part of the functionality first, and then writing the code for this function. If I have additional tests for writing to cover all the scripts, I usually write them after writing the code. Is this considered a bad form? Should I first try to write all conceivable tests for a piece of functionality before writing this code?

Answer 1

To correctly execute TDD, you always write the test first, and then the second functionality.

, , 20 , 20 . , / , . , TDD, , /.

Answer 2

, " ". "":

, . Interfaces. :

• A (API )
• Unit Test xyz,
• (//)
• 2 + 3 .

, . , . , , , , .

. , , , ( , ). powererd Mercurial MQ.

Answer 3

TDD / . :

• ,
• .

, , .

Answer 4

, . , , , . , " ". , , , , .

, -, , .

Answer 5

, , , . , . , , . , , .

, , , , , ... , , .

, , , , , "TDD Video"

http://agilesoftwaredevelopment.com/videos/test-driven-development-basic-tutorial (oops, , )

Answer 6

- . , , . , , , .

, , - , , . , , . , , .

Answer 7

, TDD. (, , ) , , , , , re test-driving. .

TDD . , , - . , , . , .

TDD . , , , . - , , , : ", ", , , , , , .

red-green-refactor: , ( "", , ), , ( "" ), , , ( "" ). , , , . , / .

, , , . , , , , .

, , : . () .

Answer 8

TDD , , , . .

Answer 9

TDD, . - . ( ), , , , , , ( , ), . , .

Answer 10

1 .. , . , , , .

If you need to write a lot of tests for one unit of code (method, function, etc.), this may be a sign that you are trying to do too much on this device ... which, in turn, makes the dificult block for testing and refactoring at a later time.