When an interface has an exception, how do you analyze the exception?

Interface testing is common bug

Routine error , The interface is not implemented , Didn't return the result as agreed , Boundary value processing error, etc ;

Enter the outlier （ Null value 、 Special characters 、 Beyond the agreed length, etc ）, Wrong interface , No encapsulation ;

Wrong parameters entered 、 Multiple input 、 Less input parameters , Possible interface errors ;

Security issues , Such as plaintext transmission 、 The returned result contains sensitive information , No verification of user identity information , No malicious request interception, etc ;

Performance issues , For example, the interface inserts multiple identical operations simultaneously , Response time is too long , There is a bottleneck in the pressure test of the interface .

When an interface exception occurs , How to analyze and handle ：

Grab the bag first , use fiddler Tool grab bag ;

Or on the browser F12 Debugging tools ;

APP What I said , have access to Fiddler Do the agent , Set up a proxy through the mobile phone to see the request and return message ;

View backend logs , Such as Linux The system goes through xhell Connect to the server , Check the interface log , Check if there is any error message

（ command ：tail -f Log files ）