Personal software testing interview process and routine sharing

Personally, I changed my career with zero foundation at the end of last year. I learned two to three thousand training fees. After learning, I was confused. I only knew that functional testing is to find problems. Other interfaces, performance, database , python basics, and virtual machine building websites have all realized course demonstrations. like that. I memorized the interview materials for nearly a week, and the resume was changed according to others. The trainer simply simulated a session. It was the first oppo online interview that night. At that time, I was extremely nervous, and my legs kept shaking. I was interviewed with a gas oven, and the questions were rare. Linux commands are all uncommon, and python can’t implement loops at all. I memorized cookies and sessions. . The next day I went to Chengdu for an on-site interview, during which there was also a telephone interview. The second interview scene question was completely failed, and the simple picture copy test, I only knew the shortcut keys and right-click copy and paste, and the third, fourth, and fifth rounds were all automated. Yes, I went to Tianfu 3rd Street and Yinhaixinzuo for two on-site interviews that day. The first written test was not good, and the most impressive question got stuck. The second machine test was abnormal, and the interviewer’s tricky database questions were not answered. , The performance was missed, the scene question was missed to test the safety, and the embarrassing batch ran away in desperation.

I failed in the interview for one day, and the group with a stable mentality, because the interviews were all companies that outsourced personnel contacted me, and the salary was all more than 10,000. I went back to my relatives’ house in the afternoon. I thought this would be the end of the day, but just after work, two project managers called me for an interview. They were both recruiting function-based test posts. The two interviewers mainly asked four questions. Self-introduction, test process, talk about previous projects, scenario questions, and the rest are whether to accept overtime, expected salary, I want to know. The first three big questions have been practiced many times, and there are no mistakes in the interview several times. The first interviewer's scene question is really lucky. The water cup test and the information sent by the training class are exactly the same. The scene question of the second interviewer is a bit tortuous, a list table, a search box to search the name, according to the normal operation idea, I said the full name, keywords, title bar, I got stuck, the interviewer asked me what else No, I have time to buffer, I answered two more points, uppercase and lowercase pinyin, and got stuck again, the interviewer still didn’t let me go, asked me again if there was anything else, pinyin extension, uppercase and lowercase initials, when it came to this, the interviewer said It’s ok, there is another question that is more thrilling, how to improve the complete coverage of use cases. This question is not difficult. As far as I know, there are two places in the materials issued by the training class, and there are quite a few, but I don’t remember much at all , so I can only say as much as I have. A few, consider special scenarios and give three, you can communicate with developers, find similar product references, look at it from the user's point of view, when it comes to this, the interviewer said that I have no problem, and I believe that I will have no problem in the interview later.

I have no experience, and I don’t know what the two sides are. At eight o’clock that night, Party A’s contact person turned on the two-sided phone, and only asked four questions, self-introduction, project explanation, scene questions, and a simple mailbox login test. Speaking of correct and incorrect accounts, password input, and interface performance testing , these are the operations in the mailboxes I have used. But during an interview during the day, an interviewer asked me if I didn’t consider security testing . I finally added security. The interviewer on the other side was a little surprised. I said that other colleagues have done it before, and I only did functions, interfaces, and performance. At this point, the interviewer said that I passed both sides.

A little explanation about security testing. Security testing is a part of software testing . After I joined the job, I was fortunate enough to follow the security post for a while. This position is not for ordinary people. At least three languages ​​​​are required, python, java, c, not to mention You have to write it yourself, but you can at least understand it and find out all the encrypted codes (that is, the key points of the test). This step is basically over, and the rest is compared with various requirements and specifications, one by one In contrast, non-compliance with the requirements is a risk. There are many requirements and specifications. You don’t need to memorize them by rote.

On the second day, I interviewed the second side of the first company and the third side of the second company. Both companies were in the same park. I went to pm in the morning to ask questions and answers. Anyway, I didn’t report my hope . I asked about self-introduction, what I did before, why I didn’t do it, expected salary, overtime and so on. Only then did I understand that it seemed like a comprehensive interview. After the talk, PM thought I was good, and I didn’t bargain for 10,000 yuan, but it suited me. Packed with more than three years of experience and a bachelor's degree. After I passed, the other party took me to the research base of Party A, a leader interview, practice makes perfect, self-introduction, test process, after two lectures, the other party said that I know a lot about the test, but in fact, my heart was beating, I just memorized it according to the information, Is the test really like this? Then the interviewer asked about their project, and he talked about some ways to make friends. If you don’t understand, just ask. He said that he could send me an offer, and went to another company in the afternoon. This outsourcing company has a relatively large scale. First, he met with two PMs, and he still talked about the introduction, testing process, and project explanation. , In the end, HR went to the stage to discuss salary and treatment. They made nonsense and expected that the salary would not be cut. They promised on the spot that as long as I agreed, I would send an offer. At this time, I had already received two offers. I said I would go back and think about it. On the way back, the HR sent me the salary Treatment, when I heard that the company next door also sent an offer, I changed my mind on the spot and said that my interview was good, and I added 1,000 (there is a commission for personnel recruitment). , double overtime.

Interview summary:

I asked about personnel, and she said that they like recruiting the most: one is that you have not changed jobs in the past three or four years, which means that your job is relatively stable; Educational qualifications that meet the company’s minimum threshold (college degrees are not very popular, Beijing, Shanghai and Shenzhen are acceptable), and finally accept overtime work. If you have these conditions on your resume, the personnel rush to find you for an interview. Last but not least, the company doesn’t like to run away after working for a few months. People who don’t understand the testing process at all, their academic qualifications are just to verify a person’s learning ability. .

Interview key summary and routine:

The first important point: self-introduction, where did the routine come from, which school graduated, where did you work before, how many years did you work on, what projects did you work on, which test post you were in charge of, what content did you do in detail, all dry goods, don’t talk about hobbies Nonsense, once you talk about it, it will make people feel that you are out of stock and filling up, and the interviewer is not in the mood and time to listen to you. Write it at the end of your resume and they will have eyes to read it. This question examines whether you can summarize, say what should be said, and waste expression when what should not be said.

The second key point: the test process. The interviewer wants to see if you have participated in this question, whether you really understand it, fully cover the routine, and talk about everything related to testing. Starting from product development, they work in two departments. When testing, testers need to participate in the review, test writing test design re-review, environment construction, subsequent iterative testing, generally there are one round and two rounds, gray scale, four rounds of online testing, question list, regression question list, etc., design problems do not meet the requirements Expectation, it is best to find the development to confirm it again, the development of the problem will generally admit it.

The third key point: project explanation, the interview time is limited, this question can take up to five minutes, so I only talk about a certain function of a certain module of a project, and all the influencing factors can be mentioned. Do you have any questions about this question? If you have done it, you have no experience, not to mention the interviewer, even the personnel screening resume will screen you out.

The fourth key point: Scenario questions, I will give you a scenario and ask you how to test, such as the water cup test. If there is no routine, it is easy to get stuck. This question needs at least ten questions to pass easily. The routine is also simple. Just come to the interface to test whether the layout of the scene is reasonable, such as equal spacing, easy to click, etc., whether the capitalization of the text is pleasing to the eye, and the appearance Whether the shape is beautiful or not, the bill of lading is developed and optimized, just three or four, and then talk about the function, what are the main functions of the scene, such as what else can the cup hold besides water, the camera can also be used as a flashlight besides taking pictures, smashing walnuts, etc. , and a few points casually, and then talk about the interface test , you can simply judge which stage the analysis problem is in, let’s talk about performance, such as where is the tolerance limit, time-consuming performance, a few special scenarios, compatibility points, and password input Add a security test, in short, point by point, orderly, clear and clear, without thinking about what to say, no one will think that you can't test after speaking. This question tests thinking.

The above four questions are referred to as general skills. If you grasp these four questions well, the technical interviewer will admit that you are really familiar with the test process. With that test thinking, you can learn it again during other internships, which can be used.

In addition to general skills, the interviewer also has other questions, such as: the bug you are most impressed with, the proportion of development and testing of the previous project team, the proportion of functional interface performance testing you are responsible for, the difference between http and https, the difference between postman and jmeter for interface testing, packet capture Front and back end judgment, breakpoint tampering, website framework construction, difference between post and get requests, 100, 200, 300, 400, 500 briefly, difference between cookie and session, two kinds of database deletion, what elements are tested for performance, smoke test, can language script, test Use case coverage, whether automation is possible, whether app testing is possible, general Linux commands, previous overtime work, where you live, your entry plan, and a regular routine: first familiarize yourself with the project business, do a good job at hand, and then optimize Improve testing efficiency, and rely on automation, testing, and safety in the future.

In the end, the interviewer will ask, what else do you want to ask to finish.

I would like to ask question 1: What is your project doing? How big is the team? Is there a mentor to accompany the entry? If you're the only one doing it, it's going to be a big hole in the wool.

I would like to ask question 2: Which test post will be responsible for after joining the job, function, interface, performance, app, automation, security, one or several of them, don't be foolishly doing the job of selling white powder, but get the salary of cabbage.

I would like to ask question 3: What stage is the project currently in, let alone agile development, you simply don't have the ability to keep up with the speed of development and testing, don't finish it right away, you go in and work for two months and then lose your job, or earn enough wages.

I would like to ask question 4: Do I have any development prospects after I join the company, such as changing jobs, and don’t get in the way of developing in a good place, I’m afraid that I will be trained as a salted fish after I enter the company.

Finally: If you don’t want to experience the feeling of not being able to find information when learning, no one answering questions, and giving up after persisting for a few days, here I will share with you some learning resources for automated testing, hoping to give you some guidance on the way forward. Come to help, friends can get it for free if they need it 【保证100%免费】

Collection of software testing interview questions

Our advanced study of automated testing must be to find a high-paying job. The following interview questions are the latest interview materials from first-line Internet companies such as Ali, Tencent, and Byte, and some Byte bosses have given authoritative answers. After completing this set of interview materials, I believe everyone can find a satisfactory job.

How to get the video file:

 

Guess you like

Origin blog.csdn.net/m0_75277660/article/details/130590076