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

Thanks for the response. I do write unit tests (although haven't yet progressed to TDD), and have on occasion broken up large classes for the sole purpose of making it easier to test the private methods (which are now public in the new classes). I suspect this probably isn't the "right" approach to take with unit testing though.

Andrew Stephens
– Andrew Stephens

2013-06-20 10:56:24 +00:00
Commented Jun 20, 2013 at 10:56
It's hard making the leap to TDD but with regards to getting into writing unit tests I'll make a huge assumption that you're doing what a lot of people do. Also if you are working with existing code the approach you are taking seems the most pragmatic.

Daniel Hollinrake
– Daniel Hollinrake

2013-06-20 11:09:37 +00:00
Commented Jun 20, 2013 at 11:09

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 »