Timeline for How does a tester's perspective towards software differ from a developer's?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 9, 2011 at 20:27 | vote | accept | CommunityBot | moved from User.Id=246 by developer User.Id=53100 | |
| May 13, 2011 at 13:15 | comment | added | user246 | I think so too. The best testers I've worked understand a product for what it really is: a bunch of algorithms that, when used in a certain way, could potentially be used for a certain purpose. They're able to let its intended purpose fall away so that its other potential uses are exposed. Each algorithm is just a bunch of inputs and outputs. We assign meanings to those inputs and outputs, but those meanings only make sense in the context of their intended purpose. Allowing other meanings leads to creativity and, of course, to finding bugs. | |
| May 13, 2011 at 2:05 | comment | added | TristaanOgre | Let me add that I think an EXCELLENT developer has some of that tester in them because it is in finding out those strange and weird interactions that come from analysis is how they find out new wonderful and amazing things to build. Likewise EXCELLENT testers need a good sense of synthesis to be able to know how to put the things together to create those new wonderful things so that they can better understand how they come apart again. | |
| May 13, 2011 at 1:59 | history | answered | TristaanOgre | CC BY-SA 3.0 |