Is the entry of Qihoo 360 very strict?

Today's tests need to be able to write Hello World in 8 languages! The level of test development is becoming more and more sophisticated. Is there no way out for the so-called "little" function tester? I am a functional test, and my work includes "bit by bit", but I need to know where to start bit by bit and what tools to use.

Many company interviewers are: building rockets for interviews and screwing screws for work. As a first-line manufacturer 360, the interviewer I met has never encountered such a situation. I was lucky not to be abused and successfully joined a great company. Let me talk about the interview process. In describing the interview process, I added some work contents after I joined the company.

I interviewed two groups of people by inference. The first group failed. Because I didn't know the code at that time, I definitely couldn't pass the exam. The second group is the function test below T4, which is also introverted. Two introverted colleagues can also chat in the group, so I got this interview opportunity.

I made a set of interview questions first, which was determined by the team leader (also my interviewer) of my work. These problems include the details of using bag grasping tools; The specific content of BUG description; You know the performance test method; The error diagram of windows Task Manager needs to find its BUG. There are some other conceptual problems, which I don't remember clearly, probably: the test type of V model, the description of iterative-incremental development model, what needs to be clarified at each test level, and so on. The team leader gave me the exam questions and left.

As a "senior interviewer", I deeply know that it is meaningless to open the mobile phone to search for answers at this time. The content and results of the interview, the answer only accounts for a small part. If the answers you write through search are more detailed, comprehensive and official, will you fail if you can't answer orally? So I answered all the questions as I thought. Half an hour later, my team leader came back on time. After reading each of my questions, I began to ask questions orally, without looking at the papers before and after.

The first is to describe the actual use scenario of the bag grabbing tool.

I choose those narratives that I do the most every day, but I dare not say that I do less, for fear of being asked:

(1) Replace the host; ;

(2) Buried point report;

(3) Self-startup of Windows-side test environment software: Add both fiddler and the tested software to the Windows self-startup menu (right-click "Self-startup" in the start menu to enter the folder settings). After configuring fiddler with the host, restart the computer. After the computer is restarted, it will automatically start fiddler and the software under test, and the test software will be automatically upgraded in the test environment immediately after the computer is turned on.

In the later work, I used the package grabbing tool to achieve "the download button should judge whether the specified APP has been installed, and there is no need to download it repeatedly"; Create your own ini configuration file, sign your own name, type your own cab upgrade package, redirect to local, redirect ini.update and dl interfaces to local files, and upgrade the simulation server. If you can talk more about this general skill in the interview, you will get extra points.

The next step is the known performance testing method.

I have always been a "bit by bit" testing client or terminal, so it is all based on UI. Among them, we all know:

(1) recorded with a high-speed camera. A few frames, add a manipulator to simulate clicking;

(2)adb commands batch simulation to click screen coordinates, and adds interval waiting ping 127.438+0 as its own host for "beauty".

-n 6 ping6 times, which takes about 5 seconds.

& gtNul does not display the running result of ping on the screen. If you don't add > Nul, it will have no effect.

(3) I included Monkey in the performance test. If no one tells me what the startup activity of the application is. Search "cmp=" in Logcat to find the startup activity of the application.

(4) Check the CPU utilization value and the memory utilization rate.

My team leader asked me if I had any practice in stress testing. I said very little, basically adb ordered coordinate clicks, such as taking pictures 500 times; Or perform operations continuously for a long time. Because I can't identify the page elements, I can't accurately grasp the elements to click. My team leader said, haven't you ever thought that "hanging up" is also a stress test? It dawned on me ... stress tests are everywhere.

Thoughts on safety inspection

As the best security company in China, we must ask some questions about security inspection. I said some ideas about the safety test I prepared:

(1) Check whether there are debugging and information logs in the APP process.

(2) After clearing the cache, you can't log in, which means there are no cookies. Remember the password of the same account and log in for a few days to see if it will take effect. Cookies have a time limit; The function of not recording password after login failure.

(3) Is the Cookie generated after successful login only http? Otherwise, it is easy to be stolen by scripts. Use Firefox's cookie manager.

(4) directly enter the URL address of each function page in the address bar to see how the system handles it, whether it can directly link to the view (anonymous view), whether it has permission control, whether it can be directly executed, and return to the corresponding result page.

(5) Limit the number of wrong logins to prevent violent cracking.

(6) Whether the user name and password are sent to the Web server through encryption.

(7) Don't enter anything, click the submit button and see the prompt. (Non-null test)

360 didn't know until after work that "safety" is a consciousness that everyone strictly abides by, from product development to testing to operation, not to mention strict code submission specifications, safety audit procedures, and the red line system that must fix safety problems within 48 hours. Specific verification items cannot be classified in detail, but they are indeed the king of safety.

Server-related

Although the previous testing work must have server-side interaction, we all call it: cloud configuration, and so on. I didn't really touch the server, just looked at the interface business and so on. I didn't answer the question about the server. My team leader didn't neglect my acquisition of exam knowledge because I just came for an interview. Take the initiative to tell me that the test of a new interface is not only a logical test of the server, but also a fault-tolerant test of the client. When the client can't tolerate the return value, for example, the specified logic given by the server is 6, and the interface is intercepted and manually set to 999, or the frequency is set to 1, and the interface is intercepted and manually set to 0, or null, an abnormal memory leak may occur and the application will crash and dump.

I clearly remember pretending to understand and nodding my head all the time. Actually, there is no outline at all. Later, it was found in practical work that it was so simple and so basic. So this should be mentioned in the interview.

I didn't answer anything else about databases and code classes, but I really didn't. But this will definitely be asked, how can there be a test without a database? Even the local test database should be operational. I can say the basic concept of software testing is relatively complete. Most importantly, I really showed my love for 360. My team leader later told me that I was admitted to the school because I loved 360 very much.

This is part of the experience of this interview. It's incomplete, after all, it involves some secrets. But this interview is a twist, and the actual work is also a twist. What you see is what you get, very real! It also proves that the old aunt who can only test the function can also join the big factory and work smoothly. I learned how to use a lot of tools in a big factory, which added a lot of assistance for functional testing. Because functional testing is smoother, there is more time and opportunity to go to advanced test development and learn code.