Timeline for Why to let / not let developers test their own work
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 5, 2013 at 16:44 | comment | added | user7433 | One extra note here; while testing is important, code reviews help greatly in catching bugs and ensure the right unit tests are written. Developers may test for different bugs with their unit-tests making it extremely important to have more than one person testing the software. | |
| May 19, 2011 at 10:53 | vote | accept | pyvi | ||
| May 18, 2011 at 17:50 | comment | added | Wipqozn | +1 for "Developers normally work with the developer mindset of "how to make this work?". A good tester is thinking about "how to break this?"" | |
| May 18, 2011 at 16:21 | comment | added | Mateen Ulhaq | Black hat testers...? | |
| May 18, 2011 at 14:53 | history | edited | Péter Török | CC BY-SA 3.0 |
added 3 characters in body
|
| May 18, 2011 at 14:53 | history | made wiki | Post Made Community Wiki by tschaible | ||
| May 18, 2011 at 12:35 | comment | added | PeterAllenWebb | I agree. After hours, days, or even weeks of trying to "make this work" under a deadline, it can be VERY hard (maybe even impossible) to break that mindset. It might be possible to test objectively if you had time to set aside your work and come back to it after a hiatus, but that is rarely feasible. | |
| May 18, 2011 at 9:08 | history | answered | Péter Török | CC BY-SA 3.0 |