Request processing method and device, equipment and readable medium

Abstract

The embodiment of the invention provides a request processing method and device, equipment and a medium. The method comprises the steps that before multiple pieces of request information are sent to a to-be-tested interface of a to-be-tested system, the multiple pieces of request information are matched with preset fields and values of the preset fields; in response to successful matching of one or more request information in the multiple pieces of request information with the preset field and the value of the preset field, obtaining respective request attributes of the one or more request information by analyzing the one or more request information, the request attributes being editable; and sending one or more pieces of request information with the edited request attributes to a to-be-tested interface of the to-be-tested system in response to the fact that the request attributes are edited. In this way, targeted testing of specific functions can be achieved, stability of the system functions is guaranteed, and the abnormal influence range is narrowed.

Description

Technical Field

[0001] The exemplary embodiments disclosed herein generally relate to the field of computer technology, and more specifically, to methods, apparatus, devices, and computer-readable storage media for request processing. Background Technology

[0002] As architectures become microservice-based, the number and complexity of interfaces increase. To ensure correct and error-free interactions between external systems and between different subsystems, it is necessary to test these interfaces in advance. For example, preheating methods, traffic recording, and traffic replay can be used to test the interfaces. Summary of the Invention

[0003] In a first aspect of this disclosure, a method for request processing is provided, comprising: matching multiple request messages with predetermined fields and values ​​of predetermined fields before sending multiple request messages to a test interface of a system under test; in response to one or more of the multiple request messages successfully matching with the predetermined fields and values ​​of predetermined fields, obtaining request attributes of each of the one or more request messages by parsing the one or more request messages, wherein the request attributes are editable; and in response to the completion of the editing of the request attributes, sending the one or more request messages having the edited request attributes to the test interface of the system under test.

[0004] In a second aspect of this disclosure, an apparatus for request processing is provided, comprising: a matching module configured to match multiple request messages with predetermined fields and values ​​of predetermined fields before sending multiple request messages to a test interface of a system under test; a parsing module configured to, in response to one or more request messages among the multiple request messages successfully matching with predetermined fields and values ​​of predetermined fields, obtain request attributes of each of the one or more request messages by parsing the one or more request messages, wherein the request attributes are editable; and a sending module configured to, in response to the completion of editing of the request attributes, send one or more request messages having the edited request attributes to the test interface of the system under test.

[0005] In a third aspect of this disclosure, an electronic device is provided. The electronic device includes at least one processing unit; and at least one memory coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, the instructions causing the electronic device to perform the method of the first aspect of this disclosure when executed by the at least one processing unit.

[0006] In a fourth aspect of this disclosure, a computer-readable storage medium is provided. This computer-readable storage medium stores a computer program that can be executed by a processor to perform the method according to a first aspect of this disclosure.

[0007] In a fifth aspect of this disclosure, a computer program product is provided, including computer-executable instructions, wherein the computer-executable instructions, when executed by a processor, implement the method of the first aspect.

[0008] It should be understood that the description in the Summary of the Invention section is not intended to limit the key or essential features of the embodiments of this disclosure, nor is it intended to restrict the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0009] In the following detailed description, in conjunction with the accompanying drawings, the above and other features, advantages, and aspects of the various implementations of this disclosure will become more apparent. In the accompanying drawings, the same or similar reference numerals denote the same or similar elements, wherein:

[0010] Figure 1 A schematic diagram of an example environment in which embodiments of the present disclosure can be implemented is shown;

[0011] Figure 2 A flowchart of a request processing procedure according to some embodiments of the present disclosure is shown;

[0012] Figure 3 A schematic diagram of a process for traffic recording according to some embodiments of the present disclosure is shown;

[0013] Figure 4 A schematic diagram of a process for traffic playback according to some embodiments of the present disclosure is shown;

[0014] Figure 5 A block diagram of an apparatus for request processing according to some embodiments of the present disclosure is shown; and

[0015] Figure 6 A block diagram of an electronic device in which one or more embodiments of the present disclosure may be implemented is shown. Detailed Implementation

[0016] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0017] In the description of embodiments of this disclosure, the term "comprising" and similar terms should be understood as open-ended inclusion, i.e., "including but not limited to". The term "based on" should be understood as "at least partially based on". The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment". The term "some embodiments" should be understood as "at least some embodiments". Other explicit and implicit definitions may also be included below.

[0018] It should be noted that the acquisition, storage, and application of user personal information involved in the technical solution disclosed herein comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0019] It is understood that before using the technical solutions disclosed in the various embodiments of this disclosure, users should be informed of the types, scope of use, and usage scenarios of the personal information involved in this disclosure through appropriate means in accordance with relevant laws and regulations, and user authorization should be obtained.

[0020] For example, in response to receiving a user's active request, a prompt message is sent to the user to clearly inform the user that the requested operation will require the acquisition and use of the user's personal information, thereby enabling the user to choose whether to provide personal information to the software or hardware such as electronic devices, applications, servers or storage media that perform the operation of the technical solution disclosed herein, based on the prompt message.

[0021] As an optional but non-restrictive implementation, in response to a user's active request, a prompt message can be sent to the user, for example, via a pop-up window, where the prompt message can be presented in text format. Furthermore, the pop-up window can also include a selection control allowing the user to choose whether to "agree" or "disagree" to provide personal information to the electronic device.

[0022] Some exemplary embodiments of this disclosure will now be described with reference to the accompanying drawings.

[0023] Figure 1 A schematic diagram of an example environment 100 in which embodiments of the present disclosure can be implemented is shown. Figure 1 In environment 100, electronic device 110 can obtain the raw traffic data of the interface to be tested during the interaction between it and server 120 through the interface to be tested.

[0024] Multiple request messages are used to test the interface under test, and test cases are constructed based on raw traffic data, where the test cases include the request messages. Furthermore, the electronic device 110 can edit the relevant attributes of the request messages and send the edited request messages with the relevant attributes to the interface under test for testing.

[0025] Electronic device 110 can be any type of computing device, including terminal devices or server devices. Terminal devices can be any type of mobile terminal, fixed terminal, or portable terminal, including mobile phones, desktop computers, laptop computers, notebook computers, netbook computers, tablet computers, media computers, multimedia tablets, personal communication system (PCS) devices, personal navigation devices, personal digital assistants (PDAs), audio / video players, digital cameras / camcorders, positioning devices, television receivers, radio receivers, e-book devices, gaming devices, or any combination thereof, including accessories and peripherals of these devices or any combination thereof. Server devices can include, for example, computing systems / servers, such as mainframes, edge computing nodes, electronic devices in cloud environments, etc.

[0026] Server 120 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks, and big data and artificial intelligence platforms. Server 120 may include, for example, computing systems / servers such as mainframes, edge computing nodes, computing devices in cloud environments, etc.

[0027] A communication connection can be established between electronic device 110 and server 120. The communication connection can be established via wired or wireless means. The communication connection may include, but is not limited to, Bluetooth connection, mobile network connection, Universal Serial Bus (USB) connection, Wireless Fidelity (WiFi) connection, etc., and the embodiments disclosed herein are not limited in this respect.

[0028] It should be understood that Figure 1 The components and arrangements shown in environment 100 are merely examples, and a computing system suitable for implementing the exemplary implementations described in this disclosure may include one or more different components, other components, and / or different arrangements. Implementations of this disclosure are not limited in this respect.

[0029] As explained above, when testing interfaces, warm-up methods or traffic recording and playback methods can be used. However, warm-up methods (i.e., hot deployment of plugins) lack specificity. For example, they cannot be triggered for a specific scenario, especially for testing certain specific functions. Traffic recording and playback methods also lack specificity, require a large amount of data, waste system resources, and may even generate dirty data for the system. Furthermore, when testing certain specific functions, triggering the method can only be done after the function is in use, which may affect the functionality's usability.

[0030] For example, when testing a certain function, if the completeness of the function and the accuracy of the data cannot be guaranteed, it may cause data rollback or even interfere with historical data, resulting in irreversible losses. Therefore, it is necessary to conduct precise testing on this function to ensure the stability of the system and minimize the scope of the impact of anomalies.

[0031] This disclosure provides a scheme for request processing. In embodiments of this disclosure, before multiple request messages are sent to the interface under test of the system under test, the multiple request messages are first matched against predetermined fields and their values ​​to filter out one or more request messages. Further, the filtered one or more request messages are parsed to obtain request attributes for each of the one or more request messages, wherein the request attributes are editable. Finally, in response to the completion of request attribute editing, the one or more request messages with the edited request attributes are sent to the interface under test of the system under test for testing.

[0032] In this way, qualified request information can be filtered from multiple request information by predefined fields and their values ​​to determine the request information to be used for testing the interface under test. The request attributes of the filtered request information can be edited to test the interface under test in different scenarios based on the request information with the edited request attributes. This enables targeted testing of specific functions, ensures the stability of system functions, and reduces the scope of anomalies.

[0033] The following description will continue with reference to the accompanying drawings, which will provide some exemplary embodiments of this disclosure.

[0034] Figure 2 A flowchart of a request processing procedure 200 according to some embodiments of the present disclosure is shown. For ease of understanding, the following will be combined with... Figure 1 Let's take a look. For example, process 200 can be implemented at electronic device 110.

[0035] In box 210, before multiple request messages are sent to the test interface of the system under test, electronic device 110 matches the multiple request messages with predetermined fields and the values ​​of predetermined fields.

[0036] The system under test can be deployed on one or more servers 120. When testing the interface under test of the system under test, the electronic device 110 needs to record relevant traffic data (such as request information), and then perform traffic playback based on the recorded traffic data to test the interface under test of the system under test.

[0037] The system under test can have one or more test interfaces. When request information requests data from server 120 through one or more test interfaces, the request information received by each test interface can have key fields and key field values ​​that are different from those received by other test interfaces. By configuring the key fields and key field values, the request information required by the corresponding interface can be filtered from multiple request information. For example, the key fields and key field values ​​corresponding to different interfaces can be represented by configuring predefined fields and predefined field values.

[0038] In some embodiments, different predefined fields and their values ​​can be set for different interfaces to be tested. Electronic device 110 can filter the request information required for the interface to be tested from multiple request messages by matching the fields and field values ​​in multiple request messages with the predefined fields and their values.

[0039] In some embodiments, the predefined fields and their values ​​can be defined by obtaining traffic entry points or by relying on the User Messaging Platform (UMP).

[0040] For example, an interceptor may be installed in the electronic device 110. By configuring predefined fields and their values ​​in the interceptor, the fields and values ​​of multiple request messages are matched with the predefined fields and their values ​​to filter out the required request messages.

[0041] In some embodiments, the matching of multiple request messages with predetermined fields and their values ​​by the electronic device 110 can be remotely triggered. For example, in response to receiving a remote triggering instruction, the electronic device 110 can match multiple request messages with predetermined fields and their values ​​before the multiple request messages are sent to the interface under test of the system under test. It should be understood that the remote triggering method can adopt any method in the related art, and the embodiments of this disclosure are not limited thereto.

[0042] In box 220, electronic device 110 responds to one or more request messages from a plurality of request messages that successfully match a predetermined field and the value of the predetermined field by parsing the one or more request messages to obtain the request attributes of each of the one or more request messages. The request attributes are editable.

[0043] In some embodiments, after obtaining the request attributes of one or more request messages by parsing one or more request messages, the electronic device 110 may present a first interface and display the request attributes on the first interface. For example, in the first interface, the electronic device 110 may present the request attributes in the form of a list.

[0044] In some embodiments, request attributes may include, but are not limited to, request headers, request parameters, and the requested Internet Protocol address. When displaying request attributes, a request can be presented in a list format, using the request headers, request parameters, and the requested Internet Protocol address as its three dimensions.

[0045] It should be understood that, for a set of predefined fields and their values, when presenting request attributes, the request information can be presented in a list format using three dimensions: request headers, request parameters, and the requested Internet Protocol address. For multiple sets of predefined fields and their values, when presenting request attributes, the request attributes can be grouped based on the predefined fields and presented in multiple groups. Each group can be presented in the same way as a set of predefined fields and their values.

[0046] In some embodiments, an editing control may be presented on the first interface. Triggering the editing control allows editing of the requested attribute presented on the first interface. The electronic device 110 may, in response to receiving an editing request for the requested attribute (or the editing control being triggered), present a second interface, in which the requested attribute is displayed, and the requested attribute presented on the second interface can be edited.

[0047] For example, you can switch between different scenarios by editing the request parameters in the request properties, or connect to different servers by editing the Internet Protocol Address (IP address) of the request in the request properties.

[0048] In some embodiments, the second interface also presents a first control and a second control. The first control is used to configure the duration of the request information, and the second control is used to configure the number of times the request information is invoked. The electronic device 110 can send one or more request messages with edited request attributes to the interface under test of the system under test based on the configured duration and / or the configured number of invocations. Thus, the stress resistance of the interface under test can be tested by setting the duration and / or the number of invocations.

[0049] In some embodiments, to facilitate subsequent traffic replay for testing the interface under test, the parsed request attributes and request information containing those attributes can be saved. For example, they can be saved locally or in the cloud.

[0050] In box 230, in response to the completion of the editing of the request attributes, electronic device 110 sends one or more request messages with the edited request attributes to the interface under test of the system under test.

[0051] In some embodiments, the request attributes of the request information can be edited by selecting only some attributes or by editing all attributes. In the case of editing only some attributes, the electronic device 110 needs to send the complete request information to the interface under test, that is, send both the edited and unedited attributes of the request information to the interface under test.

[0052] The above process 200 can be divided into two stages: traffic recording and traffic playback. The following will introduce the scheme for request processing disclosed herein through these two stages: traffic recording and traffic playback.

[0053] Figure 3 A schematic diagram of a process 300 for traffic recording according to some embodiments of the present disclosure is shown. Process 300 can be performed by an electronic device 110.

[0054] In box 310, the interceptor captures multiple request messages. In box 320, the interceptor parses the request attributes of the multiple request messages to see if they match the traffic recording rules. In box 330, when the request attributes of the multiple request messages match the traffic recording rules, the interceptor parses the request attributes of the matching request messages. In box 340, when the request attributes of the multiple request messages do not match the traffic recording rules, the request messages are not saved. In box 350, after parsing the request messages, the interceptor saves the parsed request attributes and the request messages containing those attributes.

[0055] In some embodiments, traffic recording rules may be matched with predetermined fields and their values.

[0056] Figure 4A schematic diagram of a process 400 for traffic playback according to some embodiments of the present disclosure is shown. Process 400 can be performed by electronic device 110.

[0057] In box 410, in response to the user-selected request entry point (the interface to be tested), the request attributes of multiple request information are parsed and displayed to the user in categories. In box 420, in response to the user's editing of request attributes, the request attributes are edited accordingly. In box 430, in response to the request frequency set by the user and the IP address of the requested server 120, data is requested from the corresponding server 120 based on the request frequency and IP address.

[0058] In summary, before multiple request messages are sent to the interface under test of the system under test, the request messages are first matched against predetermined fields and their values ​​to filter out one or more request messages. Further, the filtered request messages are parsed to obtain their respective request attributes, which can be edited. Finally, in response to the edited request attributes, the one or more request messages with the edited attributes are sent to the interface under test of the system under test for testing. In this way, request messages that meet the criteria can be filtered from multiple request messages using predetermined fields and their values ​​to determine the request messages used for testing the interface under test. The request attributes of the filtered request messages can be edited to test the interface under test in different scenarios based on the request messages with the edited attributes. This allows for targeted testing of specific functions, ensuring system stability and minimizing the impact of anomalies.

[0059] Figure 5 A block diagram of a request processing apparatus 500 according to some embodiments of the present disclosure is shown. The apparatus 500 may be implemented as or include an electronic device 110.

[0060] Apparatus 500 includes a matching module 510 configured to match multiple request messages with predetermined fields and their values ​​before sending them to the interface under test of the system under test. Apparatus 500 also includes a parsing module 520 configured to, in response to one or more request messages successfully matching with the predetermined fields and their values, parse the one or more request messages to obtain individual request attributes, wherein the request attributes are editable. Apparatus 500 further includes a sending module 530 configured to, in response to the completion of request attribute editing, send one or more request messages with the edited request attributes to the interface under test of the system under test.

[0061] In some embodiments, the apparatus 500 further includes a first presentation module configured to present a first interface; and to present request attributes in the first interface.

[0062] In some embodiments, the apparatus 500 further includes a second presentation module configured to present a second interface in response to receiving an edit request for a requested attribute; and to present the requested attribute in the second interface, wherein the requested attribute presented in the second interface is editable.

[0063] In some embodiments, a first control and a second control are also presented in the second interface. The first control is used to configure the duration of the request information, and the second control is used to configure the number of times the request information is invoked. The sending module 530 is also configured to send one or more request information with edited request attributes to the interface under test of the system under test based on the duration and / or the number of invocations.

[0064] In some embodiments, request attributes include request headers, request parameters, and the requested Internet Protocol address.

[0065] In some embodiments, the matching module 510 is further configured to, in response to receiving a trigger instruction, match multiple request messages with predetermined fields and the values ​​of predetermined fields before multiple request messages are sent to the test interface of the system under test.

[0066] In some embodiments, the apparatus 500 further includes a storage module configured to save request attributes.

[0067] The modules included in device 500 can be implemented in various ways, including software, hardware, firmware, or any combination thereof. In some embodiments, one or more units can be implemented using software and / or firmware, such as machine-executable instructions stored on a storage medium. In addition to or as an alternative to machine-executable instructions, some or all of the units in device 500 can be implemented at least partially by one or more hardware logic components. By way of example, and not limitation, exemplary types of hardware logic components that can be used include field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-chips (SoCs), complex programmable logic devices (CPLDs), and so on.

[0068] Figure 6 A block diagram of an electronic device 600 in which one or more embodiments of the present disclosure may be implemented is shown. It should be understood that... Figure 6 The electronic device 600 shown is merely exemplary and should not be construed as limiting the functionality and scope of the embodiments described herein.

[0069] like Figure 6As shown, electronic device 600 is in the form of a general-purpose computing device. Components of electronic device 600 may include, but are not limited to, one or more processors or processing units 610, memory 620, storage device 630, one or more communication units 640, one or more input devices 650, and one or more output devices 660. Processing unit 610 may be a physical or virtual processor and is capable of performing various processes according to programs stored in memory 620. In a multiprocessor system, multiple processing units execute computer-executable instructions in parallel to improve the parallel processing capability of electronic device 600.

[0070] Electronic device 600 typically includes multiple computer storage media. Such media can be any available media accessible to electronic device 600, including but not limited to volatile and non-volatile media, removable and non-removable media. Memory 620 can be volatile memory (e.g., registers, cache, random access memory (RAM)), non-volatile memory (e.g., read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory), or some combination thereof. Storage device 630 can be a removable or non-removable medium and can include machine-readable media, such as flash drives, disks, or any other media that can be used to store information and / or data (e.g., training data for training) and can be accessed within electronic device 600.

[0071] Electronic device 600 may further include additional removable / non-removable, volatile / non-volatile storage media. Although not explicitly stated... Figure 6 As shown, disk drives for reading from or writing to removable, non-volatile disks (e.g., "floppy disks") and optical disk drives for reading from or writing to removable, non-volatile optical disks can be provided. In these cases, each drive can be connected to a bus (not shown) via one or more data media interfaces. Memory 620 may include computer program product 625 having one or more program modules configured to perform various methods or actions of various embodiments of this disclosure.

[0072] The communication unit 640 enables communication with other electronic devices via a communication medium. Additionally, the functionality of the components of the electronic device 600 can be implemented using a single computing cluster or multiple computing machines capable of communicating via communication connections. Therefore, the electronic device 600 can operate in a networked environment using logical connections to one or more other servers, network personal computers (PCs), or another network node.

[0073] Input device 650 can be one or more input devices, such as a mouse, keyboard, trackball, etc. Output device 660 can be one or more output devices, such as a monitor, speaker, printer, etc. Electronic device 600 can also communicate with one or more external devices (not shown) via communication unit 640 as needed. These external devices include storage devices, display devices, etc., and can communicate with one or more devices that enable user interaction with electronic device 600, or with any device that enables electronic device 600 to communicate with one or more other electronic devices (e.g., network card, modem, etc.). Such communication can be performed via input / output (I / O) interface (not shown).

[0074] According to an exemplary implementation of this disclosure, a computer-readable storage medium is provided that stores one or more computer instructions, wherein the one or more computer instructions are executed by a processor to implement the methods described above. According to an exemplary implementation of this disclosure, a computer program product is also provided, which is tangibly stored on a non-transient computer-readable medium and includes computer-executable instructions that are executed by a processor to implement the methods described above.

[0075] Various aspects of this disclosure are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products implemented according to this disclosure. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-readable program instructions.

[0076] These computer-readable program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that, when executed by the processing unit of the computer or other programmable data processing apparatus, they create means for implementing the functions / actions specified in one or more blocks of the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium that causes a computer, programmable data processing apparatus, and / or other device to operate in a particular manner. Thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing aspects of the functions / actions specified in one or more blocks of the flowchart and / or block diagram.

[0077] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions that execute on the computer, other programmable data processing apparatus, or other device to perform the functions / actions specified in one or more boxes of a flowchart and / or block diagram.

[0078] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of an instruction, which contains one or more executable instructions for implementing the specified logical function. In some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0079] Various implementations of this disclosure have been described above. The foregoing description is exemplary and not exhaustive, nor is it limited to the disclosed implementations. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described implementations. The terminology used herein is chosen to best explain the principles, practical applications, or improvements to technology in the market, or to enable others skilled in the art to understand the implementations disclosed herein.

Claims

1. A method for request processing, comprising: Before multiple request messages are sent to the interface to be tested of the system under test, the multiple request messages are matched with a predetermined field and the value of the predetermined field; In response to one or more of the multiple request messages successfully matching the predetermined field and the value of the predetermined field, the request attributes of each of the one or more request messages are obtained by parsing the one or more request messages, wherein the request attributes are editable; as well as In response to the completion of the editing of the request attribute, the one or more request messages with the edited request attribute are sent to the interface to be tested of the system to be tested.

2. The method according to claim 1, wherein after obtaining the request attributes in the request information by parsing the one or more request information, the method further includes: The first screen is displayed; as well as The requested attributes are presented on the first interface.

3. The method according to claim 2, further comprising: Upon receiving an edit request for the requested attribute, a second interface is displayed; as well as The request attributes are presented in the second interface, and the request attributes presented in the second interface are editable.

4. The method according to claim 3, wherein the second interface further presents a first control and a second control, the first control being used to configure the duration of the request information, the second control being used to configure the number of times the request information is invoked, and wherein sending the one or more request messages having the edited request attributes to the test interface of the system under test includes: Based on the duration and / or the number of calls, the one or more request messages with the edited request attributes are sent to the interface under test of the system under test.

5. The method according to claim 1, wherein the request attributes include request headers, request parameters, and the requested Internet Protocol address.

6. The method of claim 1, wherein matching the plurality of request information with the predetermined field and the value of the predetermined field comprises: In response to receiving a trigger command, before the plurality of request messages are sent to the interface to be tested of the system to be tested, the plurality of request messages are matched with the predetermined field and the value of the predetermined field.

7. The method according to claim 1, wherein after obtaining the respective request attributes of the one or more request information by parsing the one or more request information, the method further comprises: Save the requested attributes.

8. An apparatus for request processing, comprising: The matching module is configured to match the multiple request messages with a predetermined field and the value of the predetermined field before the multiple request messages are sent to the test interface of the system under test; The parsing module is configured to, in response to one or more of the plurality of request messages successfully matching the predetermined field and the value of the predetermined field, obtain the request attributes of each of the one or more request messages by parsing the one or more request messages, wherein the request attributes are editable; as well as The sending module is configured to send one or more request messages with the edited request attributes to the interface under test of the system under test in response to the completion of the editing of the request attributes.

9. An electronic device, comprising: At least one processing unit; as well as At least one memory, coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, the instructions causing the electronic device to perform the method according to any one of claims 1 to 7 when executed by the at least one processing unit.

10. A computer-readable storage medium having a computer program stored thereon, the computer program being executable by a processor to implement the method according to any one of claims 1 to 7.

11. A computer program product comprising computer-executable instructions, wherein the computer-executable instructions, when executed by a processor, implement the method according to any one of claims 1 to 7.

Images