没有合适的资源?快使用搜索试试~ 我知道了~
首页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
citing the source. It is OK to use this material, but please mention the source where you
got from. It is a copyrighted material)
These questions and answers are totally based on the interview I attended during my 6
years of working experience as a QA Tester. In some sections, I have started including
the interview questions that were asked by companies to some of the candidates
whovisited this website and wanted to share. I have mentioned their names who the
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
on the company policy how long you will be working.
Finally, if you are attending an interview, you have to know these questions and answers
by heart, must be very fluent in answering these questions. Practice in front of the mirror,
loud and clear (talk to yourself). Most of the time, when we read the questions, we feel
good and feel comfortable, but the reality is, at the time of the interview, even though we
feel we have the knowledge, can’t express it well. It may sound a little rough, but this is
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.
As a QA person, I have written Test Plans, Test Cases, attended walkthrough meetings
with the Business Analysts, Project Managers, and QA Leads. I have attended
requirement review meetings and provided feedback to the Business Analysts. I have
worked in different databases like Oracle and SQLSever, wrote SQL queries to retrieve
data from the database. As far as different types of testing is concerned, I have performed
Smoke Testing, Functional Testing, Black Box Testing, Integration Testing, Regression
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?
Answer: In my last project, the application was a web-based application developed in
Java platform. As a QA Person, I wrote Test Plans from the requirement documents and
Use Cases. I performed Smoke Testing, Functional Testing, Backend Testing, Black Box
Testing, Integration Testing, Regression Testing and UAT (User Acceptance Testing). I
have participated in Load Testing and Stress Testing. I attended several walkthrough
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.
Click here to see how the Test Plan looks like.
What does it include?
Answer: A Test Plan includes Heading, Revision History, Table of Contents,
Introduction, Scope, Approach, Overview, different types of testing that will be carried
out, what software and hardware will be required, issues, risks, assumptions and sign off
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
sheet. In t he example below, it is in the Excel sheet)
Did you use any tools to write Test Cases?
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).
What document did you refer to write the Test Cases?
Answer: Requirement document. (NOTE: It can also be Use Cases, or Design Document.
It depends company to company. In some company, they use Use Cases. In some
companies, they use Requirement Documents and in companies, they use Design
Document. However, in practical scenario, most of the companies have requirement
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
where they had no documents at all. In that case, I had to discuss the application
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.
Can you tell me what a Use Case is?
Answer: A use case is a document that describes the user action and system response for
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:
(i)Generating a Concept – A concept comes from the users of the software. For example,
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
database administrators. In other words, this is the main document that will be referred
by everyone. After the requirement documents, other detailed documents many be needed.
For example, the architectural design which is a blueprint for the design with the
necessary specifications for the hardware, software, people and data resources.
(iii) Development: After the detailed requirement documents (some companies have
design documents instead of requirement documents), the developers start writing their
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).
(vi) End: And one day, the owner will have say bye to the software either because the
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.
9. What is Business Design Document?
Answer: It is the document that describes the application functionalities of the user in
detail. This document has the further details of the Business Requirement Document. This
is a very crucial step in Software Development Life Cycle (SDLC). Sometimes the
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?
Answer: Once the Business Analysts complete the requirement document, they call a
meeting to explain how the functionalities work, what the process is in the designed
application and other details. The Business Analysts explain the high level functionalities
of the application (software) that is going to the built. The participant members in the
meeting may provide feed back and various point of views are expressed. This is walk-
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?
Answer: When each of the different modules of software is prepared, the Configuration
剩余62页未读,继续阅读
anwwan
- 粉丝: 0
- 资源: 1
上传资源 快速赚钱
- 我的内容管理 收起
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
会员权益专享
最新资源
- c++校园超市商品信息管理系统课程设计说明书(含源代码) (2).pdf
- 建筑供配电系统相关课件.pptx
- 企业管理规章制度及管理模式.doc
- vb打开摄像头.doc
- 云计算-可信计算中认证协议改进方案.pdf
- [详细完整版]单片机编程4.ppt
- c语言常用算法.pdf
- c++经典程序代码大全.pdf
- 单片机数字时钟资料.doc
- 11项目管理前沿1.0.pptx
- 基于ssm的“魅力”繁峙宣传网站的设计与实现论文.doc
- 智慧交通综合解决方案.pptx
- 建筑防潮设计-PowerPointPresentati.pptx
- SPC统计过程控制程序.pptx
- SPC统计方法基础知识.pptx
- MW全能培训汽轮机调节保安系统PPT教学课件.pptx
资源上传下载、课程学习等过程中有任何疑问或建议,欢迎提出宝贵意见哦~我们会及时处理!
点击此处反馈
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功
评论0