How Do I Fill in Packets?
A packet is a core configuration item of CPTS.
The process of sending a packet: A click operation is edited to a code stream complying with protocol specifications and carrying a user's request before the code stream is sent to a third party, leading to a correct or failed response. A correct response indicates that the operation is successful, and a failed response provides tips for rectifying the problem.
CPTS supports packets in the following request types: GET, POST, PATCH, PUT, and DELETE. The following describes how to fill in packets.
- Before a pressure test, confirm the request type of an operation.
Taking queries as an example, query messages are GET requests. Therefore, set the request mode to GET during configuration.
- What do I do if my request messages require parameter input?
If it is a registration request, users need to fill in required fields. Packet capturing (using Wireshark) helps users learn how the request is sent, what the body format is, and how the request is transmitted to third-party application programming interfaces (APIs). Fill in the packet based on the captured content.
Generally, a request such as registration uses the POST method. After this method is selected, the following information is displayed.Figure 1 Editing requests
Figure 2 Packet content
For the standard HTTP or HTTPS format, fill in the packet header based on the captured content. The packet body specifies the request content, which depends on the service to be tested. The body can be a game login request or a registration request. All packets can be edited for pressure tests as long as the request complies with the HTTP or HTTPS protocol.
The preceding example is applicable to PATCH, PUT, and DELETE methods. First, confirm the protocol type, request method, and request link of the application to be tested, and then confirm the content in a request.