Test driver development trap nine, requires artificial intervention test eight, complex test configuration environment seven, take the whole body test code six, test 5 for code rather than function, huge Testcase four, red light Testing of Ming Third, Large Span, Test of Wear
I am very lucky. Basically, the mistakes mentioned earlier have been committed, and they will have a different mistakes will be made later. However, I feel that these mistakes are not as big as the biggest mistake:
First, there are many reasons for non-writing tests to refuse TDD: progress is too tight, how to write test; this way is too quirky, unacceptable; what you do is too special, not suitable for testing driving development; Some of the code can't write test at all ...
This fact is accepted "People will make mistakes" (whether in writing procedures, or when applying new development processes), and face these errors, they are found, they define them, check and clear feedback results. In the end, maybe you will find that the initial fear has been disappeared with a step in the smoke, and your steps have already expanded to the field that has not been involved.
