tag:blogger.com,1999:blog-1695460650467928609.post6452406064600901820..comments2024-03-28T01:27:39.788-07:00Comments on Software Testing Tricks: Busting 5 Software Testing Myths/Misconceptions!Debasis Pradhanhttp://www.blogger.com/profile/15059356907987625705noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-1695460650467928609.post-72635216220507066152014-08-12T05:03:00.944-07:002014-08-12T05:03:00.944-07:00Interesting and a thoughtful post.
This a very goo...Interesting and a thoughtful post.<br />This a very good write and useful piece of information shared.<br />Thanks! a ton for sharing your experience.<br /><br />Regards,<br /><a href="http://maveric-systems.com/index.aspx" rel="nofollow">Software Testing Companies</a><br /><br />Anonymoushttps://www.blogger.com/profile/10278138151196135334noreply@blogger.comtag:blogger.com,1999:blog-1695460650467928609.post-84751966268248445662013-06-27T03:09:32.359-07:002013-06-27T03:09:32.359-07:00Even I agree to your view that the programmer and ...Even I agree to your view that the programmer and tester should be in good terms so that they can mutually exchange their views and there will be betterment in the product development rather than fighting between themselves and utilizing the program as a weapon.QA Testerhttp://proitonlinetraining.comnoreply@blogger.comtag:blogger.com,1999:blog-1695460650467928609.post-41087977267628038432012-05-27T20:34:19.764-07:002012-05-27T20:34:19.764-07:00Yes, your 5 myths are certainly myths. I think ano...Yes, your 5 myths are certainly myths. I think another one would be "Testers are no longer needed with Agile development because developers test their code". We have found that although the developers may do unit testing and perhaps even more than unit testing, there is still a big need for end user black box testing. Additionally, QA personnel on an agile team tend to do requirement work in tying product management to development.software test automationhttp://www.xbosoft.com/english/test-automation-services/noreply@blogger.comtag:blogger.com,1999:blog-1695460650467928609.post-74109071883671742052008-02-15T06:31:00.000-08:002008-02-15T06:31:00.000-08:00@ NSMV (Lakshmi),This is an interesting question a...@ NSMV (Lakshmi),<BR/><BR/>This is an interesting question and I am glad that you asked it! To answer such a question, I had <A HREF="http://software-testing-zone.blogspot.com/2007/06/software-testers-do-we-assure-quality.html" REL="nofollow">written an article</A> few months back. I recommend you to go through it (along with the comments left on the article) and leave your comment on it if you still feel - "As Testers we can Assure the Quality of the Product under Test"!<BR/><BR/><I>You said... Testing is useful in finding bugs (in my view let's say as quality perspective bugs) and this automatically puts quality a step ahead by fixing those bugs.</I><BR/><BR/>This assumption of yours can fail because:<BR/><BR/><B>1. It is an inherent quality of software testing that it can show that bugs exist, but not that bugs don’t exist.<BR/><BR/>2. Every method you use to prevent or find bugs leaves a residue of subtler bugs against which those methods are ineffectual. — BORIS BEIZER</B><BR/><BR/>This is called as <B>"The Pesticide Paradox"</B>. In 1990, Boris Beizer described the ‘pesticide paradox’ phenomenon: The more you test software, the more immune it becomes to your tests. He asserted that software undergoing the same repetitive tests eventually builds up resistance to them, similar to the reaction of insects to pesticides: if you keep applying the same pesticide, the insects eventually build up resistance and the pesticide no longer works.<BR/><BR/>So just because testing can uncover bugs, it does not necessarily mean that testing can enhance the QUALITY. Quality is a multi-dimensional thing and is much more than testing. Take this: A video game is released to market after extensive testing and with *almost* no known-bugs in it. What if the users playing this game don't find it interesting enough to play? What if they find the game to be too boring and difficult to learn and comprehend? Would you still call it a QUALITY video game, just because it is quite robust in it's design and lacks any serious bugs in it?<BR/><BR/>-Debasis.Debasis Pradhanhttps://www.blogger.com/profile/15059356907987625705noreply@blogger.comtag:blogger.com,1999:blog-1695460650467928609.post-44174008601149570342008-02-15T04:52:00.000-08:002008-02-15T04:52:00.000-08:00Hi Debasis!!I have a question for you!!!How "Quali...Hi Debasis!!<BR/><BR/>I have a question for you!!!<BR/><BR/>How "Quality cannot be assured by testing?"<BR/><BR/>To the best of my knowledge, <BR/>Testing is useful in finding bugs(in my view let's say as quality perspective bugs) and this automatically puts quality a step ahead by fixing those bugs. Though we are informers of the quality, the process (testing) is a shadower of Quality.<BR/><BR/>If iam wrong please correct me.....Unknownhttps://www.blogger.com/profile/09170368899278633605noreply@blogger.comtag:blogger.com,1999:blog-1695460650467928609.post-21295085698683624632007-04-09T03:55:00.000-07:002007-04-09T03:55:00.000-07:00What makes a good Software Test engineer? A good t...What makes a good Software Test engineer? <BR/>A good test engineer has a 'test to break' attitude, an ability to take the point of view of the customer, a strong desire for quality, and an attention to detail. <BR/>Source: http://www.softwareqatest.com<BR/><BR/>I agree the above answer that good tester will try to break the software so that in production it will not fail.Anonymousnoreply@blogger.com