Some people will ask, why is this interview question the most authentic on the Internet?
Answer: This is sorted out from our thousands of interview experiences, so it is the most authentic ! ! !
Not much to say, let's just give you dry goods!
1. Interface test interview questions:
1. How is interface testing done and how to analyze data?
The actual difference between interface testing and general testing is the design part of the test case.
Get the interface specification.
Design interface test function use cases (mainly from the perspective of users to see whether the interface can meet business requirements, use case design is the set of black box use cases).
Various input parameter verifications (normal cases, abnormal cases include incorrect number of input parameters, incorrect types, optional/mandatory, and consideration of mutually exclusive or related parameters).
Various verifications of the interface return value (conforming to the requirements of the interface documentation)
Understand interface implementation logic and achieve logic coverage (statement/condition/branch/judgment/…)
Can the interface be executed concurrently, is it safe, and does the performance meet the requirements?
Use tools or self-written code to verify.
The problem found is the same as the functional test, the bug should be reported, the tracking status of the tracking status
2. What tool do you use to test the interface?
postman, jmeter, soapui (not commonly used)
3. Do you know what interface request methods are available? What is the difference?
GET post PUE DELETE
Difference: get pulls data directly from the server
post: first send the request and then pull the data (registration, update, change)
put: modified data
delete: User deletes data
These methods depend on the development, you can pass on whatever he uses
4. Why do interface tests?
1. Some logical problems at the non-functional level can be quickly found through interface testing
2. Can improve the efficiency of testing
3. Compared with UI automation, it is relatively stable and can reduce regression costs
5. Who should modify a bug that can be modified by the front and back ends?
backend modification
6. How to locate whether it is a front-end bug or a back-end bug (*)
1. Verify this BUG and reproduce the bug on the front end
2. Find the log file on the server
3. Use tail -f to display the log
4. To observe the log, if there is a clear "exception", it is an error in the background
5. The return code of the interface is 500+, which means a server problem or a background problem.
front end:
The previous problem is generally the problem of the interface, but the error that the development adds a new request parameter to the url and does not write it into the interface document belongs to the back-end error.
Generally, problems such as page layout and display are front-end problems.
8. Toutiao’s list page interface, this interface has three parameters, one parameter is the type field, type=1 means it is a graphic article, type=2 means it is a video article, when type=3 it is a plain text article, and the other two The first field is pagesize, and the other parameter is pageno. How do you test this interface?
Answer:
Pass in type=1 pagesize=6 pageno=1 and it returns 6 pieces of data on the first page of the data graphic article list
Pass in type=2 pagesize=3 pageno=2 and it returns the data of the 2nd page and 3 pieces of data of video articles
Pass in type=3 pagesize=4 pageno=2 and it will return 4 pieces of data on page 2 of video articles
The type is empty, the number of rows is empty, and the number of pages is empty, it returns no data
Type and number of items and pages are passed in special characters, super long, and negative numbers are passed in, and its nodes return no data
9. The account registration is successful, but the login fails, how to troubleshoot?
If the registered user's data is not passed into the data, then call the login interface to see if it is successful, if it fails, raise a bug
10. I want to test the product list interface, but this interface depends on the login interface. This interface can only be tested after successful login. How to use postman to test this interface?
1. First create a login interface in postman, and make sure that the login is normal. If it uses cookies, then you need to pass the cookie into the header information of the list interface
If the token returned by the login interface is in the returned message, then the list interface can directly pass in the token in the header information
After the last two connections, pass in different parameter values according to the use case to verify whether the product list interface is normal
2. Ui automation test interview questions:
1. Write 4 xpath positioning methods to locate the controls in the red box as follows
2. How to navigate from the a tag in the red box below to the div tag in the red box below?
3. How to navigate from the a tag in the red frame to the form tag in the red frame below?
4. For the following iframes, how to locate and switch to iframe1, iframe2, iframe3, and iframe4; if you have already switched to iframe4, how to locate a certain control in iframe2?
If you switch to iframe2, how to locate a certain control in the body?
3. MySQL written test questions:
1. Extend the length of the field fund code to 8 digits
2. Count the total shares held under the same seller and outlet code
3. Count the total number of the same fund account number and fund code records with more than 2 records
4. Update the share of the record with the fund account number 100008 and the smallest outlet code to 2000
CREATE TABLE A (
P_ID int,
p_num int,
s_id int);
INSERT INTO A VALUES
(1,10,01),
(1,12,02),
(2,8,01),
(3,11,01),
(3,8,03);
select a.*,a.s1_id+a.s2_id+a.s3_id as sum_p from (select p_id,
sum(case when s_id=1 then p_num else 0 end) as s1_id ,
sum(case when s_id=2 then p_num else 0 end) as s2_id ,
sum(case when s_id=3 then p_num else 0 end) as s3_id
from product_t group by p_id) a;
4. Test basic interview questions:
1. Describe the agile testing process
2. Introduce the business process of the project you have done
3. What was the composition of your team when you introduced the projects you worked on? How many developments and tests are there, how long is the project cycle, time 4, how to allocate, how many use cases, how many bugs, etc.?
5. What is the difference between APP testing and web testing?
6. What is included in the test plan?
7. What is a smoke test case? Which smoke test cases are generally selected as smoke test cases
8. Tell me about the bug handling process, what tools do you use for the bill of lading?
9. Tell me about the bug that impressed you the most
10. How to deal with occasional bugs
11. What are the methods of test case design? What method to use in what scenario
12. There is a function of uploading files, which need to be uploaded. What are the test points?
13. Carry out test case design: a string of numbers, leap year discrimination
14. How to test the ip address (the composition of the IP address is: (1~255).(0~255).(0~255).(0~255))
15. What are the elements of the test report?
16. Bug handling mechanism bug grading
17. When a bug occurs online, what is the processing process like?
18. Test case design for order list display
19. What standard do you think a software can meet to go online?
20. Please carry out test case design: a string of numbers, leap year discrimination
Well, that’s all for today’s sharing, and I’m sorry that I can’t share all the interview questions here. In fact, I have sorted them out in our question bank, and there are complete answers. Everyone can learn by themselves. , Come on , keep accumulating yourself, know what questions the company will ask in the interview, you will be easy to succeed!
