Timeline for Why to let / not let developers test their own work
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 25, 2012 at 14:47 | history | edited | John Shaft | CC BY-SA 3.0 |
Made most important point in bold text
|
| May 23, 2011 at 7:00 | history | edited | John Shaft | CC BY-SA 3.0 |
Extended my response to better answer the question
|
| May 18, 2011 at 14:53 | history | made wiki | Post Made Community Wiki by tschaible | ||
| May 18, 2011 at 13:55 | comment | added | David Thornley | In one place I worked, I was supposed to not only implement new features but write up test plans. This meant that, if I misunderstood something, it would be implemented incorrectly but wouldn't be caught by the testing department. | |
| May 18, 2011 at 12:26 | comment | added | StuperUser | @Jörg W Mittag not really. Just as not every tester will think of every test case, neither will every developer. Hence pair programming etc. and separate QA teams. Two heads are always better than one. | |
| May 18, 2011 at 12:24 | comment | added | AProgrammer | Developpers also test with the same prejudices than guided their work. Testers are less likely to share them. | |
| May 18, 2011 at 10:45 | comment | added | Jörg W Mittag | This can easily be circumvented by writing the tests before the code, though. | |
| May 18, 2011 at 10:25 | comment | added | LennyProgrammers | In advertisement for the same reason a different people proof-reads the final product than the one who created it. | |
| May 18, 2011 at 8:51 | comment | added | StuperUser | @dnolan, it's not only "protecting" their code, it's also that anything they've not thought of in coding, they won't think of for testing. | |
| May 18, 2011 at 8:47 | comment | added | pyvi | Totally agreed. However, in this case there are also step-by-step test plans (developed by several people), so I am not sure it completely applies. Even with the test plan, I still feel like the developer testing his/her own work is something to be avoided. | |
| May 18, 2011 at 8:45 | comment | added | dnolan | Agreed, a developer will take the path of least resistance to "test" their application, edge cases will rarely be looked at. | |
| May 18, 2011 at 8:44 | history | answered | John Shaft | CC BY-SA 3.0 |