Interface Testing (3) Testing Basics

Concept
Interface: It is a set of definitions, procedures and protocols that realize mutual communication between computer software through API interfaces a>
Classification
1. Classification by object
Program internal interface
Program external interface
2. Classification by protocol
WebService interface: Webservice is the external interface of the system
HTTP interface: development interface based on HTTP protocol. Note: Interface testing is usually before functional testing, or in parallel Focus on checking the data exchange and transfer, control and management process, and logical dependencies between systems Mainly used between external systems and various internal subsystems Define specific interaction points between them, and then use these interaction points to interact with data through some special rules, that is, protocols. : A test to test the interface between system components
Interface testing


The significance of interface testing
1. It is difficult to ensure high coverage by relying on front-end testing alone. Interface testing can simulate various types of input parameters, including some that cannot be simulated on the front end. It can also design relatively complete input parameter values ​​​​based on the definition of the interface document to ensure quality at the interface layer. Most of the problems lie in the interaction and data presentation of the application itself.
2. Compared with interactive interface testing and functional testing, interface testing is easier to automate, is more stable in execution, and has lower maintenance costs.
3. Interface automation is suitable for regression testing, etc., which can reduce the labor cost of manual regression testing.
4. The front-end and back-end systems are separated. From a security perspective, relying only on the front-end cannot meet security requirements. It is relatively easy to bypass the front-end, so the back-end needs to also perform input verification. Only You can rely on interface testing to verify.

Interface testing process
Interface document analysis (similar to requirements analysis in the functional testing phase): interface name, interface address, request method, request format , request parameters, response parameters, error codes
Develop interface test plan
Test case design
Execute interface test cases and submit bugs
1. Verify the availability of the interface first
2. When an interface problem is discovered during the testing process, first seek confirmation from the developer before submitting the bug
Write interface test report

Guess you like

Origin blog.csdn.net/daisyxyr/article/details/125023956