Interface Test - Interface Test Definition

1. Concept of interface testing (emphasis)

Interface testing is a test for testing the interface between system components, which is between unit testing and system testing.

Interface testing is mainly used to detect the interaction points between external systems and internal subsystems.

The focus of the test is to check the exchange of data, the process of delivery and control management, and the mutual logical dependencies between the systems.

In other words, interface testing means that the developer implements the interface, and we need to verify whether the implementation of the interface is correct. But this is a background function, and I don't want front-end personnel to intervene, because it will be more troublesome for front-end personnel to intervene.

Summary: Interface testing is to replace the front-end to verify whether the server-side program is correct.

2. Principle of interface testing (emphasis)

• Testers use tools to simulate the client sending requests to the server.

• After the server accepts the request, it processes the request accordingly and responds to the client with the result.

• After the client receives the response data, the tester judges the result.

Interface testing is black box testing. As a black-box test, the basic test idea is to judge whether the logic of the system or object under test is correct through input and output.

3. What is the basis for interface testing

1. need. Familiarity with actual business requirements can better help us design test cases and prepare test data.
2. Interface documentation. According to the interface description document, develop the interface test script and execute the script.
3. Prototype diagram. You can better judge whether the actual test data conforms to the logical relationship between the interfaces according to the prototype diagram.

4. Interface test classification (important)

• Web interface test:

  • Server interface test: test the interface implemented by your company (the focus of work)

    Calls between different modules and different services within the same system.

    For example: the current mainstream system architecture is the application layer, service layer and data layer. Application layer: responsible for displaying data and initiating data requests. Service layer: Provides data processing for the application layer. Data layer: used to store data, including relational databases, etc. The interaction between each layer is through the server interface.

  • Third-party interface testing: testing interfaces implemented by other companies (interface calls between different systems or even different companies)

    Many third-party interfaces will be used in the project. For example, to make a system to display the daily weather, how do you get the weather data? It is impossible to predict the weather by yourself, there are free third-party interfaces available, just call the desired weather data according to the interface protocol. Of course, this is data outside the calling system.

    For example, when a third party logs in, it calls the external company's Weibo login, WeChat login interface, etc.

• Module interface test: It is to test a method in a class, or an interface in a module.

  A program internal interface test, module interface test is the basis of unit test, it mainly tests the call and return of the module.

5. Characteristics of interface testing

• No UI interface: You cannot see the application interface when doing interface testing.
• No UI interactive operation: Since there is no UI page, it is impossible to perform little operations on the UI.
• Different from manual testing: interface automation testing can be used for continuous integration, and the interface coverage rate is relatively high.
• Protocol-based: The interface test is a test with an access protocol, and it is necessary to test whether the protocol and the content in the protocol are correct.
• Data verification: Check the data exchange, delivery and control management process, including the number of processing times and whether the business logic is correct.
• Format verification: data format verification of request parameters and return values, including the default of parameters, whether the returned data is complete, etc.

---

END meager strength

Finally, I would like to thank everyone who has read my article carefully. Looking at the fans’ growth and attention all the way, there is always a need for reciprocity. Although it is not a very valuable thing, you can take it away if you need it:

These materials should be the most comprehensive and complete preparation warehouse for [software testing] friends. This warehouse has also accompanied tens of thousands of test engineers through the most difficult journey, and I hope it can help you too!

加入我的软件测试交流群：110685036免费获取~（同行大佬一起学术交流，每晚都有大佬直播分享技术知识点）

Software testing interview applet

The software test question bank maxed out by millions of people! ! ! Who is who knows! ! ! The most comprehensive quiz mini program on the whole network, you can use your mobile phone to do the quizzes, on the subway or on the bus, roll it up!

The following interview question sections are covered:

1. Basic theory of software testing, 2. web, app, interface function testing, 3. network, 4. database, 5. linux

6. web, app, interface automation, 7. performance testing, 8. programming basics, 9. hr interview questions, 10. open test questions, 11. security testing, 12. computer basics

method of obtaining: