I. Introduction
In the process of using jmeter for interface testing, do you often encounter many problems, but you have no idea where to start? This is a very headache for beginners. Here, combined with the author's experience, the following methods are summarized.
2. Debugging problems by viewing the running logs
After writing the script, you can try running it first, as shown in the figure below. Click the small yellow triangle to display the execution log view interface. Pay attention to whether there are any errors. If there are errors, handle the errors in the execution log first.
3. Debugging problems by adding an inspection result tree
1. Check whether the request information is correct: including the requested protocol, request method, request address, requested data and other information
2. View the response message and check the interface development documentation
View the result tree-->Error interface-->Response data
3. Check the interface development documentation to find the relevant information returned by the interface and the description of the prompt information.
Positioning problem: Error 45065 here is because the same content was sent in bulk twice.
Solve the problem: Replace the uploaded image in the interface 2. Upload image to obtain url interface with a new image.
Executed again, the return status code is 0, indicating that the sending is successful.
4. Debugging the problem by adding a debug sampler
The association of the interface is a very important point in the debugging script. We can use the debugging sampler to check whether the associated data has been obtained. If the value is obtained, it will be displayed in the debugging sampler, as shown in the figure:
5. Enable the user agent and debug the problem using the fiddler packet capture tool.
If it is a web page interface, you can use fiddler to assist in debugging. Take https://www.baidu.com/s?wd=software testing as an example
1. Write a test script. Note: Baidu needs to add the User-Agent header.
2. Start fiddler
3.http default request, add proxy service
4. View the results: Execute it once in jmeter, and then use fiddler to view the results
Finally, I would like to thank everyone who reads my article carefully. Reciprocity is always necessary. Although it is not a very valuable thing, if you can use it, you can take it directly:
This information should be the most comprehensive and complete preparation warehouse for [software testing] friends. This warehouse has also accompanied tens of thousands of test engineers through the most difficult journey. I hope it can also help you!