（转）Interview Questions for QA Tester (Software Tester)

 **原文由王宇老师提供，感谢王宇大大

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 who visited this website and wanted to share.

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.

HERE ARE THE QUESTIONS:

1. Can you tell me about yourself?

Answer: In my QA career, I have been working on various system platforms and operating systems like Windows 95, Windows 2000, 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, Business 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 DB2, wrote SQL queries to retrieve data from the database. As far as different types of testing are concerned, I have performed Smoke Testing, Functional Testing, Backend 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 theypassed, 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.

QA（quality assurance质量保证）

       这些问题和回答完全基于我六年作为QA测试人员的工作经历中参加的面试。在一部分章节中，包括了在一些面试中应试者被公司问到的问题，他们访问这个网站并且希望分享这些问题。

       假如你参加一个面试，你必须在心中了解这些问题和回答，当你回答的时候必须非常的流利。在镜子前面对着你自己练习，要清晰大声。在大多数时间，当我们读这些个问题，我们感觉良好，但是事实是当面试的时候，即使我们感觉掌握了那个知识也不能很好的表达出来。这听起来或许有点粗鲁，但这是我的经验。当我们面试出来的时候，我们后悔了。

下面是这些问题（Q&A）

Q：你能向我介绍一下你自己吗

A:   在我的测试生涯，我曾经在各种系统平台上工作过，也在像win95、win2000、XP、UNIX这样的操作系统上工作过。我测试过使用Java编写的应用程序，也测试过C++、VB等。我测试过B/S结构的程序也测试过C/S结构的程序。

       作用一名测试人员，我编写测试计划、测试用例，参加有业务分析师、项目经理、业务经理和测试组长出席的预排会议。我还参加了需求评审会议，给产品分析师提供回应。我在不同的数据库像oracle和db2上工作过，编写SQL查询语句从数据库中检索数据。

       就关心的各种测试类型而言，我执行过冒烟测试、后台测试、黑盒测试、集成测试、回归测试和用户验收测试。我参加过负载测试和压力测试。

       我编写过缺陷(报告)，这些缺陷是用ClearQuest和TestDirector发现的。一旦这些缺陷被修复了，对它们进行返测，假如它们通过关闭掉缺陷，反之重新打开缺陷。有必要的话我也会参加缺陷评估会议。在这期间，同开发人员之间持续不断的互动式非常必要的。

       这就是我作为一个测试曾经做过的工作。

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 they passed, closed them. If the defects were not fixed, then reopened them.

Q：在过去的一个项目中你做了哪些

A：在我最近的一个项目中，程序是在java平台上开发基于web的应用程序。作为一个测试人员，我根据需求文档和使用用例来编写测试计划。我执行了冒烟测试、功能测试、后台测试、黑盒测试、集成测试、回归测试和用户验收测试。我参加了负载测试和压力测试。我参加了好几次需求审查的预排会议，给业务分析师提供了很多反馈。在绝大多数情况下我执行后台测试，则需要直接对数据库操作编写SQL查询语句。除了这些，我还用ClearQuest编写缺陷报告。一旦缺陷被修复，对他们进行返测，加入通过关闭缺陷，不通过则重新打开缺陷。

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. 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.

Q：你编写过测试计划吗？什么是测试计划，包括哪些

A：编写过，

Q：什么是测试计划

A：测试计划是一个描述测试范围、方法、资源以及要开展的测试活动的计划的文件。它确定将要被测试的测试项目、特征，测试任务以及谁将要做这些任务（角色和责任），任何风险及解决办法。

Q：它包括什么

A：一个测试计划包括标题、修订历史、目录、简介、范围、方法、概述、测试策略，软件和硬件资源、问题、风险、设想和结束部分。

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 the example below, it is in the Excel sheet)

Q：你编写过测试用例吗

A：是的

Q：什么是测试用例，包括哪些

A：测试用例是一个描述怎样测试应用程序每步过程的文件。一个测试用例包括：测试用例编号、步骤描述、预期输出、实际输出、通过/失败、备注。

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. 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 varies 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).

 Q：你使用工具去编写测试用例吗

A：是的，我使用过TestDirector和Rational TestManager 区编写测试用例。然而，在大多数的公司，我使用excel表单。

Q:在你上一个项目中你编写了多少条测试用例

A：在我上个项目中我编写了将近1100条测试用例。

Q:为了编写测试用例你参考了哪些文件

A：需求文档（注意：也可能是用例或者设计文档，每个公司都不一样。在一些公司，他们使用用例。在一些公司他们使用需求文档，一些使用设计文档。然而，在实际的场景中，大多数的公司都至少有需求文档）。

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.

Q:你是否有一种情况你什么文档都没有（没有需求文档、没有用例、没有设计文档）但是却不得不编写测试用例？在这种情况下你怎么编写测试用例

A：是的，我遇到这种场景好几次了。有一些公司这些文件一个都没有。在这种情况下，我必须和业务分析师和开发方讨论程序的场景和功能。在这个讨论的基础上，我准备文件以及开始编写测试计划和测试用例。

6. Have 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. See how a Use Case looks like.

 Q:你曾经在工作中使用过用例文档吗？

A：是的，我以前编写测试用例的时候用到过用例文档。

Q:你能告诉我用例文档是什么吗

A：用例是一个描述特定功能下用户行为和系统回应的文档。

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 may 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 demands or for some reason, then he does not need the software. That’s the end of it.

Q:什么是SDLC（软件开发生命周期）

A：SDLC（软件开发生命周期）是指通过业务需求、分析、设计、执行和维护来开发软件的流程。软件在诞生之前补习经历以下阶段：

（ii）生成概念（提出需求）-概念来自软件的使用者。例如，一个披萨屋可能需要软件来销售披萨。一个印度商店可能需要软件去销售它最新到货的电影或者杂货。公司的所有者可能会感觉他不仅需要软件区帮助他记录收支也需要软件来增强销售过程。概念就是这样产生的。公司所有者会明确的告诉软件公司他需要什么样的软件。换句话说，他已经明确了它的需求。

（ii）需求分析-当用户知道了它的需求之后，需求被交给了软件团队分析需求、准备需求文档，需求文档会解释每一个用户需要的功能点。需求文档（需求规格说明书）会是开发人员、测试人员、数据库管理员（引用）的主要文件。换句话说，这是所有人参考的主要文件。在测试计划编写之后，其他详细的文档也许会被也需要到。例如设计架构，设计架构是对于硬件、软件、人力或者数据资源的设计蓝图，伴随着必要的说明书。

（iii）开发：在（产生）详细的需求文档之后（有一些公司使用设计文档代替需求文档），开发人员开始为他们的模块编写代码。另一方面，软件测试部门的特斯人员开始编写测试计划（一个模块=一个测试计划）、测试用例并且准备测试。

（iv）测试：一旦代码写好，他们被编译在一起，组成一个版本。这个版本将会被软件测试人员测试。

（v）产品：测试之后，应用程序变成产品（意味着他将被移交给使用者处理）。

（vi）结束：某一天，软件的所有者也要告别这个软件因为业务在正常，这个软件不在适应需求，或者因为某种原因他不在需要这个软件。这是软件的结束。

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.

Q:什么是业务需求文档（BRD）

A：这是一个描述应用程序功能细节的文件，功能由用户提出需求。这个文档是由业务分析师编写。

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.

 Q:什么是业务设计文档

A：设计文档是一个详细描述应用程序功能的文档。这个文档比业务需求文档有更详细的细节。这在软件开发生命周期中是决定性的一步。有时候需求文档和设计文档可以集中在一起组成一个单独的需求文档。

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.)

 Q:什么是一个模块

A：一个模块是一个有特定任务软件组件。它可能是一个链接，可以直接访问到组件的细节。

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 feedback(反馈) and various point of views are expressed. This is walk-through meeting.

 Q：什么是预排会议（翻译的不准确☺）

A：一旦业务分析师完成了需求文档，他们会召开一个会议阐明功能是如何运作的、设计的程序内部过程是怎么样的，以及其他一些细节。业务分析师在高层次解释了程序将要建立的功能。会议的