How to locate a bug in a Web test

1. Packet Capture analysis

Web During the test , how to judge the front-end bug or the back-end bug? The clutch analysis can be carried out by grasping the package tool.

Most of BrowserHave their own grab bag plug-ins, such as Firefox's Firebug plugin, Chrome, theRapid mode, Sogou high-speed mode comes with the Developtools plug-in, F12 open capture, in the network can see the current page sent every HTTP request. In general, we can determine the bug by requesting the interface, the parameters and the response, and we can also debug the code in the browser's console. (1) The Request interface URL is correct if the request interface URL is incorrect, the front-end Bug, (2) The parameters in the HTTP request is correct if the parameters in the HTTP request is incorrect, the front-end Bug, (3) If the interface URL and parameters are correct, see if the response content is correct if this situation The response content is incorrect, then the backend bug. (4) If the JS base is better, you can also enter the JS code in the browser's console to debug in addition, in addition to the browser's own grab plug-in, you can also use other capture software, such as Fiddler, Charles, HttpWatch, Wireshark and so on. 2. Back-end bugs, how to pinpoint where the problem is, how to accurately describe the bug? (1) Check the newspaper error log to check the error log, through the log analysis, need to have some experience, and a certain code base, in order to better locate the problem. (2) View DatabaseData to understand the function of the data table structure, testing process, review the database data, confirm the correctness of the data. (3) Check if the cache (such as Memcache, APC, Redis, etc.) is correct

How to locate a bug in a Web test