Table of contents
In terms of testing the interface
The more learning tools, the better. Today, take a look at APIPOST, an integrated testing tool for documentation, debugging, and Mock testing.
Known as: ApiPost = interface debugging + rapid generation of interface documents + standardized management of interface documents + Mock API + interface process testing.
After logging in, the effect is better. If you don’t log in, it will keep reminding you to log in, which is annoying.
In terms of testing the interface
There is nothing to say in this regard. If you just want to test the interface, you can use postman directly . How familiar
Just write an interface test
generate documentation
This function is quite attractive to me, I have a short experience~~~
Previously, swagger documents were needed for front-end and back-end cooperation, and apipost can directly generate documents. I think it will be better after using it proficiently?
You can also fill in the interface description.
If you want to add a successful response case and a failed response case, just click in and fill in, and it will be included when the document is generated.
After saving your test, click Share Document. If you want to share multiple interfaces, click Create Custom Share.
Click directly to share the customization to share
After sharing, that's basically it.
Mock service
Not familiar with front-end testing, if you want to know, go directly to the official website
Using Mock in APIPOST - APIPOST usage documentation
Summarize
There are many other functions, such as script execution and process testing. Generally speaking, the functions are powerful, and some functions are worth exploring.
If it's just for testing the interface, it doesn't matter if you choose postman or it, it depends on the individual.
If you need to use more functions, you can spend a little time learning apipost.