tag:blogger.com,1999:blog-5596188161458654024.post7428378644909868340..comments2023-10-26T11:22:35.241+02:00Comments on Testing FTW!: Get to know your defectsNicolai Nielsenhttp://www.blogger.com/profile/04201200897127337869noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-5596188161458654024.post-18192158615389688732013-09-19T11:23:57.325+02:002013-09-19T11:23:57.325+02:00Hi Srinvas - Thanks for your comment!
Root cause ...Hi Srinvas - Thanks for your comment!<br /><br />Root cause analysis is often neglected in projects – Either because there is no time, or because the truth hurts. <br />Asking the question “What is really the problem?” requires analysis and time. On top of this, it requires a controlled environment where you can actually trace the problem back to its origin. Going back to the origin of the problem is not necessary the root of the problem and that is where you have to ask the question “What is the problem, really?”<br /><br />I have an example from a project I was involved in many years ago. Using the questions listed by Mikkel the rootcause analysis would have looked like this:<br /><br />What is the problem? Too many defects are rejected by developers as not reproducible!<br />What is really the problem? Developers have a hard time understanding the scenarios described in the bug reports, and it shows that the problems can be reproduced by the person who raised the defect.<br />What is the problem, really? Business personnel involved in the test don’t have a clue on how to write a good and accurate defect report.<br /><br />Problem was fixed by a Defects for Dummies manual, and me reviewing the defects for a period while the Business reps got the hang of writing repro steps without getting lost in business lingo or one-liners.<br /><br />However the answer to What is the problem, really? Could easily have been something else – What if there was a significant difference in the DEV and TEST environment? What if the developers needed to have a crash course in reading requirements? What if the test was running on poor data? <br /><br />Answering that last question accurately is in my opinion what makes money and optimizes productivity – Stopping the same error to happen over and over again.<br /><br />And one last thing: Be careful how you bring your points about root causes across, there are a lot of sore feet and toes to step on in the process.<br /><br />Happy testing!<br /><br />/Nicolai<br />Nicolai Nielsenhttps://www.blogger.com/profile/04201200897127337869noreply@blogger.comtag:blogger.com,1999:blog-5596188161458654024.post-35485608518694631602013-09-16T14:10:20.791+02:002013-09-16T14:10:20.791+02:00Thanks for sharing..
Feedback: Can u please incre...Thanks for sharing..<br /><br />Feedback: Can u please increase font size.<br /><br />Question: I think this statements can be clear?<br />What is really the problem? (What is the real problem) <br /><br />What is the problem, really? (Was it a problem, really)<br /><br />Regards,<br />Srinivas Kadiyala<br />@srinivasskcSrinivas Kadiyalahttps://www.blogger.com/profile/04702798081842391077noreply@blogger.com