Tell me about some of the points I have to pay attention to when testing the interface:
1, interface return: Data format is consistent with the expected. For example: requires that data be returned in JSON format, the key of the JSON data is named correctly, and the corresponding value is consistent with the database. Whether the data that needs to be converted is converted correctly, such as whether the timestamp is converted correctly to the data in the time format.
2, fault-tolerant processing: When the parameter value error, the interface can give the corresponding return, such as 404, 500 and so on.
3, parameter Boundary value processing: If the passed parameter is large enough or negative, the interface can be handled normally.
4, security: such as external exposure of the interface, whether to increase the access restrictions. Whether the parameter has been processed such as anti-SQL injection.
5, Performance: whether to meet the performance requirements.
6. Other:
Whether to use post requests when passing important data such as passwords.
Uploading a class request not only depends on the response of the interface, but also on whether the database insert is successful or not, and whether the data is consistent with the submission.
Request body, request header fault tolerant processing.
(Transferred from: http://blog.csdn.net/silencemylove/article/details/50605982)
How to do Web interface testing