QA interview questions and answers are completely based on the QA interview I and my friends attended during last years of working experience as Quality Assurance Testers. These tricky QA questions and scenarios are based only on real experience and were asked during actual QA interviews. Therefore, QA Tester who is looking for a Quality Assurance job will greatly benefit from this. If you are the first time job seeker as a QA Tester, then it can help you even better. Finally, if you are plant to attend an interview, you have to know these questions and answers by heart and must be very smooth in answering these questions. Practice in front of the foe or just a mirror, speak loud and clear. All the time, when you study the questions, you feel fine and feel relaxed, but the reality is, at the time of the actual interview, even though you feel you have the knowledge, cannot express it well. It may sound a little rough, but this is everyone’s hard experience. When you come out the interview door, you are deeply regretted. If you cannot remember these by heart, believe me, it may not work. The Testers are welcome to post own questions and answers to the following QA interview questions.

What tests shouldn't we automate?

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.

6 comments:

Anonymous said...

why do these are difficult to automate can you please explain?

Anonymous said...

can you please explain why can't these be automated.

Evgeni Reingold said...

Disagree with the post.

As a matter of fact QTP (Quick Test Pro) tool as well as Rational Robot and Win Runner are intended to automate Functional or GUI testing - the most complicated QA activity.

Anonymous said...

Load/stress testing needs to be automated. Other than that, if the effort to maintain the automated script(s) exceeds the manual testing effort... those are the case to think about doing manual testing. Creating and debugging an automated script involves manually executing the test case multiple times. If the script is only good for one release then there's no point.

Jason said...

Why would you guys disagree with this post? How would you test usability and exploratory with automation tool?
Unless you have WALL·E working for you, I see no way for such level of intelligence exists even is space technology :)

Anonymous said...

About 7 years ago - I've got interview in company, where they told me that using WinRunner and additional tools they automated 85 - 90% and would like to automate 100% of testing. I said - good luck and left interview.

Common QA engineer interview questions