Interface testing theory and classification

You must first know what interfaces are?

If you have your orders a hamburger, the staff tries to find the raw materials such as hamburger bread, meatloaf and lettuce, etc., in accordance with the provisions of the steps, these raw materials are combined into a hamburger, then give you; then in the example above , Hamburg raw materials is necessary interface conditions into parameters, i.e. the specific input interface; Hamburg production process, the processing logic is an internal interface; you to the front of Hamburg, the processing result is output and the specific interfaces, i.e. return parameter.

 

Interface logic processing unit is to have a specific input and a specific output, but it does not need to know its own internal logic implemented, which can also be called a black box processing logic interface.

 

The interface can be divided into two, one is an internal interface system or service, one is dependent on the external interface.

Internal interface is simple, the internal interface is an internal system call interface.

Then the software system, the internal interface is how it goes?

In fact, when you shop online, first log in and added items to the shopping cart, and then the next payment orders. So, from adding items to the shopping cart, and then pay for your order, among a long list of this process, the system is through the internal interface to complete.

So what is the external interface it? In fact, it is a concept relative to the internal interface exists above you in ordering the scenes is an external interface, it can be divided into two parts: a pre-order your ordering process. The external interface specific input when you are ordering, tell the waiter you want something, this is your output to the parameters of the restaurant. After the order, the waiter delivery process. Its specific output is attendant to Hamburg for you, which is restaurant back to your process result parameters.

What is the interface to test?

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. Stress test is to check the exchange data, and control transfer process management, and logical mutual dependencies between systems and the like.

Why do interface testing

Due to the complexity of the system is now rising, traditional testing methods and a substantial decline in the cost of a sharp increase testing efficiency, so we do interface testing. At the same time, interface testing is relatively easy to automate continuous integration, and relatively UI Automation also relatively stable, can reduce manual regression testing time and labor costs, shorten the test cycle, the back-end support fast development version requirements. Continuous integration interfaces can be the root of why the low-cost high-yield. Many systems now front end architecture is isolated from a security perspective, depends only on the front end has to be limiting system can not meet the security requirements (too easy to bypass the front), the rear end of the same need to be controlled, in this case We need to be verified from the interface level. Are the front and rear end of the transmission, log and print information encrypted transmission also need to verify, particularly in relation to the user's private information, such as ID cards, bank cards and so on.

Look at a map interface test

 

 


What kind of interface has it?

HTTP protocol interfaces, the interface RESTful format, the WebService interface, interface RPC protocol.

In fact, no matter what form of interfaces, they are by a transport protocol, the Client-side and between side Server to complete the data transfer. Analog interface test is actually the caller, such as Client-side, to detect the accuracy and fault tolerance test via interface communication interface. These analog front-end logic on the client side, invoke the interface provided by the Server side, can use some tools or code to do the job. ,

In the interface test, the tool or code is not its core, the problem is the interface test thinking you should focus on.

Interface testing, and you are most familiar with the business before the test, are concerned about whether the input and expected, especially when some of the input data for illegal import, processing and logic control interface is reasonable, which are determined by the return value of. There are some small probability processing logic is also concerned about the focus of our design input, such as some anomalies in the code, we have to find a way to trigger this logic branch of input parameters to determine the internal implementation of the corresponding interface by returning value processing logic is reasonable, whether robust.

On the scope of work, the influence of the interface will test range a little wider, it will overwrite the contents of a part of unit testing, part of the business will overwrite the contents of the test,

Interface testing and operational testing of the differences and connections, that is, "interdependent and indivisible."

Interface testing is done to test validated through the design input and expected output, interface testing is a technical knowledge and business knowledge combined with the work, but also functional test interface testing, interface testing and say that there are different places, and we just interact It is no longer a development engineer designed interface, but testing tools or code.

 

 

Guess you like

Origin www.cnblogs.com/dydxw/p/12274058.html