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.

Does your team use continuous integration?

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 finding and reporting "show-stopper" and unit level bugs. The interviewee should be prepared to answer what source control (also known as version control, source control or (source) code management (SCM) systems they used. There are plenty of them around and most popular are SV, Perforce and VSS. The interviewee also needs to know about continuous integration software like CruiseControl, Bamboo or Hudson.

3 comments:

Mr. Hericus said...

It's good to see the focus of CI going beyond the traditional dev team. QA needs to be aware of CI for two main reasons:

1) They need to be aware because they will be the consumers of the artifacts from the CI system.

2) They need to be aware because if there is no CI system in process, they should absolutely push back on the dev team and force them to introduce CI.

QA has more power than they often realize. Use it!

Anonymous said...

Definition of CI is still not clear. Please can yoube more precise?

Anonymous said...

Look up Continuous Integration on Wikipedia

Common QA engineer interview questions