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

10

Strongly and vehemently disagree... Developers can be highly effective testers but the developer of a feature should NOT also be the tester of the same feature. Many small teams play both roles, by three people working on three different features, then handing off testing to one of the other three developers. It works extremely well when a team does not have a QA tester.

maple_shaft
– maple_shaft ♦

2011-08-20 12:11:18 +00:00
Commented Aug 20, 2011 at 12:11
6

@maple_shaft: Imho there's no excuse for not having a tester. Any project will deliver higher quality with a dedicated tester and developers can focus on, well developing if there's one. Having developers test each others code is a makeshift solution, even for small teams imho. You should read Joel's article on it, too.

Falcon
– Falcon

2011-08-20 12:30:22 +00:00
Commented Aug 20, 2011 at 12:30
4

Developers can be testers - and a good developer actually knows many places where code can be weak and subject to breakage. Just never have people test the code they designed or wrote - that's useless. Other people's code may be ok.

StasM
– StasM

2011-08-21 00:05:38 +00:00
Commented Aug 21, 2011 at 0:05
2

@StasM: I agree that developers can be testers, even good ones. But they shouldn't be testers.

Falcon
– Falcon

2011-08-21 07:55:42 +00:00
Commented Aug 21, 2011 at 7:55
2

@Bryan Oakley: But that's not Q&A testing then.

Falcon
– Falcon

2011-08-21 15:43:27 +00:00
Commented Aug 21, 2011 at 15:43

| Show 4 more comments

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 »