<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" gd:etag="W/&quot;DkIGRH0zeCp7ImA9WhRaFE8.&quot;"><id>tag:blogger.com,1999:blog-30945346</id><updated>2012-02-16T12:35:25.380-08:00</updated><category term="medium" /><category term="continuous integration" /><category term="agile" /><category term="hard" /><category term="funny" /><category term="April 1st" /><category term="QA manager" /><category term="CI" /><category term="tricky" /><category term="puzzle" /><category term="automation" /><category term="riddle" /><category term="book" /><category term="easy" /><title>QA Interview Questions and ANSWERS</title><subtitle type="html">SQA interview questions and answers</subtitle><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://www.sqainterview.com/feeds/posts/default" /><link rel="alternate" type="text/html" href="http://www.sqainterview.com/" /><link rel="next" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default?start-index=26&amp;max-results=25&amp;redirect=false&amp;v=2" /><author><name>MB</name><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>53</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/atom+xml" href="http://feeds.feedburner.com/QAInterview" /><feedburner:info xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" uri="qainterview" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><entry gd:etag="W/&quot;CEQHRncyeip7ImA9WhdREkk.&quot;"><id>tag:blogger.com,1999:blog-30945346.post-6521372517621557412</id><published>2010-05-07T15:24:00.000-07:00</published><updated>2011-08-01T16:45:37.992-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-08-01T16:45:37.992-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="automation" /><title>Why automated software testing fails?</title><link rel="replies" type="application/atom+xml" href="http://www.sqainterview.com/feeds/6521372517621557412/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=30945346&amp;postID=6521372517621557412" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/6521372517621557412?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/6521372517621557412?v=2" /><link rel="alternate" type="text/html" href="http://www.sqainterview.com/2010/05/why-automated-software-testing-fails.html" title="Why automated software testing fails?" /><author><name>MB</name><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><content type="html">Automated software testing has plenty of benefits and a lot of challenges. Despite the availability of a broad array of tools for software automation Silk Test, Selenium, HP QTP, Watir and etc), almost every QA Testing teams struggle with the similar standard architecture issues. In my opinion most of the issues are due to a lack of a preparation and training for building automated software 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/E1JyFB_beNiCyf-7ihchloVtaIM/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/E1JyFB_beNiCyf-7ihchloVtaIM/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/E1JyFB_beNiCyf-7ihchloVtaIM/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/E1JyFB_beNiCyf-7ihchloVtaIM/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=8wZ-TK4gtTY:TdG6fN-kbOA:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=8wZ-TK4gtTY:TdG6fN-kbOA:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=8wZ-TK4gtTY:TdG6fN-kbOA:eGeSNSsb_WU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=eGeSNSsb_WU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content></entry><entry gd:etag="W/&quot;CkYARH07fyp7ImA9WhRbEUg.&quot;"><id>tag:blogger.com,1999:blog-30945346.post-977701126326944270</id><published>2010-04-01T00:03:00.000-07:00</published><updated>2012-02-01T18:35:45.307-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-02-01T18:35:45.307-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="April 1st" /><title>What makes a good QA Tester?</title><link rel="replies" type="application/atom+xml" href="http://www.sqainterview.com/feeds/977701126326944270/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=30945346&amp;postID=977701126326944270" title="6 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/977701126326944270?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/977701126326944270?v=2" /><link rel="alternate" type="text/html" href="http://www.sqainterview.com/2010/04/what-makes-good-qa-tester.html" title="What makes a good QA Tester?" /><author><name>MB</name><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>6</thr:total><content type="html">There are several QA tester tricks to show uncanny abilities, improve visibility and get promoted very quickly:

Submit every typo, misprint as a separate Jira or Bugzilla bug report to inflate the bugs count.
In case your QA manager keeps track of number of test cases you written, churn out test cases by copying existing ones or copying the software requirement into another document as detailed 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/Kk13i1nL3Ur5RouKgWGxY6atiqo/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Kk13i1nL3Ur5RouKgWGxY6atiqo/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/Kk13i1nL3Ur5RouKgWGxY6atiqo/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Kk13i1nL3Ur5RouKgWGxY6atiqo/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=jlEBvvxuMA4:QmvZJ4vAbfk:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=jlEBvvxuMA4:QmvZJ4vAbfk:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=jlEBvvxuMA4:QmvZJ4vAbfk:eGeSNSsb_WU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=eGeSNSsb_WU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content></entry><entry gd:etag="W/&quot;DEYFRng7fSp7ImA9WxFTGEo.&quot;"><id>tag:blogger.com,1999:blog-30945346.post-7584729806271645856</id><published>2009-12-07T23:47:00.000-08:00</published><updated>2010-04-09T22:08:37.605-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-04-09T22:08:37.605-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="QA manager" /><category scheme="http://www.blogger.com/atom/ns#" term="tricky" /><title>How to evaluate QA tester's work?</title><link rel="replies" type="application/atom+xml" href="http://www.sqainterview.com/feeds/7584729806271645856/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=30945346&amp;postID=7584729806271645856" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/7584729806271645856?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/7584729806271645856?v=2" /><link rel="alternate" type="text/html" href="http://www.sqainterview.com/2009/12/how-to-evaluate-qa-testers-work.html" title="How to evaluate QA tester's work?" /><author><name>MB</name><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>2</thr:total><content type="html">Tricky Test manager interview question may sound like : Imagine being a test manager and trying to evaluate the performance of your QA testers. As we all know staff performance reviews is a one of the responsibilities of QA Managers. Software quality assurance engineers do a wide variety of tasks, such as bug hunting, bug reporting, test planning, and test tool development. To fully evaluate the 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/y9bjwbGZVoMMBqF4o9WugrTS5Sc/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/y9bjwbGZVoMMBqF4o9WugrTS5Sc/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/y9bjwbGZVoMMBqF4o9WugrTS5Sc/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/y9bjwbGZVoMMBqF4o9WugrTS5Sc/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=6OiamU6_xyg:IjK-p-JOXws:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=6OiamU6_xyg:IjK-p-JOXws:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=6OiamU6_xyg:IjK-p-JOXws:eGeSNSsb_WU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=eGeSNSsb_WU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content></entry><entry gd:etag="W/&quot;DUUHRH0zfyp7ImA9WxNUFU8.&quot;"><id>tag:blogger.com,1999:blog-30945346.post-3520472242404600621</id><published>2009-11-06T09:06:00.000-08:00</published><updated>2009-11-06T09:07:15.387-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-11-06T09:07:15.387-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="medium" /><category scheme="http://www.blogger.com/atom/ns#" term="QA manager" /><title>What is a good ratio of QA tester to developer?</title><link rel="replies" type="application/atom+xml" href="http://www.sqainterview.com/feeds/3520472242404600621/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=30945346&amp;postID=3520472242404600621" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/3520472242404600621?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/3520472242404600621?v=2" /><link rel="alternate" type="text/html" href="http://www.sqainterview.com/2009/11/what-is-good-ratio-of-qa-tester-to.html" title="What is a good ratio of QA tester to developer?" /><author><name>MB</name><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>1</thr:total><content type="html">It depends - is a correct answer on this no right or wrong Test Manager interview question. In my humble opinion, there exist no testing industry standards that cover the ratio of quality assurance testers to developers. In order to provide meaningful answer on the open ended interview question QA manager needs to know specific context. I would expect that the candidate for Test Manager position 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/jNNzin4a2PufPv0DhMcE1rashm0/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/jNNzin4a2PufPv0DhMcE1rashm0/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/jNNzin4a2PufPv0DhMcE1rashm0/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/jNNzin4a2PufPv0DhMcE1rashm0/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=iZbCPGaI70w:DuRS3sFp9JI:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=iZbCPGaI70w:DuRS3sFp9JI:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=iZbCPGaI70w:DuRS3sFp9JI:eGeSNSsb_WU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=eGeSNSsb_WU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content></entry><entry gd:etag="W/&quot;D0IBRHk5eip7ImA9WhZUEEg.&quot;"><id>tag:blogger.com,1999:blog-30945346.post-3498724974643501460</id><published>2009-10-16T16:34:00.000-07:00</published><updated>2011-06-02T15:59:15.722-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-06-02T15:59:15.722-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="tricky" /><title>What do you do when you get bored?</title><link rel="replies" type="application/atom+xml" href="http://www.sqainterview.com/feeds/3498724974643501460/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=30945346&amp;postID=3498724974643501460" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/3498724974643501460?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/3498724974643501460?v=2" /><link rel="alternate" type="text/html" href="http://www.sqainterview.com/2009/10/what-do-you-do-when-you-get-bored.html" title="What do you do when you get bored?" /><author><name>MB</name><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><content type="html">Test interview question should show the real value of interviewee. One of this not puzzle interview questions is asking the prospective candidature about dealing with utter boredom.  Occasionally testers get involved in the never ending testing of the same module of the same application. How should SQA Engineer adjust working behavior to continue successfully work on software project? 
One of the
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/EGTbxYPH6xZUDrQBPW09NJ16BFI/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/EGTbxYPH6xZUDrQBPW09NJ16BFI/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/EGTbxYPH6xZUDrQBPW09NJ16BFI/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/EGTbxYPH6xZUDrQBPW09NJ16BFI/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=PNEQYsVSPD8:CjRCR1ednzY:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=PNEQYsVSPD8:CjRCR1ednzY:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=PNEQYsVSPD8:CjRCR1ednzY:eGeSNSsb_WU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=eGeSNSsb_WU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content></entry><entry gd:etag="W/&quot;D0QCRHozcSp7ImA9WhZUEEg.&quot;"><id>tag:blogger.com,1999:blog-30945346.post-6475361934483732896</id><published>2009-09-18T15:44:00.000-07:00</published><updated>2011-06-02T15:56:05.489-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-06-02T15:56:05.489-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="riddle" /><category scheme="http://www.blogger.com/atom/ns#" term="puzzle" /><category scheme="http://www.blogger.com/atom/ns#" term="tricky" /><title>QA interview - testing toaster</title><link rel="replies" type="application/atom+xml" href="http://www.sqainterview.com/feeds/6475361934483732896/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=30945346&amp;postID=6475361934483732896" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/6475361934483732896?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/6475361934483732896?v=2" /><link rel="alternate" type="text/html" href="http://www.sqainterview.com/2009/09/qa-interview-testing-toaster.html" title="QA interview - testing toaster" /><author><name>MB</name><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><content type="html">How would you test a toaster, vending machine, electric kettle or ATM? Some QA managers consider this most common interview question as perfect QA interview question. In the same time the test interview question is the easiest one. QA engineer needs to tell just two magic words "requirements" and "specifications" and then approach toaster tests as any other usual application under test with 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/La5TiogBlQbTMoUdZXNwpPfRSok/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/La5TiogBlQbTMoUdZXNwpPfRSok/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/La5TiogBlQbTMoUdZXNwpPfRSok/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/La5TiogBlQbTMoUdZXNwpPfRSok/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=u2zgmmejXsI:Z8SVQnmvVYQ:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=u2zgmmejXsI:Z8SVQnmvVYQ:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=u2zgmmejXsI:Z8SVQnmvVYQ:eGeSNSsb_WU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=eGeSNSsb_WU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content></entry><entry gd:etag="W/&quot;DE4BRnk-eCp7ImA9WhdRE0k.&quot;"><id>tag:blogger.com,1999:blog-30945346.post-4658062388766121883</id><published>2009-09-01T11:00:00.000-07:00</published><updated>2011-08-02T21:49:17.750-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-08-02T21:49:17.750-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="riddle" /><category scheme="http://www.blogger.com/atom/ns#" term="puzzle" /><category scheme="http://www.blogger.com/atom/ns#" term="tricky" /><title>How would you test a toaster?</title><link rel="replies" type="application/atom+xml" href="http://www.sqainterview.com/feeds/4658062388766121883/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=30945346&amp;postID=4658062388766121883" title="10 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/4658062388766121883?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/4658062388766121883?v=2" /><link rel="alternate" type="text/html" href="http://www.sqainterview.com/2009/09/how-would-you-test-toaster.html" title="How would you test a toaster?" /><author><name>MB</name><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>10</thr:total><content type="html">Interview puzzles and riddles is the long going tradition in the software development companies like Google, Facebook and Microsoft.  Personally I would not make hiring decision for software test engineer position based on the puzzle interview question like "How would you test a toaster, vending machine, electric kettle, pencil or other appliance?", but some hiring QA managers still think that 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/DDa7zmxA46ioyQMdDBr7EXe3_SE/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/DDa7zmxA46ioyQMdDBr7EXe3_SE/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/DDa7zmxA46ioyQMdDBr7EXe3_SE/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/DDa7zmxA46ioyQMdDBr7EXe3_SE/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=ecIAmV9E3Zw:RvHpXrf2UiU:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=ecIAmV9E3Zw:RvHpXrf2UiU:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=ecIAmV9E3Zw:RvHpXrf2UiU:eGeSNSsb_WU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=eGeSNSsb_WU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content></entry><entry gd:etag="W/&quot;C0AFQ349fSp7ImA9WxNTFU4.&quot;"><id>tag:blogger.com,1999:blog-30945346.post-4592581090634786980</id><published>2009-08-17T10:54:00.000-07:00</published><updated>2009-08-17T10:55:12.065-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-08-17T10:55:12.065-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="QA manager" /><category scheme="http://www.blogger.com/atom/ns#" term="tricky" /><title>Should all testers be developers?</title><link rel="replies" type="application/atom+xml" href="http://www.sqainterview.com/feeds/4592581090634786980/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=30945346&amp;postID=4592581090634786980" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/4592581090634786980?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/4592581090634786980?v=2" /><link rel="alternate" type="text/html" href="http://www.sqainterview.com/2009/08/should-all-testers-be-developers.html" title="Should all testers be developers?" /><author><name>MB</name><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><content type="html">One more QA manager interview question could help to analyze the management abilities of candidate for QA manager position.  This interview questions especially critical for the QA teams working in Agile environment.In certain domains, there is some amount of testing that cannot reasonably be automated in the proper time. This testing requires that QA Engineer eyeballs carefully look at the 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/lElyW9yQbBumA8ZSY6sBUM1htoM/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/lElyW9yQbBumA8ZSY6sBUM1htoM/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/lElyW9yQbBumA8ZSY6sBUM1htoM/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/lElyW9yQbBumA8ZSY6sBUM1htoM/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=GgJyjWM4e9c:211rck5sM20:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=GgJyjWM4e9c:211rck5sM20:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=GgJyjWM4e9c:211rck5sM20:eGeSNSsb_WU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=eGeSNSsb_WU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content></entry><entry gd:etag="W/&quot;CUAFQ3w7cCp7ImA9WxJUGEQ.&quot;"><id>tag:blogger.com,1999:blog-30945346.post-8524313508123167157</id><published>2009-07-17T22:07:00.000-07:00</published><updated>2009-07-17T22:08:32.208-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-07-17T22:08:32.208-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="QA manager" /><category scheme="http://www.blogger.com/atom/ns#" term="tricky" /><title>How would you deal with smarty pants SQA Engineer</title><link rel="replies" type="application/atom+xml" href="http://www.sqainterview.com/feeds/8524313508123167157/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=30945346&amp;postID=8524313508123167157" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/8524313508123167157?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/8524313508123167157?v=2" /><link rel="alternate" type="text/html" href="http://www.sqainterview.com/2009/07/how-would-you-deal-with-smarty-pants.html" title="How would you deal with smarty pants SQA Engineer" /><author><name>MB</name><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><content type="html">This is a perfect QA manager interview question. Software quality assurance job market took a dramatic hit early this year, some signs of stabilization are appearing. A few recruiters believe layoffs have slowed. In the same time companies are not ready to begin hiring full-time testers, but many companies started to hire the contract workers to handle quality assurance projects that had been 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/m8ZAPwWkNOo-zypH35R2-GnsmaE/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/m8ZAPwWkNOo-zypH35R2-GnsmaE/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/m8ZAPwWkNOo-zypH35R2-GnsmaE/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/m8ZAPwWkNOo-zypH35R2-GnsmaE/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=jdAH0qnVjZ4:I-c1jGdgN-A:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=jdAH0qnVjZ4:I-c1jGdgN-A:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=jdAH0qnVjZ4:I-c1jGdgN-A:eGeSNSsb_WU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=eGeSNSsb_WU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content></entry><entry gd:etag="W/&quot;CUAFRH06fCp7ImA9WxJUEEQ.&quot;"><id>tag:blogger.com,1999:blog-30945346.post-7380969229998055648</id><published>2009-07-08T15:54:00.000-07:00</published><updated>2009-07-08T15:55:15.314-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-07-08T15:55:15.314-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="tricky" /><title>Name any software quality assurance or software testing magazine?</title><link rel="replies" type="application/atom+xml" href="http://www.sqainterview.com/feeds/7380969229998055648/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=30945346&amp;postID=7380969229998055648" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/7380969229998055648?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/7380969229998055648?v=2" /><link rel="alternate" type="text/html" href="http://www.sqainterview.com/2009/07/name-any-software-quality-assurance-or.html" title="Name any software quality assurance or software testing magazine?" /><author><name>MB</name><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><content type="html">As an interviewer I would not be surprised if prospective candidate for software quality assurance engineer position would answer that the interviewee doesn’t read software quality assurance or software testing magazines at all. I personally subscribed for couple of free software testing magazines, but usually I have found only one or two articles in the fiftyor so quality assurance magazines I 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/4f-M85zxy3orgpQ17DxY3Q6oLFE/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/4f-M85zxy3orgpQ17DxY3Q6oLFE/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/4f-M85zxy3orgpQ17DxY3Q6oLFE/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/4f-M85zxy3orgpQ17DxY3Q6oLFE/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=R4AI81SqOZA:lISSEEWU2Xw:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=R4AI81SqOZA:lISSEEWU2Xw:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=R4AI81SqOZA:lISSEEWU2Xw:eGeSNSsb_WU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=eGeSNSsb_WU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content></entry><entry gd:etag="W/&quot;DUcERXk5fSp7ImA9WhdRE0k.&quot;"><id>tag:blogger.com,1999:blog-30945346.post-3911582532618998485</id><published>2009-06-11T18:05:00.000-07:00</published><updated>2011-08-02T21:50:04.725-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-08-02T21:50:04.725-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="medium" /><title>What's in your Testers Tool Box?</title><link rel="replies" type="application/atom+xml" href="http://www.sqainterview.com/feeds/3911582532618998485/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=30945346&amp;postID=3911582532618998485" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/3911582532618998485?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/3911582532618998485?v=2" /><link rel="alternate" type="text/html" href="http://www.sqainterview.com/2009/06/whats-in-your-testers-tool-box.html" title="What's in your Testers Tool Box?" /><author><name>MB</name><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>1</thr:total><content type="html">The test interview is not only a test of interviewee specific knowledge, but an opportunity to knowledge exchange. As an interviewer I have to spend at least half an hour interviewing some potential Quality Assurance Engineer and I want to use these minutes wisely. For example, I like to interview testers about various tools they use during preparation and actual testing. Here are some wonderful 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/hMvOf8aGwCs_merHHyym4KNZ2tA/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/hMvOf8aGwCs_merHHyym4KNZ2tA/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/hMvOf8aGwCs_merHHyym4KNZ2tA/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/hMvOf8aGwCs_merHHyym4KNZ2tA/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=4nu-K1Q8l-E:9DBQ_ZyN_m8:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=4nu-K1Q8l-E:9DBQ_ZyN_m8:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=4nu-K1Q8l-E:9DBQ_ZyN_m8:eGeSNSsb_WU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=eGeSNSsb_WU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content></entry><entry gd:etag="W/&quot;DUUEQHo9cCp7ImA9WxJXFE4.&quot;"><id>tag:blogger.com,1999:blog-30945346.post-5547571661084441256</id><published>2009-06-07T22:00:00.000-07:00</published><updated>2009-06-07T22:00:01.468-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-06-07T22:00:01.468-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="hard" /><title>What do you hate about testing?</title><link rel="replies" type="application/atom+xml" href="http://www.sqainterview.com/feeds/5547571661084441256/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=30945346&amp;postID=5547571661084441256" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/5547571661084441256?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/5547571661084441256?v=2" /><link rel="alternate" type="text/html" href="http://www.sqainterview.com/2009/06/what-do-you-hate-about-testing.html" title="What do you hate about testing?" /><author><name>MB</name><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><content type="html">Tester interview questions usually focused on positive results, like most obvious test interview question is what do you like about testing, but should it be the case. I believe asking reverse interview question would open the real mind of candidate for Test Engineer position and would perfectly describe the software development organization where Test Engineer works now. The most hated term 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/Q6Qw58kRiOQ7i0AGYdMU43Cras0/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Q6Qw58kRiOQ7i0AGYdMU43Cras0/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/Q6Qw58kRiOQ7i0AGYdMU43Cras0/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Q6Qw58kRiOQ7i0AGYdMU43Cras0/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=BYYWZ-9gj6c:DcL5u5FXT8g:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=BYYWZ-9gj6c:DcL5u5FXT8g:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=BYYWZ-9gj6c:DcL5u5FXT8g:eGeSNSsb_WU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=eGeSNSsb_WU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content></entry><entry gd:etag="W/&quot;D0MCQHo4fip7ImA9WxJXEE0.&quot;"><id>tag:blogger.com,1999:blog-30945346.post-31385346888218661</id><published>2009-06-02T22:01:00.000-07:00</published><updated>2009-06-02T22:04:21.436-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-06-02T22:04:21.436-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="medium" /><title>Why do you want to leave your current job?</title><link rel="replies" type="application/atom+xml" href="http://www.sqainterview.com/feeds/31385346888218661/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=30945346&amp;postID=31385346888218661" title="3 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/31385346888218661?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/31385346888218661?v=2" /><link rel="alternate" type="text/html" href="http://www.sqainterview.com/2009/06/why-do-you-want-to-leave-your-current.html" title="Why do you want to leave your current job?" /><author><name>MB</name><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>3</thr:total><content type="html">Here are some suggestions for answering this interview question. Try to put some positive spin in your answer. First of all it means that you shouldn’t say anything negative about your current position and people while being interviewed at new company or at least try a neutral mode. For example one interviewee could answer as "I have had it with working with QA Engineers who couldn't test a 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/Wa4mG2FqyO8DCwUs1MBBeGxBCNE/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Wa4mG2FqyO8DCwUs1MBBeGxBCNE/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/Wa4mG2FqyO8DCwUs1MBBeGxBCNE/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Wa4mG2FqyO8DCwUs1MBBeGxBCNE/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=d7vi7dgvClo:6wbJNvRktiU:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=d7vi7dgvClo:6wbJNvRktiU:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=d7vi7dgvClo:6wbJNvRktiU:eGeSNSsb_WU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=eGeSNSsb_WU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content></entry><entry gd:etag="W/&quot;CkUNRXY4fyp7ImA9WxJQFkk.&quot;"><id>tag:blogger.com,1999:blog-30945346.post-1480027510143276956</id><published>2009-05-29T16:37:00.000-07:00</published><updated>2009-05-29T16:38:14.837-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-05-29T16:38:14.837-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="automation" /><title>Define test automation requirements for developing web application?</title><link rel="replies" type="application/atom+xml" href="http://www.sqainterview.com/feeds/1480027510143276956/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=30945346&amp;postID=1480027510143276956" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/1480027510143276956?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/1480027510143276956?v=2" /><link rel="alternate" type="text/html" href="http://www.sqainterview.com/2009/05/define-test-automation-requirements-for.html" title="Define test automation requirements for developing web application?" /><author><name>MB</name><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><content type="html">Imagine that you were asked to evaluate web application from test automation friendliest point of view. These criteria could be used to name web application automation friendly in order to test an application with SilktTest, QTP, Selenium or any other test automation tool.All web pages should have namesSimilar objects should have consistent names Unique names should be used for various objectsAll
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/PcznMf5kDxbnwIGN0ZbbJ-aTpa0/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/PcznMf5kDxbnwIGN0ZbbJ-aTpa0/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/PcznMf5kDxbnwIGN0ZbbJ-aTpa0/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/PcznMf5kDxbnwIGN0ZbbJ-aTpa0/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=7gZu0b0wmWw:t0JPZKslA-Q:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=7gZu0b0wmWw:t0JPZKslA-Q:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=7gZu0b0wmWw:t0JPZKslA-Q:eGeSNSsb_WU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=eGeSNSsb_WU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content></entry><entry gd:etag="W/&quot;CUQBRHk6fCp7ImA9WxJQFEo.&quot;"><id>tag:blogger.com,1999:blog-30945346.post-5909262860277594129</id><published>2009-05-27T15:58:00.000-07:00</published><updated>2009-05-27T18:15:55.714-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-05-27T18:15:55.714-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="agile" /><category scheme="http://www.blogger.com/atom/ns#" term="funny" /><title>The Downfall of Agile</title><link rel="replies" type="application/atom+xml" href="http://www.sqainterview.com/feeds/5909262860277594129/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=30945346&amp;postID=5909262860277594129" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/5909262860277594129?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/5909262860277594129?v=2" /><link rel="alternate" type="text/html" href="http://www.sqainterview.com/2009/05/downfall-of-agile-hitler.html" title="The Downfall of Agile" /><author><name>MB</name><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>1</thr:total><content type="html">The agile lead goes crazy when he learns his agile team has not been following the principles of the agile manifesto. Show this clip to an interviewee. If the interviewee starts smiling and commenting, hire this person immediately. 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/TalGV9MDRqKmxC12uU-jA0hQJeI/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/TalGV9MDRqKmxC12uU-jA0hQJeI/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/TalGV9MDRqKmxC12uU-jA0hQJeI/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/TalGV9MDRqKmxC12uU-jA0hQJeI/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=P5TvBvt8A9I:Ze114AT3UqY:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=P5TvBvt8A9I:Ze114AT3UqY:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=P5TvBvt8A9I:Ze114AT3UqY:eGeSNSsb_WU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=eGeSNSsb_WU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content></entry><entry gd:etag="W/&quot;DUMER304eCp7ImA9WxJRF0g.&quot;"><id>tag:blogger.com,1999:blog-30945346.post-4996533266723575965</id><published>2009-05-19T11:22:00.000-07:00</published><updated>2009-05-19T11:23:26.330-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-05-19T11:23:26.330-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="medium" /><title>How do you keep your testing skills updated?</title><link rel="replies" type="application/atom+xml" href="http://www.sqainterview.com/feeds/4996533266723575965/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=30945346&amp;postID=4996533266723575965" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/4996533266723575965?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/4996533266723575965?v=2" /><link rel="alternate" type="text/html" href="http://www.sqainterview.com/2009/05/how-do-you-keep-your-testing-skills.html" title="How do you keep your testing skills updated?" /><author><name>MB</name><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><content type="html">This is a wonderful testing interview questions and I ask this one to everyone whom I interview recently for QA Engineer position.  There are a few possible answers:Read testing websites, magazines and books to understand latest trends in software testing industry. Read about new testing tools available in market. Practice by trying out different testing toolsAttend professional testing 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/ksbZ4zah5UHfdyKUDgNSl1uE5Hs/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/ksbZ4zah5UHfdyKUDgNSl1uE5Hs/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/ksbZ4zah5UHfdyKUDgNSl1uE5Hs/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/ksbZ4zah5UHfdyKUDgNSl1uE5Hs/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=EaC8tLTd7mY:Qtn1XsRj1sk:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=EaC8tLTd7mY:Qtn1XsRj1sk:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=EaC8tLTd7mY:Qtn1XsRj1sk:eGeSNSsb_WU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=eGeSNSsb_WU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content></entry><entry gd:etag="W/&quot;CUEGSX8zeyp7ImA9WxJSGE0.&quot;"><id>tag:blogger.com,1999:blog-30945346.post-2417143475299282284</id><published>2009-05-08T10:25:00.000-07:00</published><updated>2009-05-08T10:27:08.183-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-05-08T10:27:08.183-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="CI" /><category scheme="http://www.blogger.com/atom/ns#" term="medium" /><category scheme="http://www.blogger.com/atom/ns#" term="continuous integration" /><title>Does your team use continuous integration?</title><link rel="replies" type="application/atom+xml" href="http://www.sqainterview.com/feeds/2417143475299282284/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=30945346&amp;postID=2417143475299282284" title="3 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/2417143475299282284?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/2417143475299282284?v=2" /><link rel="alternate" type="text/html" href="http://www.sqainterview.com/2009/05/does-your-team-use-continuous.html" title="Does your team use continuous integration?" /><author><name>MB</name><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>3</thr:total><content type="html">If tester doesn't understand what interviewer means by continuous integration, the tester probably didn't work in a good software environment. How can QA Engineer get steady code build for testing if there is no bulletproof method of building and deploying code to testing and production environment?  If there is no continuous integration process in place, QA Engineers most likely would spend time
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/2xzrHyuHBu3sX5kwtMVpJQ2D4aA/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/2xzrHyuHBu3sX5kwtMVpJQ2D4aA/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/2xzrHyuHBu3sX5kwtMVpJQ2D4aA/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/2xzrHyuHBu3sX5kwtMVpJQ2D4aA/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=JW7-dfUb-x0:4NVjbrSZeeI:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=JW7-dfUb-x0:4NVjbrSZeeI:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=JW7-dfUb-x0:4NVjbrSZeeI:eGeSNSsb_WU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=eGeSNSsb_WU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content></entry><entry gd:etag="W/&quot;CUANQH06cCp7ImA9WxJSE0Q.&quot;"><id>tag:blogger.com,1999:blog-30945346.post-4269545368591218728</id><published>2009-04-30T15:46:00.000-07:00</published><updated>2009-05-03T16:36:31.318-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-05-03T16:36:31.318-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="automation" /><title>Why does test automation project fail?</title><link rel="replies" type="application/atom+xml" href="http://www.sqainterview.com/feeds/4269545368591218728/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=30945346&amp;postID=4269545368591218728" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/4269545368591218728?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/4269545368591218728?v=2" /><link rel="alternate" type="text/html" href="http://www.sqainterview.com/2009/04/why-do-test-automation-project-fail.html" title="Why does test automation project fail?" /><author><name>MB</name><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><content type="html">The following problems are often encountered during test automation projects and may result in failing test automation projects:Management doesn't treat test automation as software development. Anyone can test and automation is easy – just record and playback.QA team select wrong set of test cases for test automation. In the same time, management aims for 100% test automation of all test cases. 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/dBuIuYAPHf9jHuMxoGE8JctgbGs/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/dBuIuYAPHf9jHuMxoGE8JctgbGs/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/dBuIuYAPHf9jHuMxoGE8JctgbGs/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/dBuIuYAPHf9jHuMxoGE8JctgbGs/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=MFnqLiQUY4Y:hfPmjp9eMR8:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=MFnqLiQUY4Y:hfPmjp9eMR8:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=MFnqLiQUY4Y:hfPmjp9eMR8:eGeSNSsb_WU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=eGeSNSsb_WU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content></entry><entry gd:etag="W/&quot;DE4MQXk4fyp7ImA9WxJTEkk.&quot;"><id>tag:blogger.com,1999:blog-30945346.post-4661878070592066528</id><published>2009-04-20T10:03:00.000-07:00</published><updated>2009-04-20T10:03:00.737-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-04-20T10:03:00.737-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="medium" /><title>How to report bugs effectively?</title><link rel="replies" type="application/atom+xml" href="http://www.sqainterview.com/feeds/4661878070592066528/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=30945346&amp;postID=4661878070592066528" title="6 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/4661878070592066528?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/4661878070592066528?v=2" /><link rel="alternate" type="text/html" href="http://www.sqainterview.com/2009/04/how-to-report-bugs-effectively.html" title="How to report bugs effectively?" /><author><name>MB</name><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>6</thr:total><content type="html">The best way to report bugs effectively is too use standard bug report template. The bug tracking tools like Jira or Bugzilla already have predefined bug report template. Quality Assurance Engineer should include good supporting documents with some of the bug reports like screen shots, data samples or log files.
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/WP_aYIHyUndmJTZ6dqPJkmutShM/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/WP_aYIHyUndmJTZ6dqPJkmutShM/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/WP_aYIHyUndmJTZ6dqPJkmutShM/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/WP_aYIHyUndmJTZ6dqPJkmutShM/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=3YlaPwIDf0Y:creBfDDyriw:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=3YlaPwIDf0Y:creBfDDyriw:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=3YlaPwIDf0Y:creBfDDyriw:eGeSNSsb_WU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=eGeSNSsb_WU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content></entry><entry gd:etag="W/&quot;D0UEQns8fSp7ImA9WxNWGE8.&quot;"><id>tag:blogger.com,1999:blog-30945346.post-8392253821345062874</id><published>2009-04-18T08:00:00.000-07:00</published><updated>2009-10-17T17:20:03.575-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-17T17:20:03.575-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="medium" /><title>How do you know when to stop testing?</title><link rel="replies" type="application/atom+xml" href="http://www.sqainterview.com/feeds/8392253821345062874/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=30945346&amp;postID=8392253821345062874" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/8392253821345062874?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/8392253821345062874?v=2" /><link rel="alternate" type="text/html" href="http://www.sqainterview.com/2009/04/how-do-you-know-when-to-stop-testing.html" title="How do you know when to stop testing?" /><author><name>MB</name><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><content type="html">There are several ways for Quality Assurance Engineer to find out when testing stops:Software product  is never tested enoughRelease, testing or customer deadline has been metAll test cases have been executed and certain predetermined percentage of the passedPredetermined code coverage percentage is metThe number of found bugs or bug severity falls to a certain pointNo money left to continue 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/JUhTxRjR2JPb8qhqsA8Y2aHpJqQ/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/JUhTxRjR2JPb8qhqsA8Y2aHpJqQ/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/JUhTxRjR2JPb8qhqsA8Y2aHpJqQ/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/JUhTxRjR2JPb8qhqsA8Y2aHpJqQ/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=LOutIczxVmg:ismHMrzPT7U:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=LOutIczxVmg:ismHMrzPT7U:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=LOutIczxVmg:ismHMrzPT7U:eGeSNSsb_WU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=eGeSNSsb_WU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content></entry><entry gd:etag="W/&quot;C0AEQXo8fSp7ImA9WxVaGEg.&quot;"><id>tag:blogger.com,1999:blog-30945346.post-4025027145790654994</id><published>2009-04-15T20:15:00.000-07:00</published><updated>2009-04-15T20:15:00.475-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-04-15T20:15:00.475-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="medium" /><title>Could you name a few testing activities?</title><link rel="replies" type="application/atom+xml" href="http://www.sqainterview.com/feeds/4025027145790654994/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=30945346&amp;postID=4025027145790654994" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/4025027145790654994?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/4025027145790654994?v=2" /><link rel="alternate" type="text/html" href="http://www.sqainterview.com/2009/04/could-you-name-few-testing-activities.html" title="Could you name a few testing activities?" /><author><name>MB</name><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><content type="html">QA Engineer role usually includes a variety of testing activities:Create test plans and test casesExecute testsLog bugsCommunicate with various team members like testers, developer and managersMake crucial decisions on whether something is a bug or a design constraintSchedule projectsAllocate human and technical resourcesMake crucial decisions about the software applications Automate testing 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/EueYYRWpADDRarMC70tJJ4-58FM/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/EueYYRWpADDRarMC70tJJ4-58FM/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/EueYYRWpADDRarMC70tJJ4-58FM/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/EueYYRWpADDRarMC70tJJ4-58FM/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=vjFzzxn3-A0:jHcz_sZKQbE:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=vjFzzxn3-A0:jHcz_sZKQbE:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=vjFzzxn3-A0:jHcz_sZKQbE:eGeSNSsb_WU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=eGeSNSsb_WU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content></entry><entry gd:etag="W/&quot;CEcMSHs_cSp7ImA9WxVaFkU.&quot;"><id>tag:blogger.com,1999:blog-30945346.post-2955658496333638170</id><published>2009-04-13T21:07:00.000-07:00</published><updated>2009-04-13T21:08:09.549-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-04-13T21:08:09.549-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="medium" /><title>What makes a good QA Engineer?</title><link rel="replies" type="application/atom+xml" href="http://www.sqainterview.com/feeds/2955658496333638170/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=30945346&amp;postID=2955658496333638170" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/2955658496333638170?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/2955658496333638170?v=2" /><link rel="alternate" type="text/html" href="http://www.sqainterview.com/2009/04/what-makes-good-qa-engineer.html" title="What makes a good QA Engineer?" /><author><name>MB</name><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>1</thr:total><content type="html">A good QA Engineer should able to perform the following tasks successfully in any environment:Verification: A good QA Engineer can officially state that it is possible to accomplish certain tasks.Detection: A good QA Engineer seeks issues that exist, either in the process or the product.Prevention: A good QA Engineer recognizes potential issues before they become visible.Reflection: A good QA 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/7VnUFeW_HLMMVuVcHIWBgqzlnXM/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/7VnUFeW_HLMMVuVcHIWBgqzlnXM/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/7VnUFeW_HLMMVuVcHIWBgqzlnXM/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/7VnUFeW_HLMMVuVcHIWBgqzlnXM/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=QaM8_2uhmrA:PvNMhPbo_rM:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=QaM8_2uhmrA:PvNMhPbo_rM:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=QaM8_2uhmrA:PvNMhPbo_rM:eGeSNSsb_WU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=eGeSNSsb_WU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content></entry><entry gd:etag="W/&quot;D0AERX88eCp7ImA9WxFTGEo.&quot;"><id>tag:blogger.com,1999:blog-30945346.post-9150419244616802009</id><published>2009-04-07T21:30:00.000-07:00</published><updated>2010-04-09T22:01:44.170-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-04-09T22:01:44.170-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="easy" /><title>What are prerequisites for white box testing?</title><link rel="replies" type="application/atom+xml" href="http://www.sqainterview.com/feeds/9150419244616802009/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=30945346&amp;postID=9150419244616802009" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/9150419244616802009?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/9150419244616802009?v=2" /><link rel="alternate" type="text/html" href="http://www.sqainterview.com/2009/04/what-are-prerequisites-for-white-box.html" title="What are prerequisites for white box testing?" /><author><name>MB</name><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><content type="html">In general prerequisites for  white box testing are the same as for black box testing. The only difference is the access to the application source code. The white box tester should ask for detailed requirement, functional specifications, high-level design documents, detailed design documents and source code. The white box QA Engineer would analyze the source code and prepare test cases for 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/cHZl_MVSqJHthqVR71Osu4GlfpM/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/cHZl_MVSqJHthqVR71Osu4GlfpM/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/cHZl_MVSqJHthqVR71Osu4GlfpM/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/cHZl_MVSqJHthqVR71Osu4GlfpM/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=wpisrZ3o_fk:YpW0nqIm850:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=wpisrZ3o_fk:YpW0nqIm850:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=wpisrZ3o_fk:YpW0nqIm850:eGeSNSsb_WU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=eGeSNSsb_WU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content></entry><entry gd:etag="W/&quot;DkUNQns_fCp7ImA9WhZTGEw.&quot;"><id>tag:blogger.com,1999:blog-30945346.post-7104279360600177976</id><published>2009-04-01T01:30:00.000-07:00</published><updated>2011-03-22T10:18:13.544-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-03-22T10:18:13.544-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="puzzle" /><category scheme="http://www.blogger.com/atom/ns#" term="April 1st" /><category scheme="http://www.blogger.com/atom/ns#" term="tricky" /><title>Can you solve this QA interview puzzle?</title><link rel="replies" type="application/atom+xml" href="http://www.sqainterview.com/feeds/7104279360600177976/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=30945346&amp;postID=7104279360600177976" title="13 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/7104279360600177976?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/7104279360600177976?v=2" /><link rel="alternate" type="text/html" href="http://www.sqainterview.com/2009/04/can-you-solve-this-qa-interview-puzzle.html" title="Can you solve this QA interview puzzle?" /><author><name>MB</name><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>13</thr:total><content type="html">As you know many interviewers like to ask interviewee to solve tricky puzzle as QA interview question.  Perhaps you heard about puzzles like: why are manholes covers round, how do they make M&amp;amp;Ms, how many piano tuners are there in San Francisco. Almost all puzzles used for QA interview are documented in the book How Would You Move Mount Fuji? : Microsoft's Cult of the Puzzle. If after reading 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/-DUg7UQxReuYi2pnwAxE7DKIdtw/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/-DUg7UQxReuYi2pnwAxE7DKIdtw/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/-DUg7UQxReuYi2pnwAxE7DKIdtw/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/-DUg7UQxReuYi2pnwAxE7DKIdtw/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=WK5i3tJV-1I:DVq9bveNC7Q:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=WK5i3tJV-1I:DVq9bveNC7Q:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=WK5i3tJV-1I:DVq9bveNC7Q:eGeSNSsb_WU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=eGeSNSsb_WU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content></entry><entry gd:etag="W/&quot;DUcGR3c_eCp7ImA9WhdRE0k.&quot;"><id>tag:blogger.com,1999:blog-30945346.post-3822779108310811632</id><published>2009-03-24T08:41:00.000-07:00</published><updated>2011-08-02T21:50:26.940-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-08-02T21:50:26.940-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="automation" /><title>What tests shouldn't we automate?</title><link rel="replies" type="application/atom+xml" href="http://www.sqainterview.com/feeds/3822779108310811632/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=30945346&amp;postID=3822779108310811632" title="5 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/3822779108310811632?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30945346/posts/default/3822779108310811632?v=2" /><link rel="alternate" type="text/html" href="http://www.sqainterview.com/2009/03/what-tests-shouldnt-we-automate.html" title="What tests shouldn't we automate?" /><author><name>MB</name><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>5</thr:total><content type="html">Most types of testing benefit from automation, but some testing type's needs a real human attention and intelligence. It is possible, but difficult to automate GUI even with agile compatible tools like Selenium. Usability testing, exploratory testing and test that will never fail should not be considered as targets for test automation.
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/8fK9suScW-g71MwINi4d7UztoBw/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/8fK9suScW-g71MwINi4d7UztoBw/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/8fK9suScW-g71MwINi4d7UztoBw/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/8fK9suScW-g71MwINi4d7UztoBw/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=v4K9mglCtBo:peYXYAqZFgY:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=v4K9mglCtBo:peYXYAqZFgY:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/QAInterview?a=v4K9mglCtBo:peYXYAqZFgY:eGeSNSsb_WU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/QAInterview?d=eGeSNSsb_WU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content></entry></feed>

