Do you think before watch your TDD video series I should code as a ninja? I mean how to test code that is not constructed under the red-green-refactor cycle?
"London" style TDD is a fake TDD created by the programers that never understood the TDD and all of its benefits. Yes there is the bottom up trap in the classic (real) TDD but it is easy to avoid it by starting at the top near the user interface and then you can go down by refactoring or by "finding" the lower level objects. You can also use mock object in the classic TDD if you have a good reason for that.
Great introduction. As for the SICP reference, I think your were alluding to what Abelson and Sussman refer to as “wishful thinking.”
Do you think before watch your TDD video series I should code as a ninja? I mean how to test code that is not constructed under the red-green-refactor cycle?
great video, thank you!
Glad you liked it!
"London" style TDD is a fake TDD created by the programers that never understood the TDD and all of its benefits. Yes there is the bottom up trap in the classic (real) TDD but it is easy to avoid it by starting at the top near the user interface and then you can go down by refactoring or by "finding" the lower level objects. You can also use mock object in the classic TDD if you have a good reason for that.
Someone didn't really bother watching through the video :)