Method, device and equipment for processing automation test data, and storage medium

Abstract

This invention relates to the field of automated testing technology, and provides a method, apparatus, device, and storage medium for processing automated test data, used to improve the efficiency of monitoring server anomalies and performance issues. The method for processing automated test data includes: performing automated testing on interface test cases in an interface test case file using a main thread to obtain execution results; connecting to a pre-created sub-thread and reading the server log information of the pre-created server after successful connection using a pre-created sub-thread; performing anomaly detection on the server log information using the sub-thread to obtain target anomaly log information; acquiring resource data from the pre-created server; and sending the target automated execution result file containing the execution results, the target anomaly log file containing the target anomaly log information, and the target server resource file containing the resource data to a pre-created feedback terminal according to a pre-defined sending method.

Description

Technical Field

[0001] This invention relates to the field of automated testing technology, and in particular to a method, apparatus, equipment, and storage medium for processing automated test data. Background Technology

[0002] In today's rapidly evolving software industry, software quality is a crucial factor in determining whether software meets user needs, and software testing is a vital means of ensuring software quality. With rapid software iteration cycles, traditional manual testing is increasingly unable to keep up with this fast-paced iteration, making automated testing particularly important.

[0003] Most existing automated testing tools manage interfaces and parameters through Excel spreadsheets, read status codes from the Excel file, and obtain the interface response results based on the corresponding request methods. They then verify the status codes and response results to obtain the execution results of the test cases.

[0004] However, the above methods cannot promptly identify whether there are error or abnormal log information on the server side during the interface request process. During the execution of automated testing, there may be situations where server errors or abnormal vulnerabilities are not detected in time due to missing or incomplete interface verification rules. It is also impossible to directly discover the server's CPU, memory and other resource usage based on the automated test execution results, which can easily lead to the neglect of server performance issues. As a result, the existing automated testing methods have low efficiency in monitoring server anomalies and performance problems. Summary of the Invention

[0005] This invention provides an automated test data processing method, apparatus, device, and storage medium to improve the efficiency of monitoring server anomalies and performance problems.

[0006] The first aspect of this invention provides an automated test data processing method, comprising:

[0007] The interface test case file is read by a pre-created main thread, and the interface test cases in the interface test case file are automatically tested by the main thread to obtain the execution results. The execution results are written to a pre-set result file to obtain the target automated execution result file.

[0008] The system connects to the pre-configured server corresponding to the pre-created sub-thread and reads the server log information of the pre-configured server after a successful connection.

[0009] The sub-thread performs anomaly detection on the server log information to obtain target anomaly log information, and writes the target anomaly log information into a preset anomaly log file to obtain the target anomaly log file;

[0010] Obtain the resource data of the preset server, write the resource data into the preset server resource file to obtain the target server resource file, wherein the resource data includes process CPU usage information and process memory usage information;

[0011] According to the preset sending method, the target automated execution result file, the target exception log file, and the target server resource file are sent to the preset feedback terminal.

[0012] Optionally, in a first implementation of the first aspect of the present invention, the step of reading the interface test case file through a pre-created main thread, performing automated testing on the interface test cases in the interface test case file through the main thread to obtain execution results, and writing the execution results into a pre-set result file to obtain a target automated execution result file includes:

[0013] The interface test case file is read by a pre-created main thread, and it is determined whether the content of the interface test case file is empty.

[0014] If the content of the interface test case file is not empty, a preset function is called to obtain the parameter information of each interface test case in the interface test case file. The parameter information includes the parameter, the value corresponding to each parameter, and the index value corresponding to each parameter.

[0015] The corresponding interface request method is invoked based on the parameter information, and the interface request is triggered through the interface request method to obtain the interface response result;

[0016] The interface response result is verified to obtain the test case execution result of the interface test case. The test case execution result is written into a preset result file to obtain the execution result file.

[0017] Determine whether the last line of the execution result file is empty. If the last line of the execution result file is empty, then the execution result file is identified as the target automated execution result file.

[0018] Optionally, in a second implementation of the first aspect of the present invention, the step of connecting to a pre-created sub-thread corresponding to a pre-configured server and reading the server log information of the pre-configured server after a successful connection includes:

[0019] The configuration file is obtained through a pre-created sub-thread, and the configuration information in the configuration file is read. The configuration information includes server connection information and log exception keyword information.

[0020] The system connects to the pre-defined server corresponding to the sub-thread using the pre-defined Secure Shell protocol commands and the server connection information, and obtains the connection result.

[0021] If the connection result is successful, then read the server log information of the preset server after the successful connection.

[0022] Optionally, in a third implementation of the first aspect of the present invention, the step of performing anomaly detection on the server log information through the sub-thread to obtain target anomaly log information, and writing the target anomaly log information into a preset anomaly log file to obtain the target anomaly log file includes:

[0023] The server log information is matched cyclically using the sub-thread and the log exception keyword information until the interface test cases in the interface test case file are executed, and the target exception log information is obtained.

[0024] The target anomaly log information is compared and analyzed with the contents of a preset anomaly log file, and the target anomaly log information after comparison and analysis is written into the preset anomaly log file to obtain the target anomaly log file.

[0025] Optionally, in the fourth implementation of the first aspect of the present invention, the step of performing a cyclical match on the server log information using the sub-thread and the log exception keyword information until the interface test cases in the interface test case file are executed to obtain the target exception log information includes:

[0026] The sub-thread extracts keywords from the server log information to obtain initial log keywords. Based on the log exception keywords in the log exception keyword information, the corresponding target log keywords are matched from the initial log keywords. The log exception keyword information includes log exception keywords, as well as the exception keyword sequence and exception log template corresponding to the log exception keywords.

[0027] An initial keyword sequence for the target log keywords is generated, and the initial keyword sequence is compared with the abnormal keyword sequence to obtain the target keyword sequence corresponding to the abnormal keyword sequence.

[0028] Extract the initial exception log information corresponding to the target keyword sequence from the server log information, compare and analyze the initial exception log information with the exception log template, until the interface test cases in the interface test case file are executed, and obtain the target exception log information corresponding to the exception log template.

[0029] Optionally, in a fifth implementation of the first aspect of the present invention, the step of comparing and analyzing the target anomaly log information with the content of a preset anomaly log file, and writing the compared and analyzed target anomaly log information into the preset anomaly log file to obtain the target anomaly log file, includes:

[0030] Obtain the context information of the target log keywords from the target anomaly log information;

[0031] Determine whether the content in the preset exception log file contains information identical to the context information;

[0032] If the content of the preset exception log file does not contain information identical to the context information, then the target exception log information is written into the preset exception log file to obtain the target exception log file.

[0033] Optionally, in a sixth implementation of the first aspect of the present invention, sending the target automated execution result file, the target exception log file, and the target server resource file to a preset feedback terminal according to a preset sending method includes:

[0034] Statistical analysis is performed on the target automated execution result file and the target exception log file to obtain the exception rate, exception duration, and exception range;

[0035] A visualization chart is generated based on the anomaly rate, the anomaly duration, and the anomaly range. Based on the resource data in the target server resource file, a preset server performance level table is retrieved to obtain the corresponding target server performance level.

[0036] Obtain a preset email template and the corresponding email address of the preset feedback terminal. Based on the email template and the email address, generate the target automated execution result file, the target exception log file, the target server resource file, the visualization chart, and the feedback email of the target server performance level, and send the feedback email to the preset feedback terminal.

[0037] A second aspect of the present invention provides an automated test data processing apparatus, comprising:

[0038] The execution writing module is used to read the interface test case file through a pre-created main thread, perform automated testing on the interface test cases in the interface test case file through the main thread to obtain the execution results, and write the execution results into a pre-set result file to obtain the target automated execution result file;

[0039] The connection reading module is used to connect to the preset server corresponding to the preset thread through a pre-created sub-thread, and read the server log information of the preset server after the connection is successful.

[0040] The detection and writing module is used to perform anomaly detection on the server log information through the sub-thread, obtain the target anomaly log information, and write the target anomaly log information into a preset anomaly log file to obtain the target anomaly log file;

[0041] The acquisition and writing module is used to acquire the resource data of the preset server, write the resource data into the preset server resource file, and obtain the target server resource file. The resource data includes information on the process's CPU usage and the process's memory usage.

[0042] The sending module is used to send the target automated execution result file, the target exception log file, and the target server resource file to the preset feedback terminal according to the preset sending method.

[0043] Optionally, in a first implementation of the second aspect of the present invention, the execution writing module is specifically used for:

[0044] The interface test case file is read by a pre-created main thread, and it is determined whether the content of the interface test case file is empty.

[0045] If the content of the interface test case file is not empty, a preset function is called to obtain the parameter information of each interface test case in the interface test case file. The parameter information includes the parameter, the value corresponding to each parameter, and the index value corresponding to each parameter.

[0046] The corresponding interface request method is invoked based on the parameter information, and the interface request is triggered through the interface request method to obtain the interface response result;

[0047] The interface response result is verified to obtain the test case execution result of the interface test case. The test case execution result is written into a preset result file to obtain the execution result file.

[0048] Determine whether the last line of the execution result file is empty. If the last line of the execution result file is empty, then the execution result file is identified as the target automated execution result file.

[0049] Optionally, in a second implementation of the second aspect of the present invention, the connection reading module is specifically used for:

[0050] The configuration file is obtained through a pre-created sub-thread, and the configuration information in the configuration file is read. The configuration information includes server connection information and log exception keyword information.

[0051] The system connects to the pre-defined server corresponding to the sub-thread using the pre-defined Secure Shell protocol commands and the server connection information, and obtains the connection result.

[0052] If the connection result is successful, then read the server log information of the preset server after the successful connection.

[0053] Optionally, in a third implementation of the second aspect of the present invention, the detection and writing module includes:

[0054] The matching unit is used to perform a cyclic matching of the server log information using the sub-thread and the log exception keyword information until the interface test cases in the interface test case file are executed and the target exception log information is obtained.

[0055] The comparison and analysis unit is used to compare and analyze the target abnormal log information with the contents of a preset abnormal log file, and write the target abnormal log information after comparison and analysis into the preset abnormal log file to obtain the target abnormal log file.

[0056] Optionally, in a fourth implementation of the second aspect of the present invention, the matching unit is specifically used for:

[0057] The sub-thread extracts keywords from the server log information to obtain initial log keywords. Based on the log exception keywords in the log exception keyword information, the corresponding target log keywords are matched from the initial log keywords. The log exception keyword information includes log exception keywords, as well as the exception keyword sequence and exception log template corresponding to the log exception keywords.

[0058] An initial keyword sequence for the target log keywords is generated, and the initial keyword sequence is compared with the abnormal keyword sequence to obtain the target keyword sequence corresponding to the abnormal keyword sequence.

[0059] Extract the initial exception log information corresponding to the target keyword sequence from the server log information, compare and analyze the initial exception log information with the exception log template, until the interface test cases in the interface test case file are executed, and obtain the target exception log information corresponding to the exception log template.

[0060] Optionally, in a fifth implementation of the second aspect of the present invention, the comparison analysis unit is specifically used for:

[0061] Obtain the context information of the target log keywords from the target anomaly log information;

[0062] Determine whether the content in the preset exception log file contains information identical to the context information;

[0063] If the content of the preset exception log file does not contain information identical to the context information, then the target exception log information is written into the preset exception log file to obtain the target exception log file.

[0064] Optionally, in a sixth implementation of the second aspect of the present invention, the sending module is specifically used for:

[0065] Statistical analysis is performed on the target automated execution result file and the target exception log file to obtain the exception rate, exception duration, and exception range;

[0066] A visualization chart is generated based on the anomaly rate, the anomaly duration, and the anomaly range. Based on the resource data in the target server resource file, a preset server performance level table is retrieved to obtain the corresponding target server performance level.

[0067] Obtain a preset email template and the corresponding email address of the preset feedback terminal. Based on the email template and the email address, generate the target automated execution result file, the target exception log file, the target server resource file, the visualization chart, and the feedback email of the target server performance level, and send the feedback email to the preset feedback terminal.

[0068] A third aspect of the present invention provides an automated test data processing device, comprising: a memory and at least one processor, wherein the memory stores instructions; the at least one processor invokes the instructions in the memory to cause the automated test data processing device to perform the above-described automated test data processing method.

[0069] A fourth aspect of the present invention provides a computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform the above-described automated test data processing method.

[0070] In the technical solution provided by this invention, a pre-created main thread reads the interface test case file, performs automated testing on the interface test cases in the interface test case file to obtain execution results, and writes the execution results into a pre-set result file to obtain the target automated execution result file; a pre-created sub-thread connects to the pre-set server corresponding to the sub-thread and reads the server log information of the pre-set server after a successful connection; the sub-thread performs anomaly detection on the server log information to obtain target anomaly log information, and writes the target anomaly log information into a pre-set anomaly log file to obtain the target anomaly log file; resource data of the pre-set server is obtained and written into the pre-set server resource file to obtain the target server resource file, the resource data including process CPU usage information and process memory usage information; the target automated execution result file, the target anomaly log file, and the target server resource file are sent to a pre-set feedback terminal according to a pre-set sending method. In this embodiment of the invention, the main thread performs automated testing on the interface test cases in the interface test case file, and the sub-thread connects to the pre-configured server to monitor the server log information of the pre-configured server in real time and read the resource data of the pre-configured server. This realizes multi-process monitoring of multiple servers, real-time capture of server log information during interface request process, anomaly detection of server log information, and real-time monitoring and reading of resource data of the pre-configured server, thereby improving the efficiency of monitoring server anomalies and performance problems. Attached Figure Description

[0071] Figure 1 This is a schematic diagram of an embodiment of the automated test data processing method in this invention;

[0072] Figure 2 This is another schematic diagram of steps 101-105 in an embodiment of the present invention;

[0073] Figure 3 This is a schematic diagram of another embodiment of the automated test data processing method in this invention;

[0074] Figure 4 This is another schematic diagram of step 301 in an embodiment of the present invention;

[0075] Figure 5 This is another schematic diagram of steps 302-305 in an embodiment of the present invention;

[0076] Figure 6 This is a schematic diagram of one embodiment of the automated test data processing device in this invention;

[0077] Figure 7 This is a schematic diagram of another embodiment of the automated test data processing device in this invention;

[0078] Figure 8 This is a schematic diagram of one embodiment of the automated test data processing device in this invention. Detailed Implementation

[0079] This invention provides an automated test data processing method, apparatus, device, and storage medium, which improves the efficiency of monitoring server anomalies and performance problems.

[0080] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms “comprising” or “having,” and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0081] For ease of understanding, the specific process of the embodiments of the present invention is described below. Please refer to [link / reference]. Figure 1 One embodiment of the automated test data processing method in this invention includes:

[0082] 101. The interface test case file is read by a pre-created main thread. The interface test cases in the interface test case file are automatically tested by the main thread to obtain the execution results. The execution results are written to a pre-set result file to obtain the target automated execution result file.

[0083] It is understood that the executing entity of this invention can be an automated test data processing device, a terminal, or a server; no specific limitation is made here. This embodiment of the invention will be described using a server as an example.

[0084] The server pre-builds a test environment for the server and database, generating configuration files containing configuration information, including but not limited to server connection information (supporting multiple server connections) and log exception keywords. Based on the designed interface test information, it generates corresponding interface test case files (Excel files). After building the test environment and generating the interface test case files, the server creates the main thread and sub-threads for the test process, obtaining pre-created main and sub-threads. The server calls the pre-created main thread, which reads the interface test cases, parses the interface test case files, obtains the test parameters, and executes the automated tests of the interface test cases according to the test parameters using pre-defined automated scripts. The server then verifies the test case execution results according to a pre-defined verification strategy, obtaining the execution results for those that pass verification. These results are written to a pre-defined result file, resulting in the target automated execution result file.

[0085] It should be noted that the interface test case file includes multiple interface test cases. Test parameters include, but are not limited to, test step name parameters, input parameters, interface method name parameters, expected output parameters, actual output parameters, interface name parameters, and interface request parameters. The number of interface test cases may be one or more, i.e., multiple test case files. Pre-defined verification strategies are used to verify whether the execution result achieves the effect of the interface implementation corresponding to the interface test case. Pre-defined verification strategies include multiple verification rules, such as: whether the values ​​of preset database fields have changed in the execution result, whether preset memory values ​​have changed, and whether preset modules have not been downloaded, to determine whether the interface test case has passed execution.

[0086] 102. Connect to the preset server corresponding to the preset server through the pre-created sub-thread, and read the server log information of the preset server after the connection is successful.

[0087] The system involves pre-creating one or more sub-threads and pre-configuring one or more servers. Each pre-configured server corresponds to one sub-thread; for example, pre-configured server 1 corresponds to sub-thread 1, and pre-configured server 2 corresponds to sub-thread 2. Multiple sub-threads execute in parallel, and these sub-threads also execute in parallel with the main thread. The server retrieves a pre-generated configuration file, parses it to obtain parsed information, extracts the server connection information for the pre-configured server from the parsed information, connects to the pre-configured server based on the connection information, and enters a username and password to successfully authorize login, thus establishing a successful connection to the pre-configured server. Finally, it reads the server log information of the pre-configured server after a successful connection.

[0088] 103. Perform anomaly detection on the server log information through a sub-thread to obtain the target anomaly log information, and write the target anomaly log information into a preset anomaly log file to obtain the target anomaly log file.

[0089] After obtaining server log information, the server retrieves the corresponding configuration file through a sub-thread, parses the configuration file to obtain parsed information, and extracts preset log exception keywords or a list of regular expressions corresponding to preset log exception keywords from the parsed information. The server can then traverse the server log information using the preset log exception keywords to obtain target log exception keywords. The context information corresponding to the target log exception keywords is used as the target exception log information. Alternatively, the server can search the server log information using the list of regular expressions corresponding to the log exception keywords to obtain the target log exception keywords. A keyword sequence of the target log exception keywords is generated through a preset window, and the similarity between the keyword sequence and the list of regular expressions is calculated. The context information corresponding to the keyword sequence with a similarity greater than a preset threshold is used as the target exception log information, and the target exception log information is written to a preset exception log file to obtain the target exception log file.

[0090] 104. Obtain the resource data of the preset server, write the resource data to the preset server resource file, and obtain the target server resource file. The resource data includes information on the CPU usage of the process and the memory usage of the process.

[0091] After the server obtains the target exception log file, it retrieves the resource storage path of the preset server through a sub-thread, calls the resource read command, and reads the CPU and memory usage information of the process on the preset server (i.e., resource data) based on the resource storage path. This information is then written to the preset server resource file, thus obtaining the target server resource file. Once the sub-thread has obtained the target server resource file, it signifies the completion of its execution. The server then returns to the main thread, which executes automated tests for the next interface test case. This process continues in a loop until all interface test cases have completed automated testing.

[0092] 105. Send the target automated execution result file, the target exception log file, and the target server resource file to the preset feedback terminal according to the preset sending method.

[0093] After obtaining the target server resource file, the server checks the execution status of the interface test cases in the main thread to determine if all interface test cases have been completed. If not, it retrieves the incomplete interface test cases and executes them according to the execution process in steps 101-104 until completion. If so, it retrieves the identifier of the preset feedback end, matches the corresponding email address and email template based on the identifier, and generates feedback emails for the target automated execution result file, target exception log file, and target server resource file based on the email address and email template. The feedback emails are then sent to the preset feedback end so that the relevant personnel at the preset feedback end can promptly investigate, provide feedback, and fix issues, ensuring the project quality corresponding to the interface test case file.

[0094] In another embodiment, the execution process of steps 101-105 can be as follows: Figure 2 As shown, there are multiple sub-threads. Taking sub-thread 1 and sub-thread 2 as examples, the main thread, sub-thread 1, and sub-thread 2 execute in parallel. The main thread reads and parses the interface test case file, performs automated testing on the interface test cases in the file, obtains the execution results, writes the execution results to a pre-set result file, and obtains the target automated execution result file. The target automated execution result file is then fed back to the pre-set feedback terminal according to the email format. Specifically, when performing automated testing on the interface test cases in the interface test case file, obtaining the execution results, and writing the results to the pre-set result file to obtain the target automated execution result file, if it is detected that the target automated execution result file is not the last line, then the interface test case file is parsed again. Sub-thread 1 connects to the pre-set server 1 corresponding to sub-thread 1, listens to the log information of server 1, and reads the connection... After a successful connection, the system retrieves the server log information of the pre-configured server 1, including information on the CPU and memory usage of the process. This resource data is written to the pre-configured server resource file to obtain the target server resource file, which is then sent back to the pre-configured feedback end in an email format. The system also performs anomaly detection on the server log information to determine if the target anomaly log information exists. If so, the target anomaly log information is obtained, written to the pre-configured anomaly log file, and deduplicated. This is then sent back to the pre-configured feedback end in an email format. If not, the system listens to the log information of server 1 and reads the server log information of the pre-configured server 1 after a successful connection. The execution process of sub-thread 2 is similar to that of sub-thread 1 and will not be described further here.

[0095] In this embodiment of the invention, the main thread performs automated testing on the interface test cases in the interface test case file, and the sub-thread connects to the pre-configured server to monitor the server log information of the pre-configured server in real time and read the resource data of the pre-configured server. This realizes multi-process monitoring of multiple servers, real-time capture of server log information during interface request process, anomaly detection of server log information, and real-time monitoring and reading of resource data of the pre-configured server, thereby improving the efficiency of monitoring server anomalies and performance problems.

[0096] Please see Figure 3 Another embodiment of the automated test data processing method in this invention includes:

[0097] 301. The interface test case file is read by a pre-created main thread. The interface test cases in the interface test case file are automatically tested by the main thread to obtain the execution results. The execution results are written to a pre-set result file to obtain the target automated execution result file.

[0098] Specifically, the server reads the interface test case file through a pre-created main thread and determines whether the file content is empty. If the file content is not empty, a pre-defined function is called to obtain the parameter information of each interface test case in the file. The parameter information includes the parameter, the value of each parameter, and the index value of each parameter. Based on the parameter information, the corresponding interface request method is called to trigger the interface request and obtain the interface response result. The interface response result is validated to obtain the test case execution result, which is then written to a pre-defined result file to obtain the execution result file. Finally, the server determines whether the last line of the execution result file is empty. If the last line is empty, the execution result file is identified as the target automated execution result file.

[0099] The specific execution process can be as follows: Figure 4 As shown, the pre-defined function to retrieve the index value (index) of each parameter in each interface test case file is `getColumnindex()`, and the pre-defined functions to retrieve the value of each parameter in each interface test case file are `row_value()` and `cell_value()`. Before obtaining the interface response, the interface test case file is triggered by the interface request method. If the content of the interface test case file is empty, the execution ends; if the last line of the execution result file is not empty, the execution ends.

[0100] In another embodiment, for example, the interface test case file is an Excel spreadsheet, where each row represents an interface test case. The server obtains the sheet name of the interface test case file through a pre-created main thread, reads the interface test case file based on the sheet name, parses the file to obtain interface test case parameters, and uses the unit test assertion `junit Asser` function to analyze and determine if the interface test case parameters are empty, thereby determining if the file content of the interface test case file is empty. If so, execution ends; otherwise, the pre-defined `xlrd` module's `getColumnindex()` function is called to obtain the index value corresponding to each interface test case parameter in the header of the parsed interface test cases. Pre-defined value retrieval functions `row_value()` and `cell_value()` are then called to retrieve the value of each interface test case parameter from each row of data, such as the test case name, URL, request method, request parameters, and expected result, thus obtaining the parameter information.

[0101] The interface test cases are triggered based on the parameter information, and the corresponding interface request method is called through the interface request method parameter in the parameter information. The interface request method can be a GET request or a POST request. The interface request is triggered by the interface request method, and the interface response result based on the interface test case execution is obtained through the interface request. The corresponding verification strategy is matched according to the interface test case, and the interface response result is verified by the verification strategy to obtain the test case execution result that passes the verification. The test case execution result is written to a pre-set result file, which is an Excel spreadsheet file. The pre-set result file may include, but is not limited to, other types of pre-set result files. The execution status value, parameter name, characters (success characters, failure characters) and / or field values ​​of the test case execution result may include, but are not limited to, the execution status value. For example, a status value of 1 indicates that the test was successful. The test case execution result may include, but is not limited to, parameter name and execution status value. For example, setup|1. The test case execution result may include, but is not limited to, parameter name and characters (success characters and / or failure characters). For example, 30|OK. Determine whether the last line of the execution result file is empty. If it is, end the execution of the interface test case. If not, repeat steps 1012-1014 until the last line of the execution result file is empty.

[0102] 302. Connect to the preset server corresponding to the preset server through the pre-created sub-thread, and read the server log information of the preset server after the connection is successful.

[0103] Specifically, the server obtains the configuration file through a pre-created sub-thread, reads the configuration information in the configuration file, including server connection information and log exception keyword information; connects to the pre-configured server corresponding to the sub-thread through the pre-configured Secure Shell protocol commands and server connection information, and obtains the connection result; if the connection result is successful, the server log information of the pre-configured server after the successful connection is read.

[0104] For example, the server uses a pre-created sub-thread to retrieve the corresponding configuration file from a pre-built database based on the parameter information in the interface test case file. It then parses the configuration file to obtain the parsed configuration information, reads the corresponding server connection information from the parsed configuration information, and calls a pre-built Secure Shell (SSH) protocol command. The server connection information is then executed via the SSH command to connect to the pre-built server corresponding to the sub-thread. The server's username and password are obtained, and authorization is performed using these credentials. Upon successful authorization, the connection result is obtained. The server checks if the connection result indicates "connection successful." If it does, all operation logs on the pre-built server after the successful connection are retrieved to obtain the server log information corresponding to the execution of the interface test case. This server log information is extracted, or the `tail -f` command is sent to the successfully connected pre-built server via the pre-built `subprocess.Popen()` method to obtain server logs in real time. If not, the corresponding sub-thread execution is considered complete.

[0105] 303. By using sub-threads and log exception keyword information, perform a loop to match the server log information until the interface test cases in the interface test case file are executed and obtain the target exception log information.

[0106] Specifically, the server extracts keywords from server log information through a sub-thread to obtain initial log keywords. Based on the log exception keywords in the log exception keyword information, it matches the corresponding target log keywords from the initial log keywords. The log exception keyword information includes the log exception keywords, the corresponding exception keyword sequence, and the exception log template. An initial keyword sequence for the target log keywords is generated. The initial keyword sequence is compared with the exception keyword sequence to obtain the target keyword sequence corresponding to the exception keyword sequence. The initial exception log information corresponding to the target keyword sequence is extracted from the server log information. The initial exception log information is compared and analyzed with the exception log template until the interface test cases in the interface test case file are executed, and the target exception log information corresponding to the exception log template is obtained.

[0107] For example, the server uses a sub-thread to convert server log information into string information. The string information is then segmented, concatenated, and filtered sequentially to obtain initial log keywords. The text similarity between the initial log keywords and log anomaly keywords in the log anomaly keyword information is calculated. It is then determined whether all text similarities exceed a preset target threshold. If not, the target server log information is reread. The rereading of the target server log information occurs later than the previously read server log information. Log anomaly keyword matching is performed on the target server log information. If any or some of the text similarities exceed the target threshold, the initial log keywords corresponding to the text similarities exceeding the target threshold are selected. The target log keyword is defined, and an initial keyword sequence is generated according to the time series through a preset window. The cosine similarity between the initial keyword sequence and the abnormal keyword sequence in the log abnormal keyword information is calculated. It is determined whether the cosine similarity is within the preset similarity range. If not, it does not meet the abnormal keyword sequence, and the comparison between the next initial keyword sequence and the abnormal keyword sequence is continued. If it does, it meets the abnormal keyword sequence, and the corresponding initial keyword sequence is used as the target keyword sequence. The initial abnormal log information corresponding to the target keyword sequence is compared with the abnormal log template to obtain the target abnormal log information that is the same as the abnormal log template or has a similarity greater than the preset threshold.

[0108] The server compares and analyzes the initial exception log information with the exception log template to determine whether there is exception log information in the initial exception log information that corresponds to the exception log template. If there is exception log information in the initial exception log information that corresponds to the exception log template, then the exception log information corresponding to the exception log template is determined as the target exception log information. If there is no exception log information in the initial exception log information that corresponds to the exception log template, then the server log information is matched in a loop until the interface test cases in the interface test case file are executed and the target exception log information is obtained.

[0109] Optionally, the server can first compare and analyze the initial exception log information with the exception log template to obtain candidate exception log information. Then, it can compare and analyze the sequence information in the candidate exception log information with the target keyword sequence. Candidate exception log information whose sequence information is the same as or has a similarity greater than a preset target threshold is identified as target exception log information. If no corresponding exception keyword (i.e., target log keyword) is found in the initial log keywords, the corresponding field value is generated to obtain the target log keyword, for example, '0'. The corresponding target keyword sequence is the corresponding multiple field values, for example, '0000'. The corresponding target exception log information is the preset field name indicating that it is not present.

[0110] 304. Compare and analyze the target anomaly log information with the contents of the preset anomaly log file, and write the target anomaly log information after comparison and analysis into the preset anomaly log file to obtain the target anomaly log file.

[0111] Specifically, the server obtains the context information of the target log keyword from the target exception log information; determines whether the content of the preset exception log file contains information that is the same as the context information; if the content of the preset exception log file does not contain information that is the same as the context information, then the target exception log information is written into the preset exception log file to obtain the target exception log file.

[0112] After obtaining the target anomaly log information, the server extracts the context information of the target log keywords from the target anomaly log information. It then compares and analyzes this context information with the log information in the preset anomaly log file, calculates their information similarity, and determines whether the information similarity is greater than a preset information similarity threshold. If so, it is determined that the target automated execution result file contains information identical to the context information, and the target anomaly log information is not written to the preset anomaly log file. Alternatively, the target anomaly log information and the log information in the preset anomaly log file are deduplicated and merged to obtain the target anomaly log file. If not, it is determined that the target automated execution result file contains information identical to the context information, and the anomaly log file is written to the preset anomaly log file to obtain the target anomaly log file.

[0113] 305. Obtain the resource data of the preset server, write the resource data to the preset server resource file, and obtain the target server resource file. The resource data includes information on the CPU usage of the process and the memory usage of the process.

[0114] After the server obtains the target exception log file, it retrieves the resource storage path of the preset server through a sub-thread, calls the resource read command, and reads the CPU and memory usage information of the process on the preset server (i.e., resource data) based on the resource storage path. This information is then written to the preset server resource file, thus obtaining the target server resource file. Once the sub-thread has obtained the target server resource file, it signifies the completion of its execution. The server then returns to the main thread, which executes automated tests for the next interface test case. This process continues in a loop until all interface test cases have completed automated testing.

[0115] In another embodiment, the execution process of steps 302-305 can be Figure 5As shown, the server obtains the configuration file through a pre-created sub-thread, reads the configuration information in the configuration file, including server connection information and log exception keyword information, and connects to the pre-configured server corresponding to the sub-thread through a pre-configured secure shell protocol command (SSH) and server connection information. The connection result is obtained, and it is determined whether the connection is successful. If not, the execution ends. If yes, the top command is executed to obtain the resource data of the pre-configured server, including the CPU usage information and memory usage information of the process. The resource data is written to the pre-configured server resource file and named ip_resourse_used_current time to obtain the target server resource file. The tail -f command is executed to read the server log information of the pre-configured server after the connection is successful in real time.

[0116] The server log information is analyzed using log exception keywords and string matching algorithms (or regular expressions). If a match is found, the `top` command is executed to retrieve pre-configured server resource data, including CPU and memory usage information. If a match is found, the target exception log information is obtained and compared with the contents of a pre-configured exception log file. The resulting target exception log information is then written to the pre-configured exception log file and named `ip_exception_log_current_time`. The target exception log file is then retrieved. Finally, the execution of test cases in the interface test case file is checked. If completed, execution ends; otherwise, the `top` command is executed again to retrieve pre-configured server resource data, including CPU and memory usage information.

[0117] 306. Send the target automated execution result file, the target exception log file, and the target server resource file to the preset feedback terminal according to the preset sending method.

[0118] Specifically, the server performs statistical analysis on the target automated execution result file and the target exception log file to obtain the exception rate, exception duration, and exception range; it generates a visualization chart based on the exception rate, exception duration, and exception range, and retrieves the corresponding target server performance level from the preset server performance level table based on the resource data in the target server resource file; it obtains the preset email template and the email address corresponding to the preset feedback terminal, and generates a feedback email containing the target automated execution result file, target exception log file, target server resource file, visualization chart, and target server performance level based on the email template and email address, and sends the feedback email to the preset feedback terminal.

[0119] The anomaly rate is calculated as the percentage of abnormal interface test cases out of all interface test cases. For example, if there are 20 interface test cases and 5 are abnormal, the anomaly rate is 25%. The anomaly duration is the duration of each abnormal operation period during the automated testing process of each interface test case. This can be obtained by sliding the target anomaly log information through a preset anomaly window, and calculating the difference between the start and end times of each anomaly operation period. The anomaly scope refers to the automated test items and their corresponding content for the interface test cases corresponding to the target anomaly log information. When the server retrieves the target server performance level from the preset server performance level table based on the resource data in the target server resource file, the specific operations are as follows: A hash value for the resource data is generated; the preset index and hash value are used to retrieve the target server performance level from the preset server performance level table. The target server performance level can be excellent, good, poor, or relatively poor. Fill in the target automated execution result file, target exception log file, target server resource file, visualization chart, and target server performance level into the corresponding positions in the preset email template to obtain the feedback email, and send the feedback email to the preset feedback terminal.

[0120] In this embodiment of the invention, the main thread performs automated testing on the interface test cases in the interface test case file, and the sub-thread connects to the pre-configured server to monitor the server log information of the pre-configured server in real time and read the resource data of the pre-configured server. This realizes multi-process monitoring of multiple servers, real-time capture of server log information during interface request process, anomaly detection of server log information, and real-time monitoring and reading of resource data of the pre-configured server, thereby improving the efficiency of monitoring server anomalies and performance problems.

[0121] The above describes the method for processing automated test data in the embodiments of the present invention. The following describes the apparatus for processing automated test data in the embodiments of the present invention. Please refer to [link / reference]. Figure 6 One embodiment of the automated test data processing device in this invention includes:

[0122] The execution writing module 601 is used to read the interface test case file through a pre-created main thread, perform automated testing on the interface test cases in the interface test case file through the main thread to obtain the execution results, and write the execution results into a pre-set result file to obtain the target automated execution result file.

[0123] The connection reading module 602 is used to connect to the preset server corresponding to the preset thread through a pre-created sub-thread, and read the server log information of the preset server after the connection is successful.

[0124] The detection and writing module 603 is used to perform anomaly detection on server log information through a sub-thread, obtain target anomaly log information, and write the target anomaly log information into a preset anomaly log file to obtain the target anomaly log file;

[0125] The write module 604 is used to acquire the resource data of the preset server, write the resource data to the preset server resource file, and obtain the target server resource file. The resource data includes information on the CPU usage of the process and information on the memory usage of the process.

[0126] The sending module 605 is used to send the target automated execution result file, the target exception log file, and the target server resource file to the preset feedback terminal according to the preset sending method.

[0127] The functions of each module in the above-mentioned automated test data processing device correspond to the steps in the above-mentioned automated test data processing method embodiment, and their functions and implementation processes will not be described in detail here.

[0128] In this embodiment of the invention, the main thread performs automated testing on the interface test cases in the interface test case file, and the sub-thread connects to the pre-configured server to monitor the server log information of the pre-configured server in real time and read the resource data of the pre-configured server. This realizes multi-process monitoring of multiple servers, real-time capture of server log information during interface request process, anomaly detection of server log information, and real-time monitoring and reading of resource data of the pre-configured server, thereby improving the efficiency of monitoring server anomalies and performance problems.

[0129] Please see Figure 7 Another embodiment of the automated test data processing device in this invention includes:

[0130] The execution writing module 601 is used to read the interface test case file through a pre-created main thread, perform automated testing on the interface test cases in the interface test case file through the main thread to obtain the execution results, and write the execution results into a pre-set result file to obtain the target automated execution result file.

[0131] The connection reading module 602 is used to connect to the preset server corresponding to the preset thread through a pre-created sub-thread, and read the server log information of the preset server after the connection is successful.

[0132] The detection and writing module 603 is used to perform anomaly detection on server log information through a sub-thread, obtain target anomaly log information, and write the target anomaly log information into a preset anomaly log file to obtain the target anomaly log file;

[0133] Specifically, the detection and writing module 603 includes:

[0134] Matching unit 6031 is used to perform loop matching on server log information using sub-thread and log exception keyword information until the interface test cases in the interface test case file are executed and the target exception log information is obtained.

[0135] The comparison and analysis unit 6032 is used to compare and analyze the target abnormal log information with the contents of the preset abnormal log file, and write the target abnormal log information after comparison and analysis into the preset abnormal log file to obtain the target abnormal log file;

[0136] The write module 604 is used to acquire the resource data of the preset server, write the resource data to the preset server resource file, and obtain the target server resource file. The resource data includes information on the CPU usage of the process and information on the memory usage of the process.

[0137] The sending module 605 is used to send the target automated execution result file, the target exception log file, and the target server resource file to the preset feedback terminal according to the preset sending method.

[0138] Optionally, the write module 601 can also be specifically used for:

[0139] The interface test case file is read by a pre-created main thread, and it is determined whether the content of the interface test case file is empty.

[0140] If the content of the interface test case file is not empty, the pre-defined function is called to obtain the parameter information of each interface test case in the interface test case file. The parameter information includes the parameter, the value of each parameter, and the index value of each parameter.

[0141] The corresponding API request method is invoked based on the parameter information, and the API request is triggered through the API request method to obtain the API response result;

[0142] The interface response results are validated to obtain the test case execution results of the interface test cases. The test case execution results are written to a pre-set result file to obtain the execution result file.

[0143] Check if the last line of the execution result file is empty. If the last line of the execution result file is empty, then the execution result file is identified as the target automated execution result file.

[0144] Optionally, the connection reading module 602 can also be specifically used for:

[0145] The configuration file is obtained through a pre-created sub-thread, and the configuration information in the configuration file is read. The configuration information includes server connection information and log exception keyword information.

[0146] The system connects to the pre-defined server corresponding to the sub-thread using pre-defined Secure Shell protocol commands and server connection information, and obtains the connection result.

[0147] If the connection result is successful, then read the server log information of the preset server after the successful connection.

[0148] Optionally, the matching unit 6031 can also be specifically used for:

[0149] The server log information is extracted by a sub-thread to obtain the initial log keywords. Based on the log exception keywords in the log exception keyword information, the corresponding target log keywords are matched from the initial log keywords. The log exception keyword information includes the log exception keywords, as well as the exception keyword sequence and exception log template corresponding to the log exception keywords.

[0150] Generate an initial keyword sequence for the target log keywords, compare the initial keyword sequence with the abnormal keyword sequence, and obtain the target keyword sequence corresponding to the abnormal keyword sequence;

[0151] Extract the initial exception log information corresponding to the target keyword sequence from the server log information, compare and analyze the initial exception log information with the exception log template, until the interface test cases in the interface test case file are executed, and obtain the target exception log information corresponding to the exception log template.

[0152] Optionally, the comparison analysis unit 6032 can also be specifically used for:

[0153] Obtain the context information of the target log keywords from the target exception log information;

[0154] Determine if the content in the preset exception log file contains information identical to the context information;

[0155] If the content of the preset exception log file does not contain information that is the same as the context information, then the target exception log information is written into the preset exception log file to obtain the target exception log file.

[0156] Optionally, the sending module 605 can also be specifically used for:

[0157] Perform statistical analysis on the target automated execution result file and the target exception log file to obtain the exception rate, exception duration and exception range;

[0158] Visual charts are generated based on the anomaly rate, anomaly duration, and anomaly range. Based on the resource data in the target server resource file, a pre-set server performance level table is retrieved to obtain the corresponding target server performance level.

[0159] Obtain the preset email template and the corresponding email address of the preset feedback terminal. Based on the email template and email address, generate the target automated execution result file, the target exception log file, the target server resource file, the visualization chart, and the feedback email of the target server performance level, and send the feedback email to the preset feedback terminal.

[0160] The functions of each module and unit in the above-mentioned automated test data processing device correspond to the steps in the above-mentioned automated test data processing method embodiment, and their functions and implementation processes will not be described in detail here.

[0161] In this embodiment of the invention, the main thread performs automated testing on the interface test cases in the interface test case file, and the sub-thread connects to the pre-configured server to monitor the server log information of the pre-configured server in real time and read the resource data of the pre-configured server. This realizes multi-process monitoring of multiple servers, real-time capture of server log information during interface request process, anomaly detection of server log information, and real-time monitoring and reading of resource data of the pre-configured server, thereby improving the efficiency of monitoring server anomalies and performance problems.

[0162] above Figure 6 and Figure 7 The automated test data processing device in the embodiments of the present invention will be described in detail from the perspective of modular functional entities. The automated test data processing equipment in the embodiments of the present invention will be described in detail from the perspective of hardware processing.

[0163] Figure 8 This is a schematic diagram of an automated test data processing device 800 provided in an embodiment of the present invention. The automated test data processing device 800 can vary significantly due to different configurations or performance. It may include one or more central processing units (CPUs) 810 (e.g., one or more processors) and a memory 820, and one or more storage media 830 (e.g., one or more mass storage devices) for storing application programs 833 or data 832. The memory 820 and storage media 830 can be temporary or persistent storage. The program stored in the storage media 830 may include one or more modules (not shown in the diagram), each module including a series of instruction operations on the automated test data processing device 800. Furthermore, the processor 810 may be configured to communicate with the storage media 830 and execute the series of instruction operations in the storage media 830 on the automated test data processing device 800.

[0164] The automated test data processing device 800 may also include one or more power supplies 840, one or more wired or wireless network interfaces 850, one or more input / output interfaces 860, and / or one or more operating systems 831, such as Windows Server, Mac OS X, Unix, Linux, FreeBSD, etc. Those skilled in the art will understand that... Figure 8 The illustrated structure of the automated test data processing device does not constitute a limitation on the automated test data processing device, and may include more or fewer components than illustrated, or combine certain components, or have different component arrangements.

[0165] The present invention also provides a computer-readable storage medium, which can be a non-volatile computer-readable storage medium or a volatile computer-readable storage medium, wherein the computer-readable storage medium stores instructions that, when executed on a computer, cause the computer to perform the steps of an automated test data processing method.

[0166] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0167] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0168] The above embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method of processing automated test data, characterized by, The method for processing the automated test data includes: The interface test case file is read by a pre-created main thread, and the interface test cases in the interface test case file are automatically tested by the main thread to obtain the execution results. The execution results are written to a pre-set result file to obtain the target automated execution result file. The system connects to the pre-configured server corresponding to the pre-created sub-thread and reads the server log information of the pre-configured server after a successful connection. The sub-thread performs anomaly detection on the server log information to obtain target anomaly log information, and writes the target anomaly log information into a preset anomaly log file to obtain the target anomaly log file; Obtain the resource data of the preset server, write the resource data into the preset server resource file to obtain the target server resource file, wherein the resource data includes process CPU usage information and process memory usage information; According to a preset sending method, the target automated execution result file, the target exception log file, and the target server resource file are sent to a preset feedback terminal. This includes: performing statistical analysis on the target automated execution result file and the target exception log file to obtain the exception rate, exception duration, and exception range; generating a visualization chart based on the exception rate, the exception duration, and the exception range; and retrieving the corresponding target server performance level from a preset server performance level table based on the resource data in the target server resource file; obtaining a preset email template and the email address corresponding to the preset feedback terminal; generating a feedback email containing the target automated execution result file, the target exception log file, the target server resource file, the visualization chart, and the target server performance level based on the email template and the email address; and sending the feedback email to the preset feedback terminal.

2. The method of claim 1, wherein, The process involves reading an interface test case file using a pre-created main thread, performing automated testing on the interface test cases in the file using the main thread to obtain execution results, and writing the execution results into a pre-defined result file to obtain the target automated execution result file, including: The interface test case file is read by a pre-created main thread, and it is determined whether the content of the interface test case file is empty. If the content of the interface test case file is not empty, a preset function is called to obtain the parameter information of each interface test case in the interface test case file. The parameter information includes the parameter, the value corresponding to each parameter, and the index value corresponding to each parameter. The corresponding interface request method is invoked based on the parameter information, and the interface request is triggered through the interface request method to obtain the interface response result; The interface response result is verified to obtain the test case execution result of the interface test case. The test case execution result is written into a preset result file to obtain the execution result file. Determine whether the last line of the execution result file is empty. If the last line of the execution result file is empty, then the execution result file is identified as the target automated execution result file.

3. The method of claim 1, wherein, The step of connecting to a pre-created sub-thread and reading the server log information of the pre-created server after a successful connection includes: The configuration file is obtained through a pre-created sub-thread, and the configuration information in the configuration file is read. The configuration information includes server connection information and log exception keyword information. The system connects to the pre-defined server corresponding to the sub-thread using the pre-defined Secure Shell protocol commands and the server connection information, and obtains the connection result. If the connection result is successful, then read the server log information of the preset server after the successful connection.

4. The automated test data processing method according to claim 3, characterized in that, The process of performing anomaly detection on the server log information through the sub-thread to obtain target anomaly log information, and writing the target anomaly log information into a preset anomaly log file to obtain the target anomaly log file includes: The server log information is matched cyclically using the sub-thread and the log exception keyword information until the interface test cases in the interface test case file are executed, and the target exception log information is obtained. The target anomaly log information is compared and analyzed with the contents of a preset anomaly log file, and the target anomaly log information after comparison and analysis is written into the preset anomaly log file to obtain the target anomaly log file.

5. The automated test data processing method according to claim 4, characterized in that, The process involves repeatedly matching the server log information using the sub-thread and the log exception keyword information until the interface test cases in the interface test case file have been executed, thereby obtaining the target exception log information, including: The sub-thread extracts keywords from the server log information to obtain initial log keywords. Based on the log exception keywords in the log exception keyword information, the corresponding target log keywords are matched from the initial log keywords. The log exception keyword information includes log exception keywords, as well as the exception keyword sequence and exception log template corresponding to the log exception keywords. An initial keyword sequence for the target log keywords is generated, and the initial keyword sequence is compared with the abnormal keyword sequence to obtain the target keyword sequence corresponding to the abnormal keyword sequence. Extract the initial exception log information corresponding to the target keyword sequence from the server log information, compare and analyze the initial exception log information with the exception log template, until the interface test cases in the interface test case file are executed, and obtain the target exception log information corresponding to the exception log template.

6. The method for processing automated test data according to claim 4, characterized in that, The step of comparing and analyzing the target anomaly log information with the contents of a preset anomaly log file, and writing the compared and analyzed target anomaly log information into the preset anomaly log file to obtain the target anomaly log file includes: Obtain the context information of the target log keywords from the target anomaly log information; Determine whether the content in the preset exception log file contains information identical to the context information; If the content of the preset exception log file does not contain information identical to the context information, then the target exception log information is written into the preset exception log file to obtain the target exception log file.

7. An automated test data processing device, characterized in that, The automated test data processing device includes: The execution writing module is used to read the interface test case file through a pre-created main thread, perform automated testing on the interface test cases in the interface test case file through the main thread to obtain the execution results, and write the execution results into a pre-set result file to obtain the target automated execution result file; The connection reading module is used to connect to the preset server corresponding to the preset thread through a pre-created sub-thread, and read the server log information of the preset server after the connection is successful. The detection and writing module is used to perform anomaly detection on the server log information through the sub-thread, obtain the target anomaly log information, and write the target anomaly log information into a preset anomaly log file to obtain the target anomaly log file; The acquisition and writing module is used to acquire the resource data of the preset server, write the resource data into the preset server resource file, and obtain the target server resource file. The resource data includes information on the process's CPU usage and the process's memory usage. The sending module is used to send the target automated execution result file, the target exception log file, and the target server resource file to the preset feedback terminal according to the preset sending method; The sending module is specifically used for: performing statistical analysis on the target automated execution result file and the target exception log file to obtain the exception rate, exception duration, and exception range; generating a visualization chart based on the exception rate, the exception duration, and the exception range; and retrieving a preset server performance level table based on the resource data in the target server resource file to obtain the corresponding target server performance level; obtaining a preset email template and the email address corresponding to the preset feedback terminal; generating a feedback email containing the target automated execution result file, the target exception log file, the target server resource file, the visualization chart, and the target server performance level based on the email template and the email address; and sending the feedback email to the preset feedback terminal.

8. An automated test data processing device, characterized in that, The automated test data processing device includes: a memory and at least one processor, wherein the memory stores instructions; The at least one processor invokes the instructions in the memory to cause the automated test data processing device to execute the automated test data processing method as described in any one of claims 1-6.

9. A computer-readable storage medium storing instructions thereon, characterized in that, When the instruction is executed by the processor, it implements the automated test data processing method as described in any one of claims 1-6.

Images