[Test interview] offer harvester reappearance, software test actual combat scene interview questions (with answers)...


foreword

Software testing interview questions: https://www.bilibili.com/video/BV1Lq4y137aR/

Interview question: Have you ever captured a packet, why did you capture it, and how did you do it?

Answer:
In fact, we use the packet capture a lot in our work. Generally, we encounter problems during the test process. Sometimes we use packet capture to see the data interaction between the front end and the background. By analyzing this data, To locate whether it is a front-end problem or a background problem.

The main use is the fiddler tool. If you just want to grab web-side data, just set the proxy server on the browser, specify the proxy server as the local fiddler tool, and set the port: 8888. If you want to grab the mobile phone Package, first of all, you need to ensure that the mobile phone and the computer (the computer with fiddler installed) are on the same network. On the mobile phone, you must set the http proxy server as manual, then specify the server as the computer's ip address, and set the port to 8888

Exception, if you want to grab the https package, you may need to install the certificate on the computer, and also install the certificate on the mobile phone side, which is almost the same.

Interview question: Why do you need to capture packets? How to analyze it?

Answer:
The main reason is that when a bug occurs during the test, in order to locate and analyze the problem, we need to capture the data interaction process of the front-end and back-end, and analyze whether it is a front-end problem or a back-end problem by looking at the data.

If you analyze this piece:
1. First, check whether there is a problem with the request, whether there is an error in the requested interface url, whether there is an error in the parameter, if there is a problem with the url or the passed parameter, it is a front-end bug

2. If there is no problem with the request, check whether there is a problem with the data returned by the background. The status code starting with 5 is basically a background problem. If the status code is 200, and the response data is inconsistent with expectations, it is also a bug in the background, but it may be the database. The problem may also be a problem with the background code. Here, I usually check the data in the database. If there is no problem with the database, then I need to check the log file in the background. I will analyze it specifically to see what is wrong with the background code, and then put the log Screenshot of information information for development

3. There is no problem with the returned data, and there is no problem with the request parameter, u. It may be that there is a problem with the conversion of the front-end code, and that is the front-end bug.

Interview question: Given a requirement for you, how do you test it?

Answer:
The first point: First of all, I need to know the background of this requirement. This requires functions. I must at least know what this requirement is for, and what kind of solution is it.

The second point: clarify these, see what interactions this needs to have with other modules, whether it needs to be correlated and analyzed, whether it affects other modules, or whether data flows to other modules.

The third point: These are all clear, then I will look at the workload based on the familiar situation, which time to deliver, at this time I need to make a plan to tell the boss, if there is enough time, one person can handle it, then I can do it alone, if I can't do it, I will apply to the boss for manpower. In fact, the next step is almost the same, analyze the needs, try to review, and ensure the quality in the early stage, if there is no problem. Others are use case instantiation, execution, bug tracking, etc., and finally a report will be fine.

Basically what I do, the way I do it mainly depends on you understanding the needs thoroughly in the shortest time, making a plan, and starting the work.

Interview question: Give you a project, how do you carry out the work, please explain in detail, how did you do it?

The point of the interviewer's test: enter our company, give you a project, how do you do it, see if you have the ability to do projects independently

Answer:
The first point: first of all, I need to be familiar with the background of this project. I must at least know what this project is doing, and what kind of solution is it.

The second point: if these are clear, then we must be clear about the core modules and business of this project. We will give this module a priority, which core modules to test first, and which modules to build

The third point: According to the information just now, I will be familiar with this business, this business-related module, and the interaction before and after writing data, etc.

The fourth point: I am familiar with these, so I will look at the workload based on the familiar situation, and which time point will be delivered. At this point in time, I need to do a test plan. If the general requirements analysis is based on my experience, it will take about 2 days Yes, time for writing use cases, execution time, and bug fixing time. I will do a workload assessment. If there are other tests, I will send this plan to everyone, and let everyone review the plan and arrangement to see if the arrangement is reasonable.

Can you complete it in this planned time period, and give about 2 more days for the basic needs analysis, then you have to complete it in this time period. After completion, I will arrange for you to explain the needs, do demand reviews and need explanations, and spend more time in the early stage Point, the risk is less later, I mainly follow up the progress.

Fifth point: Then, next, everyone writes use cases according to the plan. After the use cases are completed at the time point, I will organize everyone to review them. I must control these two to reduce the risk of later testing. The previous analysis and use cases are in place, and subsequent execution If you don’t have too many problems with bugs, then everyone can implement it. I mainly follow up the progress. Every day, everyone’s bug resolution and test progress will be made into a daily report.

If there are problems that are not easy to solve, I will assist them. After the test is completed, I will collect everyone’s test data and make a test report. I will evaluate whether the test is risky. If not, send it to the development boss. , develop all, test all. Under this review, follow-up organization testers arrange to go online, which is basically what I do

Interview question: There is a problem with the returned data, how to troubleshoot the problem?

Answer:
This may require packet capture. First, capture the packet to see the data interaction between the front and backend, and confirm whether it is the front-end request to send. If there is a problem, there is a problem with the returned data. If there is a problem with the request, then mention the bug to the front end and let the front end fix it.

If there is no problem with the request, compare it with the interface document to see what is wrong with the returned data. Here you have to check the database first to see if there is a problem with the data in the database itself. If there is no problem with the database data, it may be Background code problem. At this time, you can check the log file in the background, and analyze the error information of the log file to find out what caused the problem.

Interview question: Sometimes the order is placed successfully and sometimes the order fails. What is the reason?

Answer:
For the success and failure of the order, capture the packets separately, compare the captured data twice, and analyze the reasons
1. If the sent requests are different, it must be a front-end problem.

2. If the returned data is different, the basic judgment is that there is a problem with the background code. At this time, you can check the log, check the database, and submit the information to the development process. It may also be that the network problem has not been sent out.

Interview question: How to grab the log when the APP crashes?

# adb logcat android studio logcat

Answer:
In this case, I must go to the log on the mobile phone, analyze the crash log, and directly view the log through adb logcat.

According to the crash time period, search for the log of this time period, check whether there are Error, Exception, Crash, OOM, etc., analyze the log, and if you don’t understand, you can check the reason on Baidu, and then send it to the development for processing.

Interview question: In WeChat, if no one can see the information you sent in Moments, what is the reason?

Answer:
1. A deleted the information in that circle of friends
2. A blocked all friends to view his circle of friends
3. If it is not blocked, post a few more messages to see. It may be that there is a problem with the WeChat background, or that A’s WeChat account is abnormal, etc., but this is unlikely.

The following is the most complete software test engineer learning knowledge architecture system diagram in 2023 that I compiled

1. From entry to mastery of Python programming

Please add a picture description

2. Interface automation project actual combat

Please add a picture description

3. Actual Combat of Web Automation Project

Please add a picture description

4. Actual Combat of App Automation Project

Please add a picture description

5. Resume of first-tier manufacturers

Please add a picture description

6. Test and develop DevOps system

Please add a picture description

7. Commonly used automated testing tools

Please add a picture description

Eight, JMeter performance test

Please add a picture description

9. Summary (little surprise at the end)

Time never waits for anyone, only by grasping the present can you create your own future. Therefore, please be brave to chase your dreams and create your own wonderful life.

The most important thing in life is happiness and joy, and the most valuable thing is the pursuit and realization of yourself, so please bravely embrace the challenges of life and never give up.

Grasp every opportunity and meet every challenge. Even in the face of difficulties and obstacles, you must firmly believe in your own ability and value, go forward bravely, and create your own brilliance.

Guess you like

Origin blog.csdn.net/shuang_waiwai/article/details/130345119