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.

Required fields*

Rev

6

+1 for the practical advice in the final paragraph. If multiple asserts lead to more programmer joy and better coverage, multiple asserts are better.

user949300
– user949300

2019-07-11 17:26:28 +00:00
Commented Jul 11, 2019 at 17:26
That's not what "following the rules" means. The people who get that wrong are the same people who follow SOLID and wind up with 500 classes.

Robert Harvey
– Robert Harvey

2019-07-12 17:47:24 +00:00
Commented Jul 12, 2019 at 17:47

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 »