Table of contents
1. Under what circumstances should the interface test be carried out?
Foreword:
Interface testing is an important type of testing used to verify the functionality, performance, and reliability of an application interface.
1. Under what circumstances should the interface test be carried out?
1. The project is in the development stage, whether the front-end and back-end joint debugging interfaces are available;
2. There is an interface requirement document, the development has been completed and the joint debugging (can be transferred to the test), before the functional test is launched;
3. Before the version goes online, conduct an overall regression test to check whether the interface is abnormal (such as 404, etc.). Capture the package of the version ready to go online, and check whether the server address is correct;
4. After the version function is stable, the interface will be automated;
5. It can also be used in security testing, performance testing, etc.
2. How to test the interface
Send an http request for testing. First, we need to see what the request method is get, post or other requests, and then enter the URL address, such as a get request to Baidu.
The post request requests to log in, and the post request generally needs to pass parameters, so we need to add the login name and password to the body
return result:
Parameter name, type, description Return description, String, return 0 if the sending is successful, and return "ERROR&&corresponding error message" if the sending is unsuccessful.
3. Interface test case design
Interface testing is a functional test without an interface, and the idea of designing use cases is the same as that of functional testing (only one focuses on testing the front-end page, and the other focuses on testing the back-end interface)
1. Input parameter test: Test the input parameters, which can also be said to be a test based on the assumption that the interface parameters are incorrect, to ensure that the interface handles any type of input accordingly: the input parameters are legal, and the input parameters are illegal , the input parameter is empty, the input parameter is null, and the input parameter is too long;
2. Functional test: whether the interface satisfies the functions provided, which is equivalent to a normal test;
3. Abnormal scenarios, such as: request timeout, rapid continuous click, request failure (task type, whether the task can be re-sent after failure).
4. Interface testing tools
I generally use the domestic interface document testing tool apipost, and the pressure testing tool jmeter.
As someone who has been here, I also hope that you will avoid some detours. Here I will share with you some necessities on the way forward for automated testing, hoping to help you. (WEB automated testing, app automated testing, interface automated testing, continuous integration, automated test development, big factory interview questions, resume templates, etc.), I believe it can make you better progress!
Just leave [Automated Test] [Automated Test Communication]: 574737577 (remark ccc) 
http://qm.qq.com/cgi-bin/qm/qr?_wv=1027&k=GlobQko2NS5bQu3wyjjJHcr4B9Vib3pp&authKey=2wt3S40B0Wtk%2BmHrtsk9Nj1MLWr7ipmS7cjW 3fAszz%2F11J8wOREcgAJDvHBM6TYa&noverify=0&group_code= 574737577
