Edit - Software Engineering Stack Exchange

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.

Even with 100% code coverage you can still encounter non-obvious code paths that aren't tested, such as overflow conditions.

whatsisname
– whatsisname

2016-11-28 22:49:23 +00:00
Commented Nov 28, 2016 at 22:49
3

This sentence says it all: It is all about what is the expected behavior of your class from the perspective of the rest of the system. Unit testing and TDD made more sense to me when I stopped thinking about testing methods and instead tested behaviors.

Brandon
– Brandon

2016-11-28 22:55:18 +00:00
Commented Nov 28, 2016 at 22:55

Add a comment |

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

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>

formatting help »
answering help »