How Do I Fill in Packets?

Packets refer to all click operations on the website. 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.

CodeArts PerfTest supports packets in the following request types: GET, POST, PATCH, PUT, and DELETE. The following describes how to fill in packets.

1. Before a pressure test, confirm the request type of an operation.

   Taking queries as an example, query messages are GET requests. You can set the request mode to GET during configuration.

2. What do I do if my request messages require parameter input?

   If a request involves various fields, press F12 or use a packet-capturing tool (such as Wireshark) to check how a packet is requested, what the body format is, and how the request is transmitted to third-party application programming interfaces (APIs). Then, fill in the packet to be tested according to the actual service.

   Generally, such a request uses the POST method. After this method is selected, the following information is displayed.

   Figure 1 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 also 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.