As long as more than 90% of companies with software products will do interface testing, companies that want to do interface testing must have interface test engineers. Compared with other positions, interface test engineers are easier and more competent. If you want to engage in interface testing, you must analyze the interface and study test cases.
Of course, if you want to engage in interface testing, you must first pass the interview. Recently, interviews that are frequently asked about interface testing include:
**** Technology Services Co., Ltd.
first round:
1.Introduce yourself
2. How many projects have you done? Tell us about them.
3. What are your personal advantages?
4. Are you good at UI interfaces or interface automation?
5. What does interface automation measure?
6. How do you analyze the interface?
7. From what aspects are interface test cases considered?
8. How to set up a python environment
9. What custom functions have you encapsulated?
10. Let’s talk about bubble sorting
11. What do you use to manage the code after you write it?
Second round interview:
1. How to do automation?
2. What functions are encapsulated?
3. Do you understand regular expressions?
****** Co., Ltd. Shenzhen Branch
1. Reason for resignation?
2. Where do you live now?
3.Introduce yourself
4.Project introduction
5. How to test the date query in the query module?
6. How to do UI automation?
7. Are there many project requirements?
8. Composition of the project team
9.What does the company do?
10.How many interfaces does the project have?
11. How to do interface testing?
12.What interfaces have you made?
13. How do you analyze the interface before doing interface testing?
14. What is interface test case thinking?
15. Have you done any performance testing? What parameters are involved?
16. How to test the login module?
17. Anything else you want to ask?
18. How will you control the quality and progress of testing?
19. If the developer thinks it is not a bug, how should you deal with it if you think it is a bug?
Regarding the interface, if you encounter the following two questions during the interview, you can answer them according to the editor's summary.
1. How do you analyze the interface before doing interface testing?
1). Analyze the interface document to understand the detailed information of the interface and master the functions implemented by the interface: including the interface's request and response format, parameter description, return value, etc.
2). Analyze the association between interfaces: whether it is a single-interface association or a multi-interface association.
3). Analyze the request and response: According to the interface document, the request method (GET, POST, PUT, DELETE, etc.), request header, request body, request parameters, etc. in the request information; the status code, response header, etc. in the response information. The response body is analyzed.
4). Determine test data: According to the interface document, determine the request data and response data required for testing. Typically, interface testing requires providing correct request data to simulate user operations and verifying that the returned response data is as expected.
5). Determine test scenarios: Determine the scenarios that need to be tested based on the interface functions and business requirements.
6). Determine the test method: Select the appropriate test method based on the characteristics of the interface and business needs.
7). Write a test plan: Write a detailed test plan, including test scenarios, test data, expected results, etc.
8). Execute tests: Execute tests, record test results and analyze them. If defects are found, they need to be tracked promptly.
2. From what aspects do you start writing interface tests?
1). Business logic for normal data and business logic for abnormal data
2). Test the fault tolerance of the interface when the required fields are not filled in.
3). Testing of input parameter rules and testing of constructed data of various types of return codes
4) .Interface permission test--the performance of the interface with or without permission
5).Performance testing----concurrency testing, distributed testing, etc.
6).Interfaces related to money must be implemented according to the above 3 items
7). Interfaces that have nothing to do with money may only be automated scripts that control business processes.
2023 latest Jmeter interface testing from entry to proficiency (full set of project practical tutorials)