You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
- I seems you do not mention any particular advantage of TDD over full testing? This is basically what I think for the moment. Of course the degree of coverage deserves attention. It seems if I add tests only to all classes I modify and on classes that depend on them, I should catch most bugs. So I would conclude selective testing hasn't been disproven (as compared to close to full testing which is essential in TDD)?Gere– Gere2012-08-02 15:16:40 +00:00Commented Aug 2, 2012 at 15:16
- There is no such a thing as "full testing". Testing can never demonstrate that your code is bug-free.CesarGon– CesarGon2012-08-13 17:50:42 +00:00Commented Aug 13, 2012 at 17:50
- @CesarGon: Nowhere in this post I claimed that (nobody ever claims that, this is prime example of straw man argument). Heck, I even explicitly stated OP should not follow "delusive magical-fairy-tale 100%" coverage.k.m– k.m2012-08-13 19:37:48 +00:00Commented Aug 13, 2012 at 19:37
- @jimmy_keen: Then I must have misunderstood; sorry. In that case, what do you mean by "full testing"? How can you achieve such a thing?CesarGon– CesarGon2012-08-14 19:59:10 +00:00Commented Aug 14, 2012 at 19:59
- @CesarGon: OP mentioned sporadic testing which, as I understand, is writing unit test when you feel it matters. Instead, one could start with TDD and decide when not to write unit test. After all, it's much easier to determine that "this code has small chances of breaking, so I skip test" (because you wrote similar code many times) rather than "this code will break, so I write test" (it's essentially the same story as is it a bug when you know about it upfront issue I mentioned). That's what I meant by full testing; do selection, but not when to write, but rather when not to write.k.m– k.m2012-08-17 12:11:32 +00:00Commented Aug 17, 2012 at 12:11
| Show 1 more comment
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you