tag:blogger.com,1999:blog-3806208351698608392.post6788189632194086298..comments2023-10-28T16:37:34.195+05:30Comments on Software Testing Space: Interviews of Thought Leaders - Alan PageInder P Singhhttp://www.blogger.com/profile/05923580987480854491noreply@blogger.comBlogger8125tag:blogger.com,1999:blog-3806208351698608392.post-75194821587998321562010-08-11T09:35:09.634+05:302010-08-11T09:35:09.634+05:30Such insights help a lot.
Regards,
Manas( http://c...Such insights help a lot.<br />Regards,<br />Manas( http://crazysidunplugged.blogspot.com/ )Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3806208351698608392.post-91666423754829890402010-04-30T15:43:38.055+05:302010-04-30T15:43:38.055+05:30Fantastic insights.Fantastic insights.Srideepnoreply@blogger.comtag:blogger.com,1999:blog-3806208351698608392.post-65637799913911868992010-04-28T16:00:12.134+05:302010-04-28T16:00:12.134+05:30The discussion is informative as a whole. Two thin...The discussion is informative as a whole. Two things took my attentiom most are;<br />1.Business Intelligence Role<br />2.Passion for LearningPrashantnoreply@blogger.comtag:blogger.com,1999:blog-3806208351698608392.post-78786699723073517082010-04-28T14:15:16.088+05:302010-04-28T14:15:16.088+05:30Very well put by Alan! I especially like the two s...Very well put by Alan! I especially like the two suggestions for testers:<br />1. Code reviews<br />2. End to end scenarios<br /><br />Would love to learn more of Alan's thoughts on his upcoming blog posts on these topics.<br /><br />And yes, the testers add value by discovering product issues and identifying risks. We are able to do this because we consider the product from different perspectives (including the perspective of the customer/ end-user).Inder P Singhhttps://www.blogger.com/profile/05923580987480854491noreply@blogger.comtag:blogger.com,1999:blog-3806208351698608392.post-29936197803038472442010-04-27T22:06:49.507+05:302010-04-27T22:06:49.507+05:302. Whats the value add that testers bring to the o...<b><i>2. Whats the value add that testers bring to the organization ? Finding bugs /testing functionality etc is part of job responsibility, can we call this as value add? </i></b><br /><br />I hate the role of testing as "verifying functionality" - I prefer software to at least function when I start testing it - that way I can look for more interesting issues. As for bugs, I don't see bug finding as part of the role either - they are just a side effect of what we do.<br /><br />Our value add is to uncover product issues and risk. We do that by analyzing, questioning and exercising the product with a critical eye. Testers uncover issues and unearth information about the product that would not be found otherwise - at least by anyone other than customers. As a tester, rather than discover issues that make the developer say "oops" I love to discover things that make the developer say "that's incredible - how in the world did you discover that?" I find that a portfolio of these "discoveries" provides plenty of value-add for the stakeholders.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3806208351698608392.post-74623839172940170092010-04-27T21:11:24.920+05:302010-04-27T21:11:24.920+05:301. Um...it depends - but I'll explain why. Eve...1. Um...it depends - but I'll explain why. Every team and product is different, so the things that testers do not test for can vary from team to team. I advise teams to look at the types of issues they are finding late stages and spend a bit of time brainstorming about types of testing (or quality improvements) that could have found the problem earlier. <br /><br />This is a just lightweight form of root cause analysis (rca), but can be pretty effective. Note, that there may be multiple methods for finding a bug earlier, and that's ok. Nobody ever said there had to be one, and only one, root cause.<br /><br />That said, I do see some things always come up. I know that many testers don't have an opportunity to see the source code for the apps they test, but one are where testers can help is with code reviews. Code reviews are very effective in finding bugs early. Programmers, of course, usually perform code reviews, but they don't often ask the right questions. By that I mean they review code to see if it will work as written. Testers ask better questions - like "in what situations could this condition fail", or "how would we test for this code path". <br /><br />Another approach that I like is to create full end-to-end scenarios covering a broad part of the application as early as possible. Do it before the application is available if possible, otherwise just do it early. Then run your scenarios. Early on, most, if not all, will probably fail - but that's ok. Keep doing whatever other testing you're doing "most of the time", but run the scenarios every week or so (timing depends on product size) and report results. Over time, these scenarios will move from "red" to "green". Also encourage testers to vary their approach and explore the scenario - have them pair up or trade off to remove any facets of fatigue.<br />I've observed that many issues discovered late are <i>integration</i> issues - flaws where all of the moving pieces fit together. By focusing on end-to-end scenarios early, these integration issues are often discovered much earlier.<br /><br />(I have <a href="http://angryweasel.com/blog" rel="nofollow"> blog entries</a> going up soon on both of these topics if you'd like to know more).<br /><br /><i>AND - I'll answer the value-add question in a new comment </i>.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3806208351698608392.post-75647344377314121492010-04-27T19:40:34.391+05:302010-04-27T19:40:34.391+05:30Here are a couple of questions from another reader...Here are a couple of questions from another reader. I wonder about Alan's response to these.<br /><br />1. What is that we software testers do not test for in the SDLC life cycle and that has major impact on later stages?<br /><br />2. Whats the value add that testers bring to the organization ? Finding bugs /testing functionality etc is part of job responsibility, can we call this as value add?Inder P Singhhttps://www.blogger.com/profile/05923580987480854491noreply@blogger.comtag:blogger.com,1999:blog-3806208351698608392.post-23638510286515317222010-04-26T18:02:24.629+05:302010-04-26T18:02:24.629+05:30Interview was brief concentrating on how Alan'...Interview was brief concentrating on how Alan's test career had developed, high level view about testing,its future but its very brief , i guess because of time constraints.Suprinder Pujjinoreply@blogger.com