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.

Changing the scope just for testing is vile, public or not.

Telastyn
– Telastyn

2014-10-19 16:39:34 +00:00
Commented Oct 19, 2014 at 16:39
1

No, unit tests in their pure form are supposed to determine whether a given unit viewed in isolation conforms to its specification. As private helpers can never be part of an API specification, there is no use in unit testing them, or mocking private helpers in a different unit's test. However, I take the position that it can still be useful to test private helpers to determine whether they conform to this unit's programmer's expectations, and because fine-grained tests make it easier to localize errors.

amon
– amon

2014-10-19 20:36:46 +00:00
Commented Oct 19, 2014 at 20:36

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 »