1. Tell me about the most impressive BUG you encountered in your testing work?
Answer: When I added XX information to the XX project, I encountered such an impressive BUG. I filled in the relevant information, but one column was empty. If I clicked cancel, it would show that the addition was successful. Afterwards, we located the BUG and found that the front-end call interface was wrong, and the newly-added interface on the back-end was not verified, so it returned the new addition success.
Afterwards, our front-end calls the new interface again, and the back-end re-modifies the verification logic of the new interface, and the repair is successful.
Analysis: When we encounter such a question, we have to figure out the answer the interviewer wants.
(1) Need to answer the BUG
(2) Locate the BUG problem
(3) How to fix the BUG (bonus item)
2. What is the key to test case design work?
Answer: We have a deep understanding of the needs of the project, and formulate effective strategies to deal with each module and each function point.
Analysis: To find the core of the test case is to fully cover the project requirements (close to full coverage)
3. Windows 10 copy and paste test case writing?
Answer: The test is considered from various perspectives:
Interface test (UI, text, icon, size, etc.), function test (whether copy and paste is valid, etc.), performance (time, size, etc.), compatibility (windows version, architecture, etc.), security (file missing, etc.), etc.
Analysis: Directly expand the content of the answer, and consider the writing of test cases from many aspects.
4. Where is your greatest interest in testing? Why?
A: I am curious and challenging about the unknown.
I think finding a bug will make me excited, and being able to improve a project and make the project go without problems is also a place where I am very happy.
Analysis: Start with character more, you can freely add your own opinions, and talk more in a good direction.
5. What to do when the developer says this is not a bug?
Answer: First of all, you must submit the evidence you have tested to the development engineer, and actively communicate with the development engineer. If you encounter a bug that cannot be reproduced, you must use packet capture, screenshots, etc. to save the evidence. If there is no result after communicating with the development engineer, let the product manager determine whether it is a bug.
Analysis:
1. Communicate with developers
2. Reasons for keeping bugs well
3. If they can’t be solved, go to the product manager to solve many things.
Picture
6. When is the best time to intervene in testing?
Answer: It is best to intervene from the project requirements stage. The earlier we intervene in testing, the fewer problems we encounter. We start writing plans and solutions at the requirements stage, and then write test cases according to the plans and plans. The more we can Find bugs in time.
Analysis: The sooner the better, and write corresponding documents.
7. Tell me about your development plan after the test?
Answer: 1. I need to be familiar with functional testing, and then constantly improve myself, so that I can independently be responsible for the overall functional testing of a project.
2. Learn automated testing, be able to automate testing of projects, and save time for regression testing.
3. Learn to lead a test team, divide labor, be able to solve the test work of a large project...etc.
Analysis: The key point is to have a clear mind, to be clear about what you need to learn, and what to learn at each stage.
8. Why did you enter the testing industry?
Answer: Because the testing industry is a new industry, the proportion of testing in the Internet industry is getting higher and higher, and it requires a variety of skills, such as concentration, patience, communication skills with people, and programming ability, which is more important than development. Comprehensiveness.
Analysis: Play according to your own ideas. In the front, you will talk about the prospects of this industry, and in the back, you will talk about your own personality or the various abilities required for this test.
9. How can we fully test every point?
Answer: At the initial stage of the project, the testing work must be started. The test plan must be multi-faceted and comprehensively consider the testing strategy and the writing of test cases.
Analysis: Get involved in project testing early, and the documentation should be written comprehensively.
10. What test methods do you use?
Answer: According to the different functions of the module subdivision, different testing methods are used, mainly black box and white box, and then when we test the black box, we design test cases according to different functions and use different design methods (division of equivalence classes) , orthogonal, etc.), to ensure the coverage of the test.
Analysis: Most of the tests are black-box tests, so test cases are generally included, and there are several major design methods in the test cases that should be paid attention to.
11. What do test cases usually include?
Answer: Use case number, use case name, priority, test steps, test data, expected results, final results, etc.
Analysis: This is defined according to the company's project, and generally only these few pieces are enough.
12. How to locate front-end and back-end bugs?
Answer: There are several ways
1. Simply look at the request response location
2. By querying the log, if there is no content in the log, it means that there is a front-end problem, and the back-end is reversed.
3. Use the packet capture tool to locate the interface and find data.
Analysis: The interviewer asks this question mainly to see how you solve a problem. This kind of situation is rarely encountered in actual work, and it is very easy to locate it.
13. The account registration is successful, but the login fails. How to locate the bug?
Answer: Call the login interface to see if the correct account is entered successfully. If successful, there is no problem with the login interface. Then the registration interface, the registration data may not be stored in the database, or there are problems with the registration interface verification and so on. Just submit a bug.
Analysis: Simply test how to locate a bug for a function point, and just express your own ideas.
14. What is software quality?
Answer: Software products can meet the needs of users, and the functions can be realized.
Analysis: Meeting the needs and functions of users is the most important.
15. How to design test cases?
Answer: It is divided into black box testing and white box testing
Black box testing: equivalence class division method, boundary value analysis method, causal diagram analysis method, orthogonal experiment method, decision table method, scenario method, function graph method, error guessing method
White box testing: logic coverage, loop coverage, basic path coverage
Analysis: Just answer these points normally.
16. Can all bugs be fixed, and do they all need to be fixed?
Answer: In theory, all bugs can be fixed, but some bugs do not need to be fixed. There are some subtleties that do not affect the running of the program. Functional bugs can be left unrepaired. Large bugs and important bugs should be repaired first, and then repaired at the end.
Analysis: The focus is to fix big bugs first, and then fix small bugs.
17. Is it possible to fully test the software?
Answer: Impossible. The testing work is mainly to find bugs, but there is no guarantee that there are no bugs, because in the testing process, the amount of test data required for a complete test is extremely large, and a lot of manpower and material resources are consumed. So we will see that different software has internal testing and public testing, and many people are required to complete this testing.
Analysis: Nothing is perfect, neither is testing.
18. What to do if the requirement document is found to be incomplete during the test?
Answer: Communicate with the product manager in a timely manner, find out the imperfections, and then submit them to the product manager accurately, so as to be convincing.
Analysis: The core is to mark out the imperfections.
19. After developing and fixing bugs, if it is guaranteed that other functions will not be affected?
Answer: Design test cases with the method of adding scenarios, and conduct scenario tests and business tests on some functions.
Analysis: Additional tests are performed in various ways.
20. When is the functional test?
Answer: From the beginning of the test intervention, functional testing can be carried out. Functional testing is the core of software testing, ensuring that all functions are run within a period of time and bugs are found.
Analysis: Functional testing is the core of the entire software testing, and it is the first to intervene.
Typing is not easy, if this article is helpful to you, please like, bookmark, follow and give the author an encouragement. It is also convenient for you to quickly find the next time