How Are Packets Filled In?
The packet is a core configuration item of Cloud Performance Test Service (CPTS). What is a packet?
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 different third parties, 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 with the following request types: GET, POST, PATCH, PUT, and DELETE. How are packets filled in?
- Before a pressure test, confirm the request type of an operation.
Taking query as an example, query messages are GET requests. Therefore, set the type of query messages 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 (such as by Wireshark) can be used to learn how a message is sent, what the body format is, and how the message is transmitted to third-party interfaces. Fill in the packet based on the captured contents.
Generally, a request such as registration uses the POST method. After this method is selected, the following information is displayed.Figure 1 Editing elements
Figure 2 Headers
Figure 3 Packet content
For the standard HTTP or HTTPS format, the packet header can be filled in based on the captured contents. The packet body specifies the content to be requested, which depends on the service to be tested. The body can be a game login request or a registration request. All packets that comply with HTTP or HTTPS specifications can be edited for pressure tests.
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 requested content.