软件测试英文面试题汇总

 

1. What types of documents would you need for QA, QC, and Testing?

我们需要软件规格说明书，概要设计，详细设计，我们根据这些文档编写测试计划，测试方案，测试用例，展开测试工作

2. What did you include in a test plan?

Test plan is a document which gives the overall direction to the testing. Test plans and their formats vary from company to company. It might contain : Test Scope, Test objective, Assumptions, Risk Analysis ,Test Design, Roles & Responsibilities, Schedule & Resources, Test Data Management, Test environment, Communication Approach, Test Tools.

一、前言（目的、主要内容，参考资料，本说明书的术语关键词的解释等）

二 测试内容 列出单个模块测试、系统整体测试中的每一项测试的内容、目的及其名称、标识符、进度安排和测试条件等

三 测试设计说明，包括被测项和被测特性、测试所用的方法、测试准则等

四 测试用例说明，包括测试用例名称、输入（测试数据）、输出（预期结果）、环境
、工具等

五 人员分工

六 测试计划编写的要点

3. Describe any bug you remember.

一般来说，预期结果和实际输出不一致，这肯定是bug，当然也有一些GUI不美观，或者响应时间长等问题I will take an example of Yahoo mail. Login to yahoo.com and click on the compose button. Then it should navigate to Compose page. If it is not going to that page then it is a bug. 

4. What is the purpose of the testing?

The purpose of testing can be quality assurance, verification and validation, or reliability estimation. Testing can be used as a generic metric as well. Correctness testing and reliability testing are two major areas of testing. Software testing is a trade-off between budget, time and quality.

5. What do you like (not like) in this job?

It's very interesting, challenging by thinking about the application in the end user's perception. It is interesting that we are doing destructive work but in the long term it is a constructive work.

6. What is quality assurance?

Quality assurance is a system of management activities performed to ensure that a process, item, or service is of the type and quality needed by the user. It deals with creating management controls that cover planning, implementation, and review of data collection activities

7. What is the difference between QA and testing?

Testing’s primary contribution to quality is to identify problems that we wish we could have prevented in the first place.

The mission of QA is to prevent defects in the first place as well as to remove defects that do creep into the product. That requires processes beyond testing

Testing is only part of quality assurance activities

 

8. How do you scope, organize, and execute a test project?

9. What is the role of QA in a development project?

QA has to look over all the Possibilities like Assessment, Bug Fixes, Product Quality, Client Interaction and Overall Development of Imparting Tasks for Testers

10. What is the role of QA in a company that produces software?

Quality assurance personnel are responsible for validating project assumptions and ensuring the quality of phase deliverables

11. Define quality for me as you understand it

It is software that is reasonably bug-free and delivered on time and within the budget, meets the requirements and expectations and is maintainable. 

12. Describe to me the difference between validation and verification.

Verification: is done to ensure that it meets the specifications. 
Validation: is done to ensure that it meets the customer requirements.

Verification takes place before validation

13. Describe to me what you see as a process. Not a particular process, just the basics of having a process.

The sequence of activities, people, and systems involved in carrying out some business or achieving some desired result

14. Describe to me when you would consider employing a failure mode and effect analysis.

FMEA (Failure Mode and Effects Analysis) is a proactive tool, technique and quality method that enables the identification and prevention of process or product errors before they occur. 
 Failure modes and effects analysis (FMEA) is a disciplined approach used to identify possible failures of a product or service and then determine the frequency and impact of the failure

15. Describe to me the Software Development Life Cycle as you would define it.

It's a process of developing a software system in an organized, controlled, and predictable way. There are six Main stages of SDLC: 1)Requirement 2) Analysis:3) Design3) Coding 4) Testing 5) Maintenance

16. What are the properties of a good requirement?

Good Requirements are: - clear, complete, detailed, cohesive, attainable and testable.

17. How do you differentiate the roles of Quality Assurance Manager and Project Manager?

Quality Assurance Manager is a part of the whole project or process who responsibility is to ensure that a certain protocol laid down by the Government as well as the clients are adhered to. He has to make sure that quality of the product or service is not compromised and high standard is maintained.

Project Manager on the other hand is a manager who has to manage all the activities of the whole project. In most cases Project Manager is above the Quality Assurance manager wherein the latter reports to the former.

18. Tell me about any quality efforts you have overseen or implemented. Describe some of the challenges you faced and how you overcame them.

For a tester foremost quality needed is that of clear & effective communication to every strata of the organization. I would say in each job we get to learn & hone this quality better & better.

Challenge which every tester faces some or the other time is that - the bug which he/she has found is not reproducible in the production environment & then it's a hard task to convince the development team. My suggestion is - (1) check the configuration of testing env & development environment. both should be replica of each other. (2) take snap shot of each step. (3) write down in detail all steps.

19. How do you deal with environments that are hostile to quality change efforts?

20. In general, how do you see automation fitting into the overall process of testing?

Automation Testing or Manual testing is dependent on certain factors like Requirements, Time of the project, Bud jet etc, If the Project is small and does not involve any repetitive tasks then it is best to choose manual testing. If the project has many builds released for every few days then it is difficult to check all the aspects of the application. Automation Testing Speeds up the testing process. We can create test Scripts that checks all aspects of the application and then we can run these tests on each new build. Benefits of Automated Testing:- Reliable, Repeatable, Fast, Programmable, Comprehensive, Reusable.

21. How do you promote the concept of phase containment and defect prevention?

Phase Containment is incorporating QA into all the phases of SDLC. It results in Defect Prevention. If QA team performs Requirements Review, Design Review and Code Review, defects would be few when actual application is tested. That means we have prevented many defects by performing reviews at each stage of SDLC.

22. If you come onboard, give me a general idea of what your first overall tasks will be as far as starting a quality effort.

The first tasks would be going through the system requirement documents of a application, going through the test strategy, test plan and writing the test cases and scenarios…

23. What kinds of testing have you done?

Functional testing, regression testing, database testing, compatibility testing, beta testing, etc..

24. Have you ever created a test plan?

I have never created any test plan. I developed and executed test cases. But I was involved/ participated actively with my Team Leader while creating Test Plans.

25. Have you ever written test cases or did you just execute those written by others?

I have written my own test cases and executed those written by others. 

26. What did your base your test cases?

The base of any test case is the Requirements documents and specification documents. Understanding the Application properly one can write good test cases, which are used to test the application properly.

27. How do you determine what to test?

The duties of the software Tester is to go through the requirements documents and functional specification and based on those documents one should focus on writing test cases, which covers all the functionality to be tested. The tester should carry out all these procedures at the time of application under development. Once the build is ready for testing, we know what to test and how to proceed for the testing. Make sure, main functionality is tested first, so that all other testers can be ready for testing their modules/functionality.

28. How do you decide when you have ‘tested enough?’

This is usually not a difficult decision. When all critical, serious and blocking issues have been fixed we have to test until the product is shipped and even after. The testing cycle is an endless process. Only the type of testing might vary from one stage to another in the development cycle of the product.

29. How do you test if you have minimal or no documentation about the product?

In this situation i will try to test the application with the perception of end user. And I use my(or someones) previous experiences. Here we are not prepare any formal test plans and test case documents, most of the time we perform ad-hoc on this type of applications.

30. Describe me to the basic elements you put in a defect report?

Contents of defect are: Defect ID, Summary, Description (environments, steps to reproduce, Expected values, Actual outcome), Status, Severity, Priority, Reproducible (y/n), Detected by, Detected on, Module, Build/version id, Test Case ID, Attachments (screen shots or docs).

31. How do you perform regression testing?

Regression Testing is carried out both manually and automation. The automatic tools are mainly used for the Regression Testing as this is mainly focused repeatedly testing the same application for the changes the application gone through for the new functionality, after fixing the previous bugs, any new changes in the design etc. The regression testing involves executing the test cases, which we ran for finding the defects. Whenever any change takes place in the Application we should make sure, the previous functionality is still available without any break. For this reason one should do the regression testing on the application by running/executing the previously written test cases.

32. At what stage of the life cycle does testing begin in your opinion?

Testing is a continuous process and it starts as and when the requirement for the project /product begins to be framed. 
Requirements phase: testing is done to check whether the project/product details are reflecting clients ideas or giving an idea of complete project from the clients perspective (as he wished to be) or not.

 

33. How do you analyze your test results? What metrics do you try to provide?

After the execution test cases on the corresponding build or version we get the results.
Before track down them into the bug tracking tool we have to analyze them to assign the severity. when we assign the severity, try to analyze the problem from the perception of the end user. from the above u can know how severe the problem is .
Defect density: total no of defects reported
during testing/size of project
test effectiveness: t/(t+uat)
where t:total no of defect recorded during testing
and Uat : total no of defect recorded during use acceptance testing
Defect removal efficiency(DRE): (total no of defect removed / total no of defect injected)*100

 

34. Realizing you won’t be able to test everything - how do you decide what to test first?

when time is less and when requirements are given as a professional test engineer I would prioritize the features then go ahead and test the critical and major features, if time permits I would test the minor ones

 

35. Where do you get your expected results?

We get expected results from the SRS and Functional Design Documents. 
If there is no clear documentation we prepared expected results from the  
1. Previous similar products. 
2. by communicating with the developers 
3. by common sense.

 

36. If automating - what is your process for determining what to automate and in what order?

Which test case to automate: 
1: test cases that need to run for every built. (also called sanity testing) 
2: test that uses multiple set of data values for same action (called data driven testing). 
3: identical test that need to be executed using different browser. 
4: mission critical pages or transaction with pages that won’t change is short term. 
Generally speaking more repeated the execution better the condidate for automation. 

If you using Automation, then Automation process is 
1.Recording Script 
2.Writing Script 
3.Executing Script 
4.Editing Script 
5.Analysing Testing Result

 

37. In the past, I have been asked to verbally start mapping out a test plan for a common situation, such as an ATM. The interviewer might say, “Just thinking out loud, if you were tasked to test an ATM, what items might you test plan include?” These type questions are not meant to be answered conclusively, but it is a good way for the interviewer to see how you approach the task.

In the past, I have been asked to verbally start mapping out a test plan for a common situation, such as an ATM. The interviewer might say, “Just thinking out loud, if you were tasked to test an ATM, what items might you test plan include?” These type questions are not meant to be answered conclusively, but it is a good way for the interviewer to see how you approach the task.

 

38. If you’re given a program that will average student grades, what kinds of inputs would you use?

 

39. Tell me about the best bug you ever found.

There is a functionality in our application i.e when an user submits a request to reported manager, that request should be displayed in the tasks inbox of the reporting manager. Whenever Manager log in into the application, after finding the task in the task inbox, he will approve it. But the application was behaving in entirely different manner i.e instead of going the request to reporting manager, the request was going to his (who created the request) task inbox.

It is a very typical bug, here we can't figure out the problem, why the data flow is effecting? Here we can't say this problem is occurring due to server problems, coding problems or database problems.

 

40. What made you pick testing over another career?

 Testing is one aspect which is very important in the Software Development Life Cycle (SDLC). I like to be part of the team which is responsible for the quality of the application being delivered. Also, QA has broad opportunities and large scope for learning various technologies. And of course it has lot more opportunities than the Development.

41. What is the exact difference between Integration & System testing, give me examples with your project.

Integration testing starts after completing of unit testing. It validates the interaction between grouped components. It identifies the bugs which cannot be identified at individual testing of component, sub module, module.

System testing starts after completing of integration testing. Performance testing, load testing, stress testing, compatibility testing, security testing etc come under System testing.

42. How did you go about testing a project?

From a functional testing perspective, I do the following:
Test planning:  Gain as much domain knowledge as possible; review and learn about the product through requirements, work-flows, wireframes, system architecture diagrams, and any other available information.
Test development: Create test cases based on the knowledge gained during test planning; map test cases to requirements; prioritize test cases.
Test execution: Execute the test cases over the necessary number of test cycles until the quality of the product satisfies the company's exit criteria.
Test reporting: Discover and report defects giving them appropriate weight of severity and priority.
Test result analysis: Analyze the test results in order to better understand the quality of the product as well as the quality of our test effort. 
Defect retesting: Retest fixes sent back from the development team.
Regression testing: Test vulnerable functionalities that are impacted by code changes.   
Test closure: Test through to completion and report results to key stakeholders. 

43. When should testing start in a project? Why?

Testing starts when the SRS are ready. Tester starts writing test cases where as developer starts coding for the requirements of a particular module

44. How do you go about testing a web application?

It’s clear that for testing any application, one should be clear about the requirements and specification documents. For testing Web application, the tester should know, what the web application deals with. For Testing Web application, the test cases written should be in two different types, 1) The Test cases related to the Look and Feel of the Web pages and navigation and 2) The test cases related to the functionality of the web application. Make sure, whether the web application is connected to the Database for the inputs. Write Test cases based on the Database and write test cases for the backend testing as well if there is any database. The web application should be tested for the server response time for displaying the web pages, Make sure the web pages under load as well. For load testing, the tools are very much useful for simulating the many users.

45. Difference between Black & White box testing

Black Box Testing: Testing input/output without knowledge and/or regard of the internal code. Commonly designed /executed by test team.  
White (Glass) Box Testing: Testing input/output with full knowledge and/or regard of the internal code. Commonly designed /executed by Developers. 

46. What is Configuration management? Tools used?

Software configuration management (SCM) is the control, and the recording that are made to the software and documentation throughout the software development cycle (SDLC). SCM covers the tools and processes used to control, coordinate and track code, requirements, documentation, problems, change requests, designs, tools, compilers, libraries, patches and changes made to them, and to keep track of who males the changes.  

Tools include Rational Clear Case, Doors, PVCS, CVS and many others. 

47. What do you plan to become after say 2-5yrs (Ex: QA Manager, Why?)

48. Would you like to work in a team or alone, why?

I would like to work in a team. Because the process of software development like a relay race where many runners have to contribute in their respective laps. It is important because the complexity of work and degree of efforts required is beyond level of an individual.

49. Give me 5 strong & weak points of yours

 

50. Why do you want to join our company?

 

51. When should testing be stopped?

It is very difficult to determine when to stop testing. Because it depends upon the some of the testing to be follow:

1. When Alfa and beta testing gets over.

2. Defect rate follows down below the criteria

3. When the test manger is confident when the application will perform as expected in the production environment

4. Bug rate falls down below the criteria.

5. Test budget 

6. Deadlines to be released the project

52. What sort of things would you put down in a bug report?(重复)
53. Who in the company is responsible for Quality?

In the company everyone involved in the software development of software is responsible for the software quality. QA AND QC team

54. Who defines quality?

Customer defines coz If u archive customer's specification that is what the quality.

 

55. What is an equivalence class?
56. Is a “A fast database retrieval rate” a testable requirement?
57. Should we test every possible combination/scenario for a program?
58. What criteria do you use when determining when to automate a test or leave it manual?
59. When do you start developing your automation tests?
60. Discuss what test metrics you feel are important to publish an organization?
61. In case anybody cares, here are the questions that I will be asking:
62. Describe the role that QA plays in the software lifecycle.
63. What should Development require of QA?
64. What should QA require of Development?
65. How would you define a “bug?”
66. Give me an example of the best and worst experiences you’ve had with QA.
67. How does unit testing play a role in the development/software lifecycle?
68. Explain some techniques for developing software components with respect to testability.
69. Describe a past experience with implementing a test harness in the development of software.
70. Have you ever worked with QA in developing test tools? Explain the participation Development should have with QA in leveraging such test tools for QA use.
71. Give me some examples of how you have participated in Integration Testing.
72. How would you describe the involvement you have had with the bug-fix cycle between Development and QA?
73. What is unit testing?
74. Describe your personal software development process.
75. How do you know when your code has met specifications?
76. How do you know your code has met specifications when there are no specifications?
77. Describe your experiences with code analyzers.
78. How do you feel about cyclomatic complexity?
79. Who should test your code?
80. How do you survive chaos?
81. What processes/methodologies are you familiar with?
82. What type of documents would you need for QA/QC/Testing?
83. How can you use technology to solve problem?
84. What type of metrics would you use?
85. How to find that tools work well with your existing system?
86. What automated tools are you familiar with?
87. How well you work with a team?
88. How would you ensure 100% coverage of testing?
89. How would you build a test team?
90. What problem you have right now or in the past? How you solved it?
91. What will you do during the first day of job?
92. What would you like to do five years from now?
93. Tell me about the worst boss you’ve ever had.
94. What are your greatest weaknesses?
95. What are your strengths?
96. What is a successful product?
97. What do you like about Windows?
98. What is good code?
99. Who is Kent Beck, Dr Grace Hopper, Dennis Ritchie?
100. What are basic, core, practises for a QA specialist?
101. What do you like about QA?
102. What has not worked well in your previous QA experience and what would you change?
103. How you will begin to improve the QA process?
104. What is the difference between QA and QC?
105. What is UML and how to use it for testing?
106. What is CMM and CMMI? What is the difference?
107. What do you like about computers?
108. Do you have a favourite QA book? More than one? Which ones? And why.
109. What is the responsibility of programmers vs QA?
110. What are the properties of a good requirement?
111. How to do test if we have minimal or no documentation about the product?
112. What are all the basic elements in a defect report?(重复)