Timeline for What benefit does having developer experience or background have on the effectiveness of a tester?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 23, 2011 at 8:45 | comment | added | Sub S | Interface need not be the HCI alone. Testers usually write code at all interface levels - interfaces between classes etc. This is where whitebox testing comes into picture. In your case, this should solve the problem - again, as long the SRP and interfaces are clear. | |
| May 19, 2011 at 14:10 | comment | added | TristaanOgre | The interface does not necessarily indicate what the code path is. I have a project I'm currently working on where that is the case. There's a fairly complex decision tree made to determine who gets e-mail notifications of certain events. However, the interface is simply a data entry screen. Now, there are detailed specifications, but there are some complexities in the decisions that a specification is VERY verbose on but can be easily summed up by looking at the code. | |
| May 17, 2011 at 22:48 | comment | added | Sub S | Ideally all these information should be arrived at from the interface, not by looking at the implementation. And the other pair of eyes are your other developers in the team :). In fact, the other developers will have a better understanding of interactions with other related components internal workings as well - so this will help them give better comments. | |
| May 17, 2011 at 18:09 | comment | added | TristaanOgre | Additionally, as @Ethel points out below, the ability to help out with static white-box testing (code review) is VERY helpful to give that other pair of eyes to things | |
| May 17, 2011 at 16:48 | comment | added | TristaanOgre | While I agree on the contamination point, I think it is helpful for a tester to know at least some of the logic that's in the code that s/he is testing in order to be able to build boundary cases and the like. Additionally, while the tester doesn't need to read the actual code to do this, having some knowledge of what happens when you don't initialize a variable, what happens when you loop on n-1 records on an array based upon 1 instead of based upon 0, etc., is helpful in, again, knowing what kinds of tests to run and how to communicate results to the developers. | |
| May 17, 2011 at 16:29 | history | answered | Sub S | CC BY-SA 3.0 |