4 ms·
TDD slide has an error it seems. In slide 18 Fucci2016 is referred for a replication study with 39 professionals. That study only uses students. That slide quo
by infocollector 5y ago
TDD slide has an error it seems.
In slide 18 Fucci2016 is referred for a replication study with 39 professionals. That study only uses students. That slide quotes Fucci2016, but I do not see that quote in the paper. He talks about TDD and hatemail and is not careful about references? Perhaps this was just a small error - the reference is incorrect. I am not sure.
It seems believable that Test-first vs Test-last might have similar impacts. I just checked one thing in this talk and it turned out to problematic. Has anyone else done fact-checking on his stories?
- Erikun 5y agoIt seems he took the title of a different Fucci 2016 paper, it should say "A Dissection of the Test-Driven Development Process: Does It Really Matter to Test-First or to Test-Last?" This paper contains both the quote and is done on 39 professionals. This seems like an easy mistake to make and not something I feel has an impact on the trustworthiness of his talk
- infocollector 5y agoThanks! Seems like short cycles of development including interleaving testing - is the key in this paper. TDD might just achieve this by a fluke, but it should help that - unless you do this TLD or even test addition in cycles. Any thoughts on that?
- preommr 5y ago> TDD might just achieve this by a fluke I am confused by this comment and the overall sentiment in the video. Short dev cycles isn't an accidental byproduct - it's literally one of the key parts of tdd. The first google result for tdd has this: > Test-driven development (TDD) is a software development process that relies on the repetition of a very short development cycle: first the developer writes an (initially failing) automated test case that defines a desired improvement or new function, then produces the minimum amount of code to pass that test, and finally refactors the new code to acceptable standards.