Interview questions for Test Engineer

This post is for QA engineers who are planning for a Senior test engineer or a Team lead role. To help them in their preparation, we’ve added ten must know QA interview questions and answers in this article.

We brought these must know QA interview questions after putting up a lot of research. It involved meeting with candidates who appeared for a Senior test engineer/Test lead interview. That’s how we could keep the questionnaire a bit more realistic and practical.

Also, most interviewers expect an answer which seems real and backed by an example. So, don’t reply with answers that look like reading from a book.

Apart from these must know QA interview questions, you might like to check out the below posts. These offer some of the best technical questionnaires for Senior test engineers.

Also, it’s not late that we’d posted a two part series of Software testing interview questions and answers. So please see through these blog posts, they might be pretty useful for the interview preparation.

Now, it’s time to dive into reading the must know QA interview questions and answers.

Q-1# What are the steps you follow to create a test script?

Ans# Creating a test script usually requires the below steps.

Step-1# The primary requirement is to get a thorough understanding of the Application Under Test.

• To achieve this, we will read the requirements related documents very thoroughly.
• In case the requirements document is not available with us, then we will use other available references like the previous version of the application or wire-frames or screenshots.

Step-2# After developing an understanding of the requirements, we will prepare an exhaustive list of the areas to be tested for the AUT.The focus in this step is to identify “What” to test. Thus the outcome of this step is a list of test scenarios.

Step-3# After we are ready with the test scenarios, our focus shifts on “How” to test them. This phase involves writing detailed steps about how to test a particular feature, what data to enter (test data) and what is the expected outcome.

With all this done we are ready for testing.

Q-2# What are the key elements in a bug report?

Ans# An ideal bug report should contain the following key points.

• A unique ID.
• Defect description – a short description of the bug.
• Steps to reproduce – include the detailed test steps to emulate the issue. We should also provide the test data and the time of its occurrence.
• Environment – add any system settings that could help in reproducing the issue.
• Module/section of the application in which issue has occurred.
• Severity.
• Screenshots.
• Responsible QA – This person is a point of contact in case you want to follow-up regarding this issue.

Q-3# How will you overcome the challenges due to unavailability of proper documentation for testing?

Ans# If the standard documents like System Requirement Specification or Feature Description Document are not available then QAs may have to rely on the following references if available.