Testing to determine how the front-end or back-end problem

Background problem

XXXException at at is the background formatting problems

1, find the log file on the server above

2, a log with a tail -f

3, at the front end to recreate the bug

4, to observe the log, if there is a clear exception, and that is the background error

5, the interface return code that is 500+ server issues, background issues.

 

Case

1, return unwanted messages interface documentation, parameters are case sensitive, inconsistent letters spelling errors, int or string and interface documentation.

2, the front end of the identification value can not return, after consulting with the background field expansion to meet the needs of the distal end

3, should return 0 records, but all returned, should return one record, but returned multiple records

4, should return ordered data, but the data returned disorder

5, the result of an incorrect page (not the number of pages, first page, second page, third page)

6, when too much data is not optimized SQL interfaces lead to long response time, overtime

 

Front-end problem

Front-end interface issues in general is a problem, but as the development of new requests to join in the url parameter, but there is no interface documentation error in the written part of the backend error.

Like the general layout and display the page in question belong to the front-end problem

Here to share a summary of Gangster: train

 

Guess you like

Origin www.cnblogs.com/cheneyboon/p/11530963.html