Table of contents
2. What is required for interface testing?
4. How to obtain interface-related information?
5. How to conduct interface test?
6. Automated interface testing
1. What is interface testing?
Definition: A test that tests the interfaces between system components. It is mainly used to detect the interaction points between external systems and internal subsystems, focusing on the inspection of data exchange, transmission and control management processes, and mutual logical dependencies between systems, etc.;
Purpose: to test the correctness and stability of the interface;
Principle: Simulate the process that the client sends a request message to the server, the server processes the corresponding message after receiving the request message and returns a response to the client, and the client receives the response;
Key points: Examining data exchange, transfer and control management processes, including the number of processes;
Core: continuous integration is the core of interface testing;
Advantages: Bring efficient defect monitoring and quality supervision capabilities to highly complex platforms. The more complex the platform, the larger the system, the more obvious the effect of interface testing (improving test efficiency, improving user experience, and reducing R&D costs);
Key points of use case design: Usually, the two outermost interfaces are mainly tested: data entry system interface (calling the parameters of the external system for use by the system) and data outflow system interface (verifying whether the data processed by the system is normal);
PS: When designing use cases, it is also necessary to pay attention to what functions external interfaces provide to external users who use these interfaces, and what functions external users really need;
Python interface automation testing: 2023 latest collection of Python automation testing development framework [full stack/actual combat/tutorial] collection essence, annual salary 40W+ after learning_哔哩哔哩_bilibili 
https://www.bilibili.com/video/BV1AF411T7qJ/ ?spm_id_from=333.999.0.0
2. What is required for interface testing?
① Understand the business logic interaction between the system and various internal components;
② Understand the I/O of the interface (input/output: input and output);
③ Understand the basic content of the protocol, including: communication principle, three-way handshake, commonly used protocol types, message composition, data transmission mode, common status codes, URL composition, etc.;
④Common interface testing tools, such as: jmeter, loadrunner, postman, soapUI, etc.;
⑤Basic database operation commands (check data storage, extract test data, etc.);
⑥ Common character types, such as: char, varchar, text, int, float, datatime, string, etc.;
3. How to learn these skills?
①Business interaction logic between systems: through many channels and methods such as requirements documents, flow charts, mind maps, and communication;
②Protocol: I recommend the book "Illustrated http", which is vivid in content and is relatively an entry-level book. Others include "Illustrated tcp, IP" and so on;
③Interface testing tools: Baidu these tools, and then you will find a lot of teaching blogs, related problem solutions, and some tools-based books, of course, it is very important to choose the right book;
④ Database operation commands: learning websites, teaching blogs, and some database-related books, entry-level recommendations: "mysql must know and know", "oracle PL/SQL must know and know", etc.
⑤Character type: Still Baidu, there is a saying: if you are not sure about internal affairs, ask Baidu, and if you are undecided about foreign affairs, ask Google. . .
4. How to obtain interface-related information?
In general enterprises, the development or corresponding technical personnel will write the interface document, which will indicate the address, parameter type, method, input, output and other information related to the interface. If not, find a way to obtain it. . .
Eight elements of an interface document:
Cover: The cover should preferably be the cover specified by the company, with logo, content title, version number, company name, and date of document generation;
Revision History: The table format is better, including: version, revision description, revision date, revision person, review time reviewer, etc.;
Interface information: interface calling method, commonly used GET/POST method, interface address;
Function description: describe the interface functions concisely and clearly, for example: what information is not included in the interface acquisition;
Interface parameter description: each parameter must be the same as the actual call, including upper and lower case; the meaning of the parameter is concisely explained, and the format is string, int or long, etc.;
In the description part, explain where the parameter value needs to be provided, and detail how the parameter is generated, such as the timestamp, which time period it is, whether the parameter is required, some parameters are mandatory, and some are optional parameters, etc.;
Return value description:
① It is best to have a template return value and explain the meaning of each return parameter;
②Provide a real calling interface and real return value;
Call restrictions, security aspects:
Encryption method, or a special encryption process of your own company, as long as both parties adopt a consistent encryption algorithm, the interface can be called to ensure the security of the interface call, such as the common md5;
Document maintenance: When the document is being maintained, if there is any modification, the modification date and the person who modified it must be written, and the version number must be changed for major modifications;
Python interface automated testing:
5. How to conduct interface test?
After experiencing the above scenarios, I believe most people should be able to do interface testing. As for which tool to use and the problems encountered in the execution of the test, please Baidu! ! !
There are blogs, libraries, group files of major test groups, and tutorial books, and there are many, many. As long as you use your hands and brain, general problems can be solved. . .
Massachusetts Institute of Technology school motto: Mens et Manus (Mind and Hand) --- hands, brains! ! !
6. Automated interface testing
As mentioned earlier, the core of interface testing is continuous integration, and automated testing can improve work efficiency and reduce costs, so the automation of interface testing is very necessary.
As for the framework of interface automation, it can be said that there are many kinds. According to the different tools used, the programming language that the individual is good at, the needs of the working environment, etc., the flexibility is relatively large.
The framework I am more familiar with: jmeter+maven+Jenkins+mysql+dubbo. . .
7. Others
Engineers refer to those who have the ability to operate, design, manage and evaluate engineering systems. The title engineer is usually reserved for persons with a professional degree or equivalent work experience in one of the fields of engineering. ----Baidu Encyclopedia
The IT industry is a knowledge-intensive industry, and software testing engineers should also have corresponding knowledge and skills, namely: core competitiveness.
Continuous learning is essential, don't let yourself be easily replaced! ! !
Python interface automation testing: 2023 latest collection of Python automation testing development framework [full stack/actual combat/tutorial] collection essence, annual salary 40W+ after learning_哔哩哔哩_bilibili https://www.bilibili.com/video/BV1AF411T7qJ/ ?spm_id_from=333.999.0.0
The correct way to learn new technology:
