This domestic API tool is too powerful! made me give up postman

Why abandon postman and switch to Eolink?

Programmers usually need to self-test after the interface development is completed. When the returned results meet expectations, it means that the interface is available. I used to use postman for interface testing before, but postman can only perform interface testing, which has limitations, and many scenarios cannot meet my needs, such as the inability to simply move APIs between collections, and the inability to create folder management when managing Collections Multiple, synchronous data functions are often not easy to use.
Just some time ago, I came across a good API tool by chance. I have used this product for a while. Generally speaking, it is very suitable for everyone, whether it is development, testing, operation and maintenance, etc. I think it is good. Let me show you how it works in practice.

You can compare the main function lists of Eolink and Postman , and the advantages of Eolink are reflected.

I also read the official introduction to Eolink. The main functions of the product are reflected in API interface debugging, Mock function, automated testing, teamwork and interaction, combined with API design, document management, automated testing, monitoring, and R&D. Management and teamwork, it also integrates platforms such as Gitlab, DingTalk, Enterprise WeChat, Jenkins, Feishu, etc. It is simply a hexagonal warrior without any shortcomings! Most importantly, Eolink has taken the lead in commercial use!

The current product is free, and you can use the web version and download the desktop side at the same time. Windows, Linux, and Mac platforms are all supported!

Experience address : Eolink-integrated API R&D management platform

Not much to say, let me directly introduce a few practical function points that I often use.

Actual combat experience function 1: One-click import of data sources from multiple platforms

Eolink provides a one-click import function. I exported the interface documents previously tested with postman from postman to json format

in Eolink. Data in products such as Swagger, RAP, and YAPI are quickly migrated to Eolink.

After selecting the JSON file to be imported, a task list queue will pop up on the right, where you can view the import status and download.

After importing, you can see the standard interface information in Json format imported from postman in the root directory of the project, and it is loaded and rendered in Eolink. Click the interface to perform functional testing or share the link to the front-end partners for interface joint debugging.

Practical experience function 2: upload API document synchronization based on IDEA plug-in

Eolink supports the IDEA plug-in method, which can parse JAVA methods into API documents, analyze method input and output parameters and automatically generate comments, and upload API information to Eolink services. At present, the plug-in has entered the IDEA market, search for "apikit" in the IDEA plug-in market, find the "Eolink ApiKit" plug-in and install it.

It should be noted that all versions of IDEA from March 2020 to the present are currently supported

I have already installed it here, so I will not reinstall it. After the installation is complete, IDEA needs to be restarted. After the restart is complete, you need to select Eolink Setting in Preferences to configure the upload parameters.

Parameter acquisition method : SpaceKey and ProjectHashKey parameters can be obtained through the url path of the Eolink web version.

After obtaining, you need to configure the following in IDEA

After configuration, it can be used in IDEA. Here, take the page interface method under Controller as an example.

You can see the comments generated by the plug-in above the method, and you can add other information by yourself.

  /**
   * @eo.name page
   * @eo.url /page
   * @eo.method get
   * @eo.request-type formdata
   * @param params
   * @param tousuxinxi
   * @param request
   * @return R
   */
  @RequestMapping("/page")
  public R page(@RequestParam Map<String, Object> params,TousuxinxiEntity tousuxinxi,
HttpServletRequest request){
    
    
String tableName = request.getSession().getAttribute("tableName").toString();
if(tableName.equals("yonghu")) {
    
    
   tousuxinxi.setYonghuming((String)request.getSession().getAttribute("username"));
}
      EntityWrapper<TousuxinxiEntity> ew = new EntityWrapper<TousuxinxiEntity>();
PageUtils page = tousuxinxiService.queryPage(params, MPUtil.sort(MPUtil.between(MPUtil.likeOrEq(ew, tousuxinxi), params), params));

      return R.ok().put("data", page);
  }

After the writing is completed, it can be uploaded to the Eolink server

You can see that the upload was successful. As for why it was not uploaded to a certain project, I think it is because of the path configuration problem. Due to time constraints, I will study it later. You are welcome to communicate or tell me in the comment area.

Experience address : Eolink-integrated API R&D management platform

Actual combat experience function 3: full-featured and concise API debugging page

On the API editing test page, API document information is automatically generated by manually creating or importing JSON and other format files, and manually creating a new one or selecting a project directory and filling in IP, port, request method, interface basic information, request parameters, etc. Here, the host
IP port information is recommended to be configured in the global environment.

We can click on the "Environment" menu on the left to set the general global project environment and parameters here

After setting, click the input box on the right side of the small eye to switch on the API interface edit call page. Click the small eyes to view the current global variables and detailed information about the environment, just select the environment path of the global configuration.

Click the send button to view the result set returned by interface debugging

Actual combat experience function 4: Analysis of interface test cases

On the API editing test case page, you can launch a test on the API interface with one click, and there is also a special test editor that can directly write JSON and XML data, and can also support automatic generation of test data and custom request parameters.

After the setting is complete, return to the list and click the batch test to see the test results

The failure here is caused by the inability to access the company network at home

This is an example of a successful test. Here you can see the specific returned status, time-consuming, pass rate, execution times, and other indicators.

summary

After using Eolink for a period of time, I feel good about it. I also shared this useful API development and testing tool with the front-end partners. Now our projects use Eolink for interface testing and management, and the overall feedback is good. . It saves the maintenance and writing of traditional interface documents, reduces a certain amount of workload and communication costs, and also helps to improve teamwork.

The most important thing is that many developers and testers are using it. There is a special Eolink technology exchange group. There are many enthusiastic teachers in the group. If you encounter some questions, you can directly ask them in the group. There is also Eolink professional technical support and help. You must click here great.

Experience address : Eolink-integrated API R&D management platform