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*
- Ah I totally forgot that quote! Guess I will use it as my main argument because frankly - what can break here? Not really much. Only thing that can break is the method invocation and if that happens than it means something really bad happened. Thanks!Zenzen– Zenzen2012-01-19 21:35:22 +00:00Commented Jan 19, 2012 at 21:35
- 7@Zenzen: "what can break here? Not really much." - So it can break. Just a small typo. Or somebody adds some code. Or messes up the dependency. I really think that Beck would claim that your main example qualifies as breakable. Getters and setters, less so, although I have caught myself out in a copy/paste error, even then. The real question is, if it's too trivial to write a test, why does it even exist?pdr– pdr2012-01-19 21:44:22 +00:00Commented Jan 19, 2012 at 21:44
- 1The amount of time you spent thinking about it already you could have written the test. i say write the test, don't leave when not to write a test as a grey area, more broken windows will appear.kett_chup– kett_chup2012-01-20 00:11:24 +00:00Commented Jan 20, 2012 at 0:11
- 1I'll add that my general experience is that testing getters and setters is somewhat valuable in the long-term, but low-priority. The reason why is because why it has "zero" chance of finding a bug now, you can't guarantee that another developer won't add something in three months ("just a simple if statement") that will have a chance of breaking. Having a unit test in place guards against that. At the same time, it isn't really overly high priority, because you aren't going to find anything soon that way.dclements– dclements2012-01-20 04:00:47 +00:00Commented Jan 20, 2012 at 4:00
- 8Blindly testing everything that could break doesn't make sense. There needs to be a strategy where high risk components get tested first.CodeART– CodeART2014-03-27 23:50:15 +00:00Commented Mar 27, 2014 at 23:50
| Show 2 more comments
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