After collecting the interview questions of all dark horse students in 2022, the dark horse lecturers in charge of employment have sorted out 7 interview questions that appear frequently, let's take a look together.
High-frequency question 1: Please introduce yourself?
High-frequency question 2: Please introduce the projects you have done recently?
High-frequency question 3: Please introduce your impressive bug?
High-frequency question 4: How to use the Fiddler tool?
High-frequency question 5: Tell me about your commonly used Linux commands?
Frequently Asked Question 6: Where has the database been used?
Frequently Asked Question 7: Why did you leave your previous company?
How to answer these 7 interview questions so as not to step on the pit? Below I will refer to the answers to introduce you one by one, and collect them quickly .
Question 1: Please introduce yourself?
Core elements: personal skill advantages + work background + experience highlights
reference answer:
The first type: basic information + reason for leaving
Hello interviewer, my name is Zhang San, I come from Tomato City, and I have 3 years of working experience in the software testing industry. Has done testing work on Web/APP and small program projects, and has independent testing experience in charge of the entire project.
Due to personal reasons, I resigned from my previous company, and I am currently resigned. The above is my personal introduction.
The second type: basic information + project introduction
Hello interviewer, my name is Zhang San, I come from Tomato City, I have 3 years of working experience in the software testing industry, and I have done web/APP and small program projects Testing work, with independent testing experience in charge of the entire project.
The most recent project is xxx, which is a xxx product based on (B/S or C/S) architecture. In this project, I am mainly responsible for xxx business and xxx business and the functions of xxx module and xxx module. Interface, and automated testing.
The xxx test tool and xxx defect management system are mainly used in functional testing, and the xxx tool is mainly used in interface testing. The automated test is based on the test framework built and implemented by Python+Requests+pytest+Jenkins Test implementation. The above is my personal introduction.
Question 2: Please introduce your recent project
Core elements: What is the project, including several platforms, who is it for, what are they used for, what is the core business, and which modules are you responsible for.
Reference answer:
My latest project is a financial lending project, including front-end (Web/APP) and back-end management system (Web).
The front desk includes: home page, quality financial management, smart investment, community, and personal center (information sections for personal loans and my investment, which can be switched between each other).
The background includes: system home page, loan center, fund management, user management, authentication management, content management, message notification, customer service, etc. (Fund wealth management, insurance wealth management, bank selection zone)
Core business:
1. Loan process (divided into personal loan and online loan)
● Personal loan:
○ Registration--Login--Open a fund custody account--Application quota--Successful quota review--Borrowing method ( Credit mortgage)--Fill in the loan application--Submit the loan application successfully--The background preliminary review management has not reviewed--The background administrator has passed the preliminary review of the bid (failed, rejected, and the borrower cancels when it fails)--The loan application is successful
● Online borrowing:
○ Unregistered--applying for a loan online-approval of the loan application--adding users in the background--opening fund custody and applying for a quota at the front desk of the user--passing the background review of the quota--release the loan--passing the initial bid -- Borrowing success
2. Investment process
● Registration-->Investor login-->Enable fund custody-->Small recharge-->Risk evaluation-->Select funds to invest-->Full standard-->Full standard Approved --> Repayment by the borrower
I am mainly responsible for the functional testing and related interface testing of the two core modules of borrowing and P2P investment.
Question 3: Please introduce your impressive bug
Core elements: combined with your own project theory.
Reference answer:
I have tested a function before, after clicking the button, the page does not respond. I've raised this issue as a bug on the backend.
After reading the log, the back-end developer called me back this bug, saying that this is not a back-end bug. I used a packet capture tool to look at the interface and response before I found out that this is a front-end bug.
The reason why this bug is so deep is that I raised the bug without thinking too much, and then there was a little bit of friction with the back-end development.
In future work, if I encounter a bug, I will reproduce it first, and then locate the front-end or back-end of the bug, and then raise the bug.
That's about it.
Question 4: Have you ever used the fiddler tool? How do you use it?
Core elements: fiddler tool experience + fiddler tool function summary
reference answer:
1. I use Fidder in the login and registration module of the project. Register a valid email address at the front desk and submit it. Use fidder to intercept it. After capturing the packet, modify it to an invalid email address in fidder. Submit to see if the registration is successful. If it succeeds, the background interface is not available. authenticating. You can also capture the payment order information here to modify the data, modify the amount of money, and spend 1 cent to buy things.
2. Once took over a project, there is no document, and the project interface needs to be verified. Open Fiddler, then visit the project URL, grab the network request of the project, see which interface is accessed, what kind of data is passed, and the returned data, and then organize it into a document. It is convenient for later use.
Ps: Mac does not use fiddler to capture packets. Gotta use Charles
1. Analyze whether the defect is a front-end problem or a back-end problem.
For example: the request address for submitting an order:
① The interface organizes to submit the order product data, click [Submit Order] to trigger the sending request ② The background code performs processing, and returns the order-related data after the processing is completed. The returned data is determined by the developer (requirements determine which data to return) the order number, order amount, such as the order amount is displayed incorrectly on the interface, grab and submit the order response data, and check whether the total amount of the order in the interface returned information is correct. If the total order amount in the interface is correct, it is a front-end problem, and if the order total amount in the response message is wrong, it is a back-end problem.
2. The front-end has corresponding restrictions on the input information, which does not mean that the back-end code also has restrictions. For those who understand IT, each request address can directly skip the front-end page for operation. Verify whether the backend has corresponding restrictions on abnormal input.
3. Interface testing tests the implementation of each request. The development of some companies has not written interface documents, and the specific interface address can be obtained through the packet capture tool.
4. Do mobile weak network test
Question 5: Tell me about your commonly used Linux commands?
Core elements: Summary of Linux application scenarios + specific commands, function
reference answer:
As a test, I use Linux mainly in the following 4 scenarios:
1) Developers test, I will use linux to build a test environment here.
2) For example, after a developer submits a test, if I want to deploy his code to the specified path, I need to use the decompression command. Also compile and install.
3) Sometimes the server hangs up during the test, and to restart the service, I use the service command. |Others need to check the process, port, etc. after restarting,
4) But most of them are used more often because they will go to the server to check the log information if there is an error during the test. tail -f log file.
I won’t mention some simple ones such as ls ll cd pwd. The more commonly used Linux commands are as follows:
View process: ps -aux View port: netstate -tnulp | grep port number
Kill process: kill Forcefully end the process kill -9
Remote copy: scp find Find the specified file
tail -f View logs in real time cat is used for Display all the contents of the specified file
mkdir create a directory touch create a new file
tar.zxvf decompress chmod -R 777 give 777 permission
grep find strings that meet the conditions in the file
vim edit command mode, text mode, last line mode
Question 6: Where has the database been used?
Reference answer:
1 When executing test cases, sometimes it is necessary to verify the accuracy and integrity of the data in the database.
2 When locating bugs, sometimes it is necessary to check the detailed information of the data in the database.
3 When constructing a test scenario, you can directly modify the data in the database, which is more efficient than using the interface.
4 During the software upgrade process, the processing of historical data is often involved. In this case, it is necessary to execute the upgrade sql and verify the results.
Insert into inserts data, update modifies data, inner join query, left and right join query, subquery, I am very familiar with it personally.
Personally, the database visualization tool is navicat
Question 7: Why did you leave your last company?
Answer the prompt:
①The most important thing is: the applicant must convince the recruiting unit that the applicant's "reason for leaving" in the past unit does not exist in this recruiting unit.
② Avoid saying the "reason for leaving" in too much detail and too specific.
③It should not be mixed with subjective negative feelings, such as "too hard work", "complicated interpersonal relationships", "management is too chaotic", "the company does not value talents", "the company rejects our so-and-so employees", etc.
④ However, dodge and evasion are not allowed, such as "wanting to change the environment", "personal reasons" and so on.
⑤Do not involve your own negative personality traits, such as dishonesty, laziness, lack of responsibility, and not easy-going.
⑥ Try to make the reasons explained to add color to the applicant's personal image.
Reference answer:
I resigned because the company closed down; I have worked in the company for more than three years, and I have a deep relationship; since last year, due to sudden changes in the market situation, the company's situation has taken a turn for the worse; I feel very regretful at this point, But I still have to face the show and find a new stage where I can display my abilities.
There is not only one answer to the same interview question, and the same answer is not valid in any interview situation. The key is for the applicant to grasp the specific situation of the interview after mastering the rules, and consciously figure out The interviewer asks the psychological background of the question, and then hits the mark.
analyze:
Don't use "salary" as an excuse unless the pay is too low, or the original job. "Development" is also heard too much by the examiners. The reason for leaving the job should be designed according to each person's real reason for leaving the job, but you must be sincere when answering. When you really can’t figure it out, you can say that your family is out of town because you have to ask for leave for a few months because of something at home. It is impossible for the company to grant leave, so you resign. Generally, the interviewer can accept this answer.
In addition, see the comments section of the students who have attached the software testing interview book
