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.

1

I don't see where you come up with use cases in your approach.

user188153
– user188153

2017-01-06 17:58:19 +00:00
Commented Jan 6, 2017 at 17:58
As a single developer, I usually wouldn't (except maybe in my head). When working within a team, I would usually expect this to occur as the developer and test team are working to clarify the details of the story and what could possibly be happening from start to finish.

Jay S
– Jay S

2017-01-06 21:50:48 +00:00
Commented Jan 6, 2017 at 21:50

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 »