A multi think about why it
Usually work, you are not often encounter such a situation? Leaders said, xxx, you are ready to do it at the interface testing, interface testing reports remember to give me a copy. After hearing a lot of people, you do Pidianpidian interface testing. Sometimes I think they really know: Why do interface testing it? Frankly, in fact, at first I also do not know why the interface test. . .
Second, what is the interface testing
Testing at the interface between the test interface system components. An interface test between the point of interaction is mainly used between the detection system and the external system, and inside of each subsystem. Key tests are interdependent relationship between the inspection data exchange and delivery systems.
In general, the test interface refers to the functional, performance and stability test test interface, and of course the level of chiefs of security testing. In addition, work is the interface to test the basic interface test against HTTP or HTTPS protocols.
A project, we may encounter many interfaces, there are dozens of small, there are many hundreds of thousands of interfaces. When do interface testing, we do not have the software interface, there is no specific test scenarios, only one interface description document. Interface, is an abstract thing, we need to take advantage of software testing theory and methods and interface documentation, which found defective function and safety of the interface.
Interface includes internal and external interfaces.
- Internal interface: developers to develop their own interfaces
- The external interface: for example, sites and call micro-channel pay Alipay payment interface; some of the interface between the module and the module
Third, why do interface testing
1. Now before and after a lot of system-side architecture are separate, because different ends (front-end, back-end) of the progress of work is not the same, so we have to respect the interface initially come out, and you need to call other companies (banking, Paypal, micro-letters, qq, etc.) some interface interfaces testing and verification data. For security reasons, only rely on front-end system limit has been completely unable to meet security requirements, after all too easy to bypass the front-end verification. . . So, we need to back-end verification, namely for verification from the interface level. PS: a message related to the user's privacy, such as identity cards, bank cards, etc., to verify the level from the interface.
2. forward now respected test, also known as test left, hoping the test can intervene earlier test, just to test the interface is a kind of early intervention approach. Traditional test requires both the front and rear end can be done after the test, in order to automate coding writing. But different interface testing, only the front and rear ends well defined interface, the interface can be involved in the preparation of the automation interface to automate test code, and the interface for manual testing only need to back-end code is complete, you can step back-end logic test, do not wait for front-end work is done quietly greatly improve the efficiency of the test.
Reference Links: https://www.cnblogs.com/du-hong/p/10494149.html