With the growth of the company’s business and the continuous changes in project requirements, the cost of operation and maintenance has become higher and higher, and the developer 996 has become more and more normalized. At the moment when most companies implement front-end separation, the R&D team is used for communication The time spent in, testing, and managing APIs and the time spent on developing project code are also getting the same. The following API-related issues have appeared widely: API documentation is not clear and I don’t know how to connect and test, and need to communicate with the backend repeatedly, and even look at the code; Frontend and testing need to wait for the completion of API development to continue working, and test cases cannot be replicated Use; API changes are not followed up in time, and I don’t know where to change; Interface documentation and testing are two systems, which switch back and forth and cannot synchronize data; Automated testing requires scripting, which requires high learning costs, time costs, and maintenance costs;
Don't worry about the solution, let's first deal with the driving method of API development.
In the process of API development, it can be basically divided into document-driven and test-driven. The former refers to writing interface documents before development, replacing oral conventions and note-taking documents with standard documents; the latter refers to writing test cases before development and quickly using test results to promote development progress.
So are these two driving methods separate? The answer I will say is no. The shortcomings of traditional interface documents are three points: natural language descriptions are prone to ambiguity; they cannot be verified automatically; and they cannot guarantee the synchronization of documents and development. Thus, the corresponding test drive is extended. So another way of thinking, if there is a tool that can automatically generate documents and meet most of the interface testing functions, isn't it all right? Our company recently started looking for a new API management tool due to localization needs, and later found a good one called Eolinker, which can meet the API development and management needs of our R&D team, and can directly import the original Postman and Swagger APIs. Project and interface documentation. Put two used pictures, and if you have used them, you can share them together~ Scenario 1: Front-end development has completed the API docking, change the current API status to pending test, and notify the relevant testers for testing.
Scenario 2: The back-end has developed the API, and uses the test cases written by the testers to test the API in batches to troubleshoot errors. 
Use address: www.eolinker.com