function comparison
In actual work, I personally use the three tools eolink, apifox, and apipost. Next, I will compare the three functions, so I pulled a list of function comparisons.
Special Note: The following comparisons are not to be criticized, but only to list functions, purely objective comparison, and do not have any meaning of commercial delivery .
The three tools eolink, aifox, and apipost have many functional modules. This time, only three commonly used functional modules are selected, including interface testing, mock data, and online documentation.
The following is a comparison of several sub-functions such as interface testing, mock data, and online documentation.
We will select several commonly used functions for actual practical comparison, and show you the similarities and differences of the three tools.
Interface Test Comparison
http/https protocol test
The http/https protocol test is the most commonly used function in daily work. The three tools eolink, aifox and apipost all support this function. We mainly compare the UI interface and the ease of use of the function.
Here is a demonstration using the get request interface: https://suggest.taobao.com/sug?code=utf-8&q=%E6%B5%8B%E8%AF%95&callback=cb
eolink
After clicking to create an interface, it will be displayed in the top tab, including five functions: document, edit, test, mock, and monitor.
Click the test tab to see, including: request header, request body, Query parameters, REST parameters, permission verification, pre-script, post-script, advanced settings and other functions.
Click the send button to receive the request, and display the interface data in the returned result section. The time analysis function is displayed in the returned result section, which can analyze the entire network request process from the interface request to the interface returned data.
apifox
After clicking Create Interface, four functions including document, modify document, run and advanced Mock are displayed on the top.
Click the test tab to see, including: Params, Body, Headers, Cookies, pre-operation, post-operation and other functions.
Click the send button to make an interface request, and display the returned data in the returned Body.
apipost
The creation interface page of apipost is different from the layout of eolink and apifox, and feels more like the page layout of postman. Mock data needs to be switched below.
Click the send button to send the interface test, view the returned data in the real-time response section, and display the response header status code, interface response time and other data.
Summary: In the http/https protocol test, the three tools of eolink, aifox, and apipost can all support the practicality of the function well. The difference is the difference in the layout of the page and the difference in user experience.
WebSocket protocol test
When we do interface testing, in addition to the common http interface, there is another kind that is more common, which is the WebSocket interface.
The WebSocket protocol test function is supported in eolink and apipost, but not in apifox.
eolink
Select ws protocol on the edit page, and enter ip+port information.
Click the Establish Connection button to first establish a WebSocket connection.
If the link is successfully established and the send button appears, it means the connection is established successfully. Enter name:1234 in the parameter name and parameter value, and click the send button.
After clicking Send, you can see {"name":"1234"} in the message content part, indicating that the WebSocket protocol message was sent successfully.
apipost
On the create interface page, select the Raw protocol and enter the ip and port, click the connect button, if the connection success text appears, it means the ws connection is successful.
In the send content area, enter name:1111, click send message, you can see the message just sent in the message list.
Summary: Both eolink and apipost support WebSocket protocol testing, and they can perform WebSocket testing well during use.
The use of timing test in eolink
The timing test function is very practical in work. For example, there is an online interface that requires timing of the status code of the health service and whether the returned data is normal. In the past, jenkins or third-party tools were used to implement the timing test function. I really hope that the interface test itself can support this. Function.
Compared with eolink, aifox and apipost, only eolink has this function. Next, we will briefly introduce the practicality of timing test in eolink.
First, select the API Monitor space at the top to solve the 7 * 24 hour regular monitoring, prevent and reduce business losses caused by API exceptions.
Select an interface that needs to be monitored, and select the monitoring frequency once every 10 minutes. The monitoring frequency can be adjusted according to business needs.
The monitoring implemented by eolink is not local monitoring, but a practical cloud monitoring solution, using monitoring nodes all over the country. The advantage of this is that some interfaces may have problems under certain regional networks, and it is practical to monitor using monitoring nodes across the country , covering a wider range.
After clicking to start monitoring, it will be monitored at a frequency of 10 minutes. If an error occurs, it will be displayed on the dashboard, and a line chart of the interface will be requested according to the time sequence at the bottom.
Summary: Using the timing test function in eolink is relatively simple and has rich functions in overall practicality. In addition, with the powerful chart function, it can more intuitively reflect the effectiveness of monitoring.
Interface document sharing
After we finish writing the interface document, it will be provided to other teams or partner companies for development docking. In the past, word documents or tables were provided for viewing. If there are parameter changes, it is impossible to view the latest interface documents. We hope to provide the other party with a real-time updated online interface document, which can improve the efficiency of work and cooperation.
Only eolink and apipost have the interface document sharing function, and the comparison between these two tools will be used below.
eolink
Select the API and click the Share Project button. Click to enable sharing, and the sharing address will be automatically generated, and the visible page permissions and passwords can be set.
Copy the generated link address and put it in the browser to view and execute the interface use cases. If interface parameters are changed on the eolink client, just refresh the access address of the browser.
apipost
Select the share tab and create a new custom share, and then check the interface that needs to be shared. An online browsing address will be generated and placed in the browser for access.
But in the web page, only interface documents can be viewed but interface testing cannot be performed.
Summary: In terms of interface document sharing, eolink, aifox, and apipost all support the most basic function of viewing interface protocols, but eolink can perform more responsible operations on the PC page and the experience provider is also very good.
epilogue
The above is the basic practicality and comparison of the three tools eolink, aifox, and apipost. In summary, the three tools can meet the daily practical needs of interface documentation and interface testing. But in actual work, we will use multiple interface-related tools, hoping to finally have a tool that can manage the entire life cycle of the interface and reduce our cost of switching tools. Currently, eolink apikit is the best tool I have experienced. The support function is powerful. The timing test, project monitoring, and collaboration capabilities mentioned in this article, if you think it is good, you can experience it~.