tag:blogger.com,1999:blog-326963428284433428.post812420270128385144..comments2023-05-23T05:34:52.986-07:00Comments on Journey begins...: Philosophy of testingKashif Ali Habibhttp://www.blogger.com/profile/14963125844474587107noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-326963428284433428.post-84348299244485544862009-08-18T06:14:59.103-07:002009-08-18T06:14:59.103-07:00If the software has features that were not part of...If the software has features that were not part of requirements the tester should be asking why the heck they are there. To some degree they're as bad as bugs in that they may not add value to the customer and may detract from developing what is of value.<br /><br />Kashif, have a look for the book called 'Did you spot the gorilla' where Dr Wiseman talks about change blindness. There's a video related to the effect here http://snipurl.com/qfz0p<br /><br />It struck me that when we test we can often have a gut feel that a page we clicked a moment ago was somehow different than now. Is it Change Blindness that stops the difference being apparent to us.<br /><br />Exploratory testing is a great technique for overcoming this issue, if we 'feel' there is a difference there probably is. We can then apply ET approaches and tester skill to find where the bug is.<br /><br />MarkMark Crowtherhttps://www.blogger.com/profile/11540303029361604504noreply@blogger.comtag:blogger.com,1999:blog-326963428284433428.post-32353966588687352082009-08-05T00:00:36.490-07:002009-08-05T00:00:36.490-07:00Thanks fatima for your comment.
well, yes you are ...Thanks fatima for your comment.<br />well, yes you are true its not like demolishing the building rather, it is about building it in a right way,so that we have minimum or no issues later on , but testers always work with code breaking attitude so it seems destructive process.<br /><br />As far as your second point is concerned, sometimes we have scenario, where we have to consult our stake holders like, lets have a scenario, that after changing password, what would be appropriate behavior, user should be redirected to main page, or remian on this page, now this does not harm any body, but user can raise his desire, so there might e some usuability issues. in that case, as a tester, we should have a deep look on the application.<br /><br />i think i tried to clear my point, looking for your feedback.Kashif Ali Habibhttps://www.blogger.com/profile/14963125844474587107noreply@blogger.comtag:blogger.com,1999:blog-326963428284433428.post-75192283656626934992009-08-03T03:25:40.386-07:002009-08-03T03:25:40.386-07:00Some queries and comments here:
- In a psychologi...Some queries and comments here:<br /><br />- In a psychological way, testing could termed as destructive and sadistic but overall isn't it like demolishing a building in order to renovate or revamp it which surely give a sense of relief n feel of contentment? <br /><br />- Often s/w contains features that were not a part of requirements but also doesn't harm s/w in any sense, should we consider them as errors too in light of your following comments:<br />"...because purpose of software testing is to establish a confidence that software does what it is supposed to do, and does not do what it is not supposed to do."<br /><br />- Well, I am strongly agree with your this statement:<br />"...it can only be error free when testing is started with assumption that it contains errors in it. If we start testing with this frame of mind, then testing can add lot of value in software/application development. "Fatimanoreply@blogger.com