Software QA interview Question Summary

Interview Questions for QA Tester

Practical QA Interview Questions on TestDirector, ClearQuest, QTP, Sample Test Plan,

Sample Test Case, Sample Resume, Backend Testing..

Interview Questions for QA Tester

(Software Tester)

Author: Prakash Nepal

January 25,2007

(I came to know that many institutions and organizations are using this materials without

questions were asked to.These questions and scenarios are based on practical

experience. These were asked during my several interviews. Therefore, a person who is

looking for a QA job (Quality Assurance job) can greatly benefit from this. If you are the

first time job seeker as a QA person, then it can help you even better. As a consultant (or

contractor), I moved to different companies in various locations in the United States.

Consulting job or contracting job is such a job where an individual takes (or has to take)

a job anywhere in the United States and normally, it is for a short period of time, for

example, 3 months to several years. Some companies allow a contractor to work only for

15 months (It is their policy) and the consultant has to leave the company no matter what.

Some companies allow the contractors as long as they want. Therefore, it really depends

my experience. When we come out the door, we regret. If you cannot remember these by

heart, trust me, it may not work. Therefore, let’s not regret.

HERE ARE THE QUESTIONS:



1. Can you tell me about yourself?



Answer: In my 2 years QA experience, I have been working on various system platforms

and operating systems like Windows 2003, Windows XP and UNIX.

I have tested applications developed in Java, C++, Visual Basic and so on. I have tested

Web-based applications as well as client server applications.

Testing and UAT (User Acceptance Testing) Testing. I have participated in Load Testing

and Stress Testing.

I have written defects as they are found using ClearQuest and TestDirector. Once the

defects were fixed, retested them and if the passed, closed them. If the defects were not

fixed, then reopened them. I have also attended the defect assessment meetings as

necessary.

In the meantime, a continuous interaction with developers was necessary.

This is pretty much what I have been doing as a QA person.



2. What did you do in your last project?

meetings for requirement reviews and provided feedback to the Business Analysts.

Mostly, I was in the backend testing, which required writing SQL queries directly to the

database.

Besides these, I wrote defects using ClearQuest. Once the defects were fixed, retested

them and if the passed, closed them. If the defects were not fixed, then reopened them.



3. Have you written Test Plan? What is a Test Plan? What does it include?

Answer: Yes.



What is a Test Plan?

Answer: A Test Plan is a document that describes the scope, approach, resources, and

schedule of intended testing activities. It identifies test items, the features to be tested, the

testing tasks and who will do each task (roles and responsibilities) and any risks and its

solutions.

What does it include?

section.



4. Have you written Test Cases? Answer: Yes.

What is a Test Case? What does it include?



Answer: A Test Case is a document that describes step-by-step process how to test the

application. A Test Case includes Test Case ID, Steps Description, Expected Output,

Actual Output, Pass/Fail, and Remarks. (Remember, this is NOT a part of Test Plan. It is

a separate document written using Excel. In some companies, they use Rational

TestManager or TestDirector. But for companies, who do not have these tools, use Excel



Answer: Yes. I have used TestDirector (now called QualityCenter) and Rational

TestManager to write Test Cases. However, in most of the companies, I used Excel sheet.

Click here to see a sample Test Case.



How many Test Cases did you write in your last project?

Answer: I wrote about 1100 Test Cases in my last project. (The reasonable number of

Test Cases varies from 500 to thousands. The number 1100 test cases can be completed

in 6-month project duration).



document at least).



5. Did you have a situation where you did not have any documents (no requirement

document, no Use Cases, or no Design Document) and you had to write the Test

Cases? How did you write the Test Cases in this situation?



Answer: Yes. I have been to that kind of scenarios several times. There were companies

scenario and functionalities with the Business Analysts or developer. On the basis of that

discussion, I prepared a document in consultation with Business Analysts and Developers

and then started writing Plans and Test Cases.



6. What you worked with Use Cases before?



Answer: Yes. I have written Test Cases using Use Cases.

a particular functionality. Click here to see how a Use Case looks like.



7. What is SDLC (Software Development Life Cycle)?



Answer: SDLC (Software Development Life Cycle) is the process of developing software

through business needs, analysis, design, implementation and maintenance. Software has

to go through various phases before it is born which are as follows:

a Pizza Hut may need software to sell pizza. An Indian store may need software to sell its

newly arrived movies or grocery. The owner of the company feels that he needs software

that would help him in tracking his expenses and income as well as enhance the selling

process. This is how the concept is generated. The owner will specifically tell the

software company what kind of software he would need. In other words, he will specify

his requirements.

(ii) Requirements analysis – After the owner (user) knows his requirements, then it is

given to a software team (company) who will analyze the requirement and prepare

requirement document that will explain every functionality that are needed by the owner.

The requirement document will be the main document for developers, testers and

code (program) for their modules. On the other hand, the testers in the QA (Quality

Assurance) Department start writing Test Plans (one module=1 test plan), test cases and

get ready for testing.

(iv) Testing: Once the code (programs) are ready, they are compiled together and to

make a build. This build is now tested by the software testers (QA Testers)

(v) Production: After testing, the application (software) goes into production (meaning, it

will be handed over to the owner).

business grows and this software does not meet the demand or for some reason, the he

does not need the software. That’s the end of it.



8. What is Business Requirement Document (BRD)?



Answer: It is a document that describes the details of the application functionalities

which is required by the user. This document is written by the Business Analysts.

Business Requirement Document and Business Design Document can be lumped together

to make only one Business Requirement Document.



10. What is a Module?



Answer: A ‘Module’ is a software component that has a specific task. It can be a ‘link’,

which can go inside to its component detail. (This is NOT a very common question for the

interview. This is just for your knowledge, if you don’t know what a module is.)



11. What is walk-through meeting?

through meeting.



12. What is a Use Case and what does it include?



Answer: A Use Case is a document that describes the user action and system response for

a particular functionality. It includes cover page, Revision History, Table of Contents,

Flow of Events (normal flow and alternative flow), Exceptions, Special Requirements,

Pre-conditions and Post-conditions. Click here to see how a Use Case looks like.



13. What is Build?