Skip to main content
10 events
when toggle format what by license comment
S Dec 27, 2022 at 20:21 history suggested Rob Gilton CC BY-SA 4.0
Replace dead link with archive.org link
Dec 16, 2022 at 9:28 review Suggested edits
S Dec 27, 2022 at 20:21
Jan 16, 2014 at 9:51 comment added Julia Hayward I think you could substitute "algorithms" - and other terms - for "architecture" and the argument still holds; it's all about being unable to see the wood for the trees. Unless you are going to write a separate test for every single integer input, TDD will not be able to distinguish between a proper factorial implementation and some perverse hard-coding which works for all tested cases but not others. The problem with TDD is the ease with which "all tests pass" and "the code is good" are conflated. At some point a heavy measure of common sense needs to be applied.
Nov 26, 2010 at 9:11 comment added CraigTP I agree with @rmx. This doesn't really answer my specific question, per se, but it does give rise to food for thought as to how TDD in general fits into the big picture of the overall software development process. So, for that reason, +1.
Nov 25, 2010 at 23:21 comment added Joppe The ideal solution is an algorithm and has nothing to do with architecture. Doing TDD won't make you invent algorithms. At some point you need to make steps in terms of an algorithm/solution.
Nov 25, 2010 at 16:33 comment added Robert Harvey @rmx: Um, the question is: How do you get that balance between "writing the minimum code to pass the test" whilst still keeping it functional and in the spirit of what you're actually trying to achieve? Are we reading the same question?
Nov 25, 2010 at 16:32 history edited Robert Harvey CC BY-SA 2.5
deleted 2 characters in body; deleted 1 characters in body
Nov 25, 2010 at 16:29 comment added Nobody Not really an answer to the question, but 1+
Nov 25, 2010 at 16:25 history edited Robert Harvey CC BY-SA 2.5
Nov 25, 2010 at 16:15 history answered Robert Harvey CC BY-SA 2.5