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.

thank you i have similar scenario and was finding difficult to write test cases for it.

Bhalchandra K
– Bhalchandra K

2018-08-05 08:34:27 +00:00
Commented Aug 5, 2018 at 8:34
I like this perspective. What you test is your code and your expectations. What I'd add is this is also where you test the design of your own abstractions, interfaces, names, and API because tests let you see them being used. Make sure they make sense even when you don't look inside.

candied_orange
– candied_orange

2018-08-05 15:05:02 +00:00
Commented Aug 5, 2018 at 15:05

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 »