How to distinguish between front-end and back-end problem issues?
The reception bug is often a function, interface and compatibility with other relevant;
Background bug and logic, performance and safety related.
Data-related errors, scheduling problem mostly is a background issue;
For APP page toast may be prompted to back, possibly to the APP.
(1) Check that
Between front-end and back-end are interconnected by an interface file, testers can view the interface file, to distinguish between front-end and back-end bug.
(2) Analysis
a, check what data is requested? What feedback data is?
To perform packet capture by capture tool.
Most browsers have built-in packet capture plug-ins, such as FireBug in FireFox plug-in, Chrome, 360 rapid mode, Sogou high-speed mode comes DevelopTools plug (F12 open), can be seen in NetWork sent per the current page a http request. Request interface, parameter passing, in response to determination of three parts Bug, further, may be positioned in js code debugging console browser.
1) Request Interface URL is correct
If the URL request interface is incorrect, the front end of the Bug;
2) http request parameters are correct
If the http request parameter is incorrect, the front end of the Bug;
3) If the interface parameters are correct URL and view the content of the response is correct
If the content of the response in this case is not correct, for the back-end Bug.
4) If the JS good foundation, you can also enter the JS code in the browser console for debugging.
b, according to the file interface, check the data is correct.
If the data sent is correct, but the background of the feedback data is not consistent with demand, and that is the background of the problem.
If the front end when there is no request interface, or send a request and demand does not match the data, and that this time is the problem of the front end.