Background of the project:
Our in-vehicle equipment needs to be authorized, and our software can only be used after the authorization is completed. In order to verify the stability of the service, we need to do a pressure test on the authorized interface, request an interface every 5 seconds, and test for dozens of hours. See below How many requests succeeded and how many failed.
Because there are no restrictions on the requested interface, different user requests are not required, so the same device can be used to request the interface once every 5 seconds.
Interface request sequence:
1: HTTP header manager
2: HTTP request:
The message body parameters here are: CDKey, appid, imeiTwo, sig, type;
CDKey and appid are developed and provided, imeiTwo is the device number, and the type type can be obtained from the interface document.
Among them, sig is concatenated with all the parameters except appid and sig, and then appends the value of appscrect (provided by appscrect development) for md5 encryption, with the key in the front and the value in the back. :
3: Add timer
The requirement is to request once every 5 seconds, so the parameter set by the added fixed timer is 5000 milliseconds. (1 second = 1000 milliseconds)
4: Add threads (because a device requests one every 5 seconds, so the number of virtual users is 1, and the number of cycles is set to the number of times to be tested, here I probably set the number of times to 3060):
5: After saving the test plan, use the non-GUI mode to test, and then analyze the results after the test is completed (in order to analyze the failed requests that can be viewed in the future, you can search for information on how to view non-GUI mode response data that is empty under Baidu Next, or see what I wrote in the "Caching track (batch track) upload interface test" document mentioned"
testing report
