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.

How to report bugs effectively?

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.

6 comments:

Anonymous said...

kindly advise how to deal with non reproducible bugs.

naveen

Anonymous said...

While testing any application,you must remember all actions done before you found any bug.
That might be a 10 minutes before or from the start of the application till you find some bug.

You must provide all these actions in the bug report along with the all available logs, if GUI issues, screen snaps etc.

Sushitha said...

You can keep non reproducible bug as an investigative bug and keep an eye on that always when you perform regression. You have chance of getting it again when you do so. That time you can record all the steps to reproduce it.

Anonymous said...

If a release has 80 bugs, what would you say about the product?

Anonymous said...

"It depends" is the correct answer for questions about "the release with 80 bugs". It depends from the size of the project, from the severity and priority of the bugs and so on.

Anonymous said...

If the non reproducible bug causes system crash, report it as soon as you can with high severity but low priority.

Common QA engineer interview questions