A method and system for managing API interface addresses

Abstract

The present invention relates to a method and system for managing API interface addresses. The method includes: obtaining a target item and related items, establishing a binding relationship between the target item and the related items, adding an API interface address according to the binding relationship, and calling the related The API interface address of the project is used. The management system includes an acquisition module, a relationship binding module, an address binding module, and a calling module, which solves the problem that multiple R&D personnel are required to cooperate with testers to carry out project testing, and can be used for different projects. The API interface address is managed in a unified manner, and the API interface address can be called flexibly, which avoids the confusion of the API interface address caused by the release of the project version.

Description

technical field [0001] The invention belongs to the technical field of computers, and particularly relates to a method and system for managing API interface addresses. Background technique [0002] With the frequent changes of computer business and the rapid iteration of software projects, the code system used in each project will adopt the management method of trunk and multi-branch. The version control system of open source code generally used is one of git and svn. With the detailed differentiation of business modules, different projects focus on a certain aspect of functional services. [0003] During the development and environmental testing of new projects, for the convenience of version control and clear code management, a new branch will be created for development, and each system will call each other with the specified branch address for interaction. interface), when the new project version is tested, the developers who need to connect to the system need to modify ...

AI Technical Summary

Problems solved by technology

[0003] In the development and environment testing of new projects, for the convenience of version control and clear code management, a new branch will be created for development, and each system will call the specified branch address for interaction. interface), when the new project version is tested, it is necessary for the developers of the docking system to modify the application programming interface (API interface) address once, which requires a lot of manpower to modify; there will be changes during the modification process The address is wrong, or you forget to release the code to the test environment after modification, which will cause the test to be invalid; if the new project is urgent, or the test is proposed during non-working days, it is difficult to find the assistance of operators in other projects, not only the test progress cannot be guaranteed, but also the Delay the normal schedule of the project and go online; the current solution is that the R&D personnel in the new project manually simulate an interface and request their own system in the project. Because the simulation interface is not accurate enough, it is difficult to form a complete interaction process and it is difficult to improve it according to the interaction problem. In this project, the risk of launching the project is relatively high; and the API interface addresses of each system end are confused, and it is often unknown which version the address is called, which seriously affects the test progress and test effect

Images