Re:Cognition versus Programming: The Big Two – Why TDD?
by lmm on Friday March 18, 2022 @06:14AM
(#30720352)
Then what do you call it where you write programs bottom-up but still write test cases before implementation? Because that's the most common approach that I've seen being done and called TDD.
Re:Cognition versus Programming: The Big Two – Why TDD?
by thibauts on Friday March 18, 2022 @07:33PM
(#30729012)
I call it wasting time trying to fit square pegs in round holes. Many things and approaches have their virtues and their place, be it top-down, bottom-up or tests. Silver bullet techniques and dogma have absolutely none.
Re:Cognition versus Programming: The Big Two – Why TDD?
by lmm on Saturday March 19, 2022 @03:44AM
(#30731980)
Not my experience, shrug.
Re:Cognition versus Programming: The Big Two – Why TDD?
by janto on Friday March 18, 2022 @07:44AM
(#30720928)
That's when you adopt other XP practices in addition to TDD.
« Test-driven development (TDD) is a software development process relying on software requirements being converted to test cases before software is fully developed, and tracking all software development by repeatedly testing the software against all test cases. This is as opposed to software being developed first and test cases created later. » [1]
[1] https://en.m.wikipedia.org/wiki/Test-driven_development