A test case generation execution method and system applied to intelligent parking management

Abstract

This invention discloses a test case generation and execution method and system for smart parking management, relating to the field of intelligent road parking management testing. The method includes: extracting interface call information, vehicle identification information, user identification information, the business process with the most frequently used interfaces corresponding to vehicle identification information, and the business process with the most frequently used interfaces corresponding to user identification information from the operation log files of each smart parking management server within a preset time period; generating functional test case tables and scenario test case tables based on the extracted information; and executing the test cases in the functional and scenario test case tables in ascending order of test case generation time at a preset time and generating a test report. This achieves targeted automated test analysis of the current system based on the business characteristics of smart parking, thereby improving the efficiency and accuracy of testing in the field of smart parking management.

Description

Technical Field

[0001] This invention relates to the field of intelligent parking management testing, and in particular to a method and system for generating and executing test cases for intelligent parking management. Background Technology

[0002] With increasing government investment in urban parking resources, especially on-street parking, in recent years, more and more roadside parking spaces have been put into operation. The efficiency and accuracy of intelligent parking management are inseparable from the testing of intelligent parking management software. Currently, in the field of software testing, test cases need to be determined and designed manually. However, due to the complexity of intelligent parking management systems, the number of test cases required is large, and the scenarios are highly complex. Currently, relying solely on manual design of functional and scenario test cases for intelligent parking management is costly in terms of manpower and time, and may also deviate from actual scenarios, failing to fully simulate real-world conditions. This results in low testing efficiency and difficulty in guaranteeing testing accuracy in the current field of intelligent parking management. Summary of the Invention

[0003] To address the aforementioned technical problems, this invention provides a test case generation and execution method and system for smart parking management, which can solve the problems of low testing efficiency and difficulty in guaranteeing testing accuracy in the existing smart parking management field.

[0004] To achieve the above objectives, on the one hand, the present invention provides a test case generation and execution method for intelligent parking management, the method comprising:

[0005] Extract interface call information from the operation log files of each smart parking management server within a preset time period, and store the interface call information in the basic data table of the preset database;

[0006] Based on the basic data table and the interface design document information corresponding to each interface, obtain the parameter type and parameter settings of the interface, and configure corresponding interface test cases for each interface according to the parameter type and parameter settings to generate a functional test case table.

[0007] The operation log files within the preset time period are analyzed to obtain vehicle identification information and user identification information;

[0008] After sorting the log information corresponding to vehicle identification information that appears more frequently than a preset threshold in the operation log file in ascending order according to the update time, the interface call information corresponding to the vehicle identification information is separated according to the business serial number of each smart parking business, and the business process that uses the most interfaces after separation is stored in the scenario use case table.

[0009] The business information corresponding to the user identification information that appears more frequently than a preset threshold in the operation log file is separated according to the business serial number, and the business process that uses the most interfaces is selected from the separated business information and stored in the scenario use case table.

[0010] At a preset time, the test cases in the functional test case table and the scenario test case table are executed in ascending order of test case generation time, and a test report is generated.

[0011] Furthermore, the step of extracting interface call information from the operation log files of each smart parking management server within a preset time period and storing the interface call information in the basic data table of the preset database includes:

[0012] The duplicate interface call information in the runtime log file is removed using regular expressions, and the deduplicated interface call information is stored in the basic data table of the preset database. The interface call information includes the interface request path, request method, and request parameters.

[0013] Furthermore, the step of obtaining the parameter types and parameter settings of the interfaces based on the basic data table and the interface design document information corresponding to each interface, and configuring corresponding interface test cases for each interface according to the parameter types and parameter settings, includes:

[0014] Determine whether all parameters of the current interface are required based on the interface design document information corresponding to each interface.

[0015] If not, configure the parameter types and parameter settings of the interface to allow only required fields, allow both required and optional fields to exist, and allow all parameters to be filled.

[0016] Configure corresponding interface test cases for each interface based on the parameter type and parameter settings of the interface.

[0017] Furthermore, the step of obtaining the parameter types and parameter settings of the interfaces based on the basic data table and the interface design document information corresponding to each interface, and configuring corresponding interface test cases for each interface according to the parameter types and parameter settings, includes:

[0018] Obtain the return value type of each interface based on the interface design document information corresponding to each interface;

[0019] When an interface call fails, retrieve the return value corresponding to the interface.

[0020] Set up test cases for the interface based on the return value type of the interface and the return value when the interface call fails.

[0021] Furthermore, prior to the step of storing the business process with the most frequently used interface after separation into the scenario use case table, the method further includes:

[0022] If the scenario use case table contains data with the same number and order of API calls as the business process that uses the most APIs, then delete the data for the business process that uses the most APIs.

[0023] On the other hand, the present invention provides a test case generation and execution system for smart parking management. The system includes: an extraction unit, used to extract interface call information from the running log files of each smart parking management server within a preset time period, and store the interface call information in the basic data table of a preset database;

[0024] The generation unit is used to obtain the parameter type and parameter settings of the interface based on the basic data table and the interface design document information corresponding to each interface, and to configure corresponding interface test cases for each interface according to the parameter type and parameter settings, and generate a functional test case table.

[0025] The acquisition unit is used to analyze the operation log files within the preset time period to obtain vehicle identification information and user identification information;

[0026] The storage unit is used to sort the log information corresponding to vehicle identification information that appears more frequently than a preset threshold in the operation log file in ascending order according to the update time; separate the interface call information corresponding to the vehicle identification information according to the business serial number of each smart parking business; and store the business process that uses the most interfaces after separation in the scenario use case table; and separate the business information corresponding to user identification information that appears more frequently than a preset threshold in the operation log file according to the business serial number, and filter out the business process that uses the most interfaces from the separated business information and store it in the scenario use case table.

[0027] The testing unit is used to execute the test cases in the functional test case table and the scenario test case table in ascending order of test case generation time at a preset time and generate a test report.

[0028] Furthermore, the extraction unit is specifically used to delete duplicate interface call information in the running log file using regular expressions, and store the deduplicated interface call information in the basic data table of a preset database. The interface call information includes the interface request path, request method, and request parameters.

[0029] Furthermore, the generation unit is specifically used to determine whether all parameters of the current interface are required fields based on the interface design document information corresponding to each interface; if not, the parameter type and parameter settings of the interface are configured to allow only required fields to be filled, allow both required and non-required fields to exist, and allow all parameters to be filled; and configure corresponding interface test cases for each interface according to the parameter type and parameter settings of the interface.

[0030] Furthermore, the generation unit is specifically used to obtain the return value type of each interface according to the interface design document information corresponding to each interface; when an interface call fails, obtain the return value of the interface; and set test cases for the interface according to the return value type of the interface and the return value corresponding to the interface call failure.

[0031] Furthermore, the storage unit is also configured to delete the data of the business process that uses the most interfaces if there is data in the scenario use case table that has the same number and order of calling interfaces as the business process that uses the most interfaces.

[0032] This invention provides a test case generation and execution method and system for smart parking management. Based on the operation log files of each smart parking management server within a preset time period, it extracts information such as interface call information, vehicle identification information, user identification information, the business process with the most frequently used interfaces corresponding to vehicle identification information, and the business process with the most frequently used interfaces corresponding to user identification information. Based on the extracted information, it generates functional test case tables and scenario test case tables, respectively. At a preset time, it executes the test cases in the functional test case tables and scenario test case tables in ascending order of test case generation time and generates a test report. This achieves targeted automated test analysis of the current system based on the business characteristics of smart parking, thereby improving the efficiency and accuracy of testing in the field of smart parking management. Attached Figure Description

[0033] Figure 1 This invention provides a business process diagram for a test case generation and execution method applied to intelligent parking management.

[0034] Figure 2 This is a schematic diagram of the structure of a test case generation and execution system for smart parking management provided by the present invention. Detailed Implementation

[0035] The technical solution of the present invention will be further described in detail below with reference to the accompanying drawings and embodiments.

[0036] like Figure 1 As shown in the figure, an embodiment of the present invention provides a test case generation and execution method for smart parking management, which includes the following steps:

[0037] 101. Extract the interface call information from the operation log files of each smart parking management server within a preset time period, and store the interface call information in the basic data table of the preset database.

[0038] In this embodiment of the invention, step 101 may specifically include: deleting duplicate interface call information from the running log file using regular expressions, and storing the deduplicated interface call information in a basic data table of a preset database. The interface call information includes the interface's request path, request method, and request parameters.

[0039] Specifically, for example, the system connects to the smart parking system via FTP protocol. At 1:00 AM daily, it can retrieve the previous day's operational log files from each smart parking management server via FTP. After obtaining the log files, the files are categorized and managed locally according to their file service source, stored in different folders. At 1:30 AM daily, the system parses the log files retrieved from each server, analyzing their content. First, it filters out the interface call information in the current log file, using regular expressions to extract all called interface information, including the interface request path, request method, and request parameters. Duplicate interface call information is then removed. Finally, all interface data is stored in the basic data table of the MySQL database. Before storing data in the database, the system checks if the interface data to be inserted already exists in the basic data table. If it already exists, it is not inserted; otherwise, it is inserted into the current basic data table.

[0040] 102. Based on the basic data table and the interface design document information corresponding to each interface, obtain the parameter type and parameter settings of the interface, and configure corresponding interface test cases for each interface according to the parameter type and parameter settings to generate a functional test case table.

[0041] In this embodiment of the invention, step 102 may specifically include: determining whether all parameters of the current interface are required fields based on the interface design document information corresponding to each interface; if not, configuring the parameter type and parameter settings of the interface to only require fields, require and optional fields coexisting, or all parameters being filled; configuring corresponding interface test cases for each interface based on the parameter type and parameter settings of the interface. Alternatively, obtaining the return value type corresponding to each interface based on the interface design document information corresponding to each interface; when an interface call fails, obtaining the return value corresponding to the interface; setting test cases corresponding to the interface based on the return value type corresponding to the interface and the return value corresponding to the interface call failure.

[0042] Specifically, for example, after obtaining the basic data table, the service reads and analyzes the obtained basic data. When reading the basic data table, the service combines the corresponding interface design document information to obtain the parameter types and parameter settings of the interface. Then, different interface test cases are designed for each interface. The test cases can be designed in two ways: positive test cases and negative test cases. Positive test cases first confirm whether all parameters of the current interface are required. If not, the positive test cases can be designed in three ways: only required fields are filled, required and non-required fields coexist, and all parameters are filled. The reverse test cases first determine the return value type of the interface based on the interface documentation, identifying the values ​​returned when the interface call fails. Then, design corresponding test cases for different return scenarios. Next, design different reverse test cases for different parameter values. When designing test cases for parameter values, equivalence classes and boundary values ​​can be used to design test cases for the interface parameters, generating different test cases. Finally, when designing reverse test cases for a single interface, different reverse test cases can be designed based on whether a parameter is missing. Finally, all test cases for each interface are inserted into the functional test case table as needed, thus generating the functional test case table, which is mainly responsible for storing all functional test cases in the system.

[0043] 103. Analyze the operation log files within the preset time period to obtain vehicle identification information and user identification information.

[0044] In this embodiment of the invention, the analysis of user messages from the log file mainly focuses on two dimensions: license plate number and mobile phone number. This is because in the field of smart parking, vehicle entry, vehicle exit, coupons, parking cards, etc. are all associated with the license plate number, while the payment of parking fees and the issuance of coupons and parking cards are also based on the user's mobile phone number.

[0045] 104. After sorting the log information corresponding to vehicle identification information that appears more frequently than a preset threshold in the operation log file in ascending order according to the update time, separate the interface call information corresponding to the vehicle identification information according to the business serial number of each smart parking business, and store the business process that uses the most interfaces after separation in the scenario use case table.

[0046] Specifically, for example, analysis can be performed based on license plate numbers. Regular expressions can be used to obtain license plate information from the current log file, filter out the license plate numbers that appear frequently, separate the logs for these license plate numbers, and then sort the logs for each type of license plate number in ascending order according to the update time. After sorting, all interface call information for the current license plate number is separated according to the business serial number of each business. After separation, the process that uses the most interfaces is selected, and then the process is stored as a scenario use case in the scenario use case table. Before storing it in the table, it is compared with the existing data in the scenario use case table. If there is data with the same number and order of interface calls, it is not inserted into the current data; otherwise, it is inserted into the current scenario use case table.

[0047] 105. Separate the business information corresponding to the user identification information that appears more frequently than a preset threshold in the operation log file according to the business serial number, and select the business process that uses the most interfaces from the separated business information and store it in the scenario use case table.

[0048] Specifically, for example, log information in the current file is filtered by mobile phone number. After filtering out the mobile phone numbers that appear frequently, the logs associated with the current mobile phone number are filtered and summarized. Then, they are separated according to the business transaction number of each business. After separation, the process that uses the most interfaces is filtered out. Then, the process is stored as a scenario use case in the scenario use case table. Before storing it in the table, it is compared with the existing data in the scenario use case table. If there is data with the same number and order of interface calls, the current data is not inserted. Otherwise, it is inserted into the current scenario use case table to generate the corresponding scenario use case.

[0049] In an embodiment of the present invention, in order to further improve the accuracy of the scenario use case table, before storing the business process with the most interfaces after separation into the scenario use case table, the method may further include: if there is data in the scenario use case table that has the same number and order of calling interfaces as the business process with the most interfaces, then delete the data of the business process with the most interfaces.

[0050] 106. At a preset time, execute the test cases in the functional test case table and the scenario test case table in ascending order of test case generation time and generate a test report.

[0051] Specifically, for example, after functional test cases and scenario test cases are automatically generated, an automated testing service needs to read the functional test case table and scenario test case table in the MySQL database at 1:30 a.m. every day. When reading, the automated testing service prioritizes reading functional test cases, and the reading process is executed in ascending order of test case generation time. After the functional test case table is read, the scenario test case table is read automatically. When all scenario test cases have been executed, an automated test report is generated, forming a complete test plan.

[0052] This invention provides a test case generation and execution method for smart parking management. Based on the operation log files of each smart parking management server within a preset time period, it extracts information such as interface call information, vehicle identification information, user identification information, the business process with the most frequently used interfaces corresponding to vehicle identification information, and the business process with the most frequently used interfaces corresponding to user identification information. Based on the extracted information, it generates functional test case tables and scenario test case tables, respectively. At a preset time, it executes the test cases in the functional and scenario test case tables in ascending order of test case generation time and generates a test report. This achieves targeted automated test analysis of the current system based on the business characteristics of smart parking, thereby improving the efficiency and accuracy of testing in the field of smart parking management.

[0053] To implement the method provided in the embodiments of the present invention, the embodiments of the present invention provide a test case generation and execution system applied to intelligent parking management, such as... Figure 2 As shown, the system includes: an extraction unit 21, a generation unit 22, an acquisition unit 23, a storage unit 24, and a testing unit 25;

[0054] Extraction unit 21 is used to extract interface call information from the operation log files of each smart parking management server within a preset time period, and store the interface call information in the basic data table of the preset database.

[0055] The generation unit 22 is used to obtain the parameter type and parameter settings of the interface based on the basic data table and the interface design document information corresponding to each interface, and to configure corresponding interface test cases for each interface according to the parameter type and parameter settings, thereby generating a functional test case table.

[0056] The acquisition unit 23 is used to analyze the operation log files within the preset time period to obtain vehicle identification information and user identification information.

[0057] Storage unit 24 is used to sort the log information corresponding to vehicle identification information that appears more frequently than a preset threshold in the operation log file in ascending order according to the update time, separate the interface call information corresponding to the vehicle identification information according to the business serial number of each smart parking business, and store the business process that uses the most interfaces after separation into the scenario use case table; separate the business information corresponding to user identification information that appears more frequently than a preset threshold in the operation log file according to the business serial number, and filter out the business process that uses the most interfaces from the separated business information and store it into the scenario use case table.

[0058] Test unit 25 is used to execute test cases in the functional test case table and the scenario test case table in ascending order of test case generation time at a preset time and generate a test report.

[0059] Furthermore, the extraction unit 21 is specifically used to delete duplicate interface call information in the running log file using regular expressions, and store the deduplicated interface call information in the basic data table of the preset database. The interface call information includes the interface request path, request method, and request parameters.

[0060] Furthermore, the generation unit 22 is specifically used to determine whether all parameters of the current interface are required fields based on the interface design document information corresponding to each interface; if not, the parameter type and parameter settings of the interface are configured to allow only required fields to be filled, allow both required and non-required fields to exist, and allow all parameters to be filled; and configure corresponding interface test cases for each interface according to the parameter type and parameter settings of the interface.

[0061] Furthermore, the generation unit 22 is specifically used to obtain the return value type of each interface according to the interface design document information corresponding to each interface; when an interface call fails, obtain the return value of the interface; and set test cases for the interface according to the return value type of the interface and the return value corresponding to the interface call failure.

[0062] Furthermore, the storage unit 24 is also used to delete the data of the business process that uses the most interfaces if there is data in the scenario use case table that has the same number and order of calling interfaces as the business process that uses the most interfaces.

[0063] This invention provides a test case generation and execution system for smart parking management. Based on the operation log files of each smart parking management server within a preset time period, it extracts information such as interface call information, vehicle identification information, user identification information, the business process with the most frequently used interfaces corresponding to vehicle identification information, and the business process with the most frequently used interfaces corresponding to user identification information. Based on the extracted information, it generates functional test case tables and scenario test case tables, respectively. At a preset time, it executes the test cases in the functional and scenario test case tables in ascending order of test case generation time and generates a test report. This system enables targeted automated test analysis of the current system based on the business characteristics of smart parking, thereby improving the efficiency and accuracy of testing in the field of smart parking management.

[0064] It should be understood that the specific order or hierarchy of steps in the disclosed process is an example of an exemplary method. Based on design preferences, it should be understood that the specific order or hierarchy of steps in the process may be rearranged without departing from the scope of this disclosure. The appended method claims provide elements of various steps in an exemplary order and are not intended to limit the scope to the specific order or hierarchy described.

[0065] In the above detailed description, various features are combined together in a single embodiment to simplify this disclosure. This approach to disclosure should not be construed as reflecting an intention that embodiments of the claimed subject matter require more features than are explicitly stated in each claim. Rather, as reflected in the appended claims, the invention is presented with fewer features than all of the features of the single disclosed embodiment. Therefore, the appended claims are hereby explicitly incorporated into the detailed description, wherein each claim stands alone as a preferred embodiment of the invention.

[0066] The disclosed embodiments have been described above to enable any person skilled in the art to implement or use the present invention. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein can be applied to other embodiments without departing from the spirit and scope of this disclosure. Therefore, this disclosure is not limited to the embodiments given herein, but is consistent with the broadest scope of the principles and novel features disclosed in this application.

[0067] The foregoing description includes examples of one or more embodiments. It is certainly impossible to describe all possible combinations of components or methods in order to describe the above embodiments, but those skilled in the art will recognize that further combinations and arrangements of the various embodiments are possible. Therefore, the embodiments described herein are intended to cover all such changes, modifications, and variations that fall within the scope of the appended claims. Furthermore, the term "comprising" as used in the specification or claims is interpreted in a manner similar to the term "including," as interpreted when used as a conjunction in the claims. Additionally, the use of any term "or" in the specification of the claims is intended to mean "non-exclusive or."

[0068] Those skilled in the art will also understand that the various illustrative logical blocks, units, and steps listed in the embodiments of the present invention can be implemented by electronic hardware, computer software, or a combination of both. To clearly demonstrate the interchangeability of hardware and software, the functions of the various illustrative components, units, and steps described above have been generally described. Whether such functionality is implemented through hardware or software depends on the specific application and the overall system design requirements. Those skilled in the art can implement the described functions using various methods for each specific application, but such implementation should not be construed as exceeding the scope of protection of the embodiments of the present invention.

[0069] The various illustrative logic blocks or units described in the embodiments of this invention can be implemented or operate the described functions using a general-purpose processor, digital signal processor, application-specific integrated circuit (ASIC), field-programmable gate array or other programmable logic system, discrete gate or transistor logic, discrete hardware components, or any combination thereof. The general-purpose processor can be a microprocessor; alternatively, it can be any conventional processor, controller, microcontroller, or state machine. The processor can also be implemented using a combination of computing systems, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors combined with a digital signal processor core, or any other similar configuration.

[0070] The steps of the methods or algorithms described in the embodiments of this invention can be directly embedded in hardware, a software module executed by a processor, or a combination of both. The software module can be stored in RAM, flash memory, ROM, EPROM, EEPROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium in the art. Exemplarily, the storage medium can be connected to the processor so that the processor can read information from and write information to the storage medium. Optionally, the storage medium can also be integrated into the processor. The processor and storage medium can be housed in an ASIC, which can be housed in a user terminal. Optionally, the processor and storage medium can also be housed in different components of the user terminal.

[0071] In one or more exemplary designs, the functions described in the embodiments of the present invention can be implemented in hardware, software, firmware, or any combination of these three. If implemented in software, these functions can be stored on a computer-readable medium or transmitted on a computer-readable medium in the form of one or more instructions or code. Computer-readable media include computer storage media and communication media that facilitate the transfer of computer programs from one place to another. Storage media can be any available media that can be accessed by a general-purpose or special-purpose computer. For example, such computer-readable media can include, but is not limited to, RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage systems, or any other medium that can be used to carry or store program code in the form of instructions or data structures and other forms that can be read by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Furthermore, any connection can be suitably defined as a computer-readable medium, for example, if the software is transmitted from a website, server, or other remote resource via a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wirelessly, such as infrared, wireless, and microwave, it is also included in the defined computer-readable medium. The disks and discs mentioned include compressed disks, laser discs, optical discs, DVDs, floppy disks, and Blu-ray discs. Disks typically copy data magnetically, while disks typically copy data optically using lasers. Combinations of the above can also be contained in computer-readable media.

[0072] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of the present invention. It should be understood that the above descriptions are merely specific embodiments of the present invention and are not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, or improvements made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A method for generating and executing test cases for intelligent parking management, characterized in that, The method includes: Extract interface call information from the operation log files of each smart parking management server within a preset time period, and store the interface call information in the basic data table of the preset database; Based on the basic data table and the interface design document information corresponding to each interface, obtain the parameter type and parameter settings of the interface, and configure corresponding interface test cases for each interface according to the parameter type and parameter settings to generate a functional test case table. The operation log files within the preset time period are analyzed to obtain vehicle identification information and user identification information; After sorting the log information corresponding to vehicle identification information that appears more frequently than a preset threshold in the operation log file in ascending order according to the update time, the interface call information corresponding to the vehicle identification information is separated according to the business serial number of each smart parking business, and the business process that uses the most interfaces after separation is stored in the scenario use case table. The business information corresponding to the user identification information that appears more frequently than a preset threshold in the operation log file is separated according to the business serial number, and the business process that uses the most interfaces is selected from the separated business information and stored in the scenario use case table. At a preset time, the test cases in the functional test case table and the scenario test case table are executed in ascending order of test case generation time, and a test report is generated.

2. The test case generation and execution method for intelligent parking management according to claim 1, wherein, The steps of extracting interface call information from the operation log files of each smart parking management server within a preset time period and storing the interface call information in the basic data table of the preset database include: The duplicate interface call information in the runtime log file is removed using regular expressions, and the deduplicated interface call information is stored in the basic data table of the preset database. The interface call information includes the interface request path, request method, and request parameters.

3. The test case generation and execution method for intelligent parking management according to claim 1, wherein, The steps of obtaining the parameter types and parameter settings of the interfaces based on the basic data table and the interface design document information corresponding to each interface, and configuring corresponding interface test cases for each interface according to the parameter types and parameter settings, include: Determine whether all parameters of the current interface are required based on the interface design document information corresponding to each interface. If not, configure the parameter types and parameter settings of the interface to allow only required fields, allow both required and optional fields to exist, and allow all parameters to be filled. Configure corresponding interface test cases for each interface based on the parameter type and parameter settings of the interface.

4. The test case generation and execution method for intelligent parking management according to claim 3, wherein, The steps of obtaining the parameter types and parameter settings of the interfaces based on the basic data table and the interface design document information corresponding to each interface, and configuring corresponding interface test cases for each interface according to the parameter types and parameter settings, include: Obtain the return value type of each interface based on the interface design document information corresponding to each interface; When an interface call fails, retrieve the return value corresponding to the interface. Set up test cases for the interface based on the return value type of the interface and the return value when the interface call fails.

5. The test case generation and execution method for intelligent parking management according to claim 1, characterized in that, Before the step of storing the business process with the most frequently used interface after separation into the scenario use case table, the method further includes: If the scenario use case table contains data with the same number and order of API calls as the business process that uses the most APIs, then delete the data for the business process that uses the most APIs.

6. A test case generation and execution system for intelligent parking management, comprising: The system includes: The extraction unit is used to extract interface call information from the operation log files of each smart parking management server within a preset time period, and store the interface call information in the basic data table of the preset database; The generation unit is used to obtain the parameter type and parameter settings of the interface based on the basic data table and the interface design document information corresponding to each interface, and to configure corresponding interface test cases for each interface according to the parameter type and parameter settings, and generate a functional test case table. The acquisition unit is used to analyze the operation log files within the preset time period to obtain vehicle identification information and user identification information; The storage unit is used to sort the log information corresponding to vehicle identification information that appears more frequently than a preset threshold in the operation log file in ascending order according to the update time; separate the interface call information corresponding to the vehicle identification information according to the business serial number of each smart parking business; and store the business process that uses the most interfaces after separation in the scenario use case table; and separate the business information corresponding to user identification information that appears more frequently than a preset threshold in the operation log file according to the business serial number, and filter out the business process that uses the most interfaces from the separated business information and store it in the scenario use case table. The testing unit is used to execute the test cases in the functional test case table and the scenario test case table in ascending order of test case generation time at a preset time and generate a test report.

7. A test case generation and execution system for intelligent parking management according to claim 6, characterized in that, The extraction unit is specifically used to delete duplicate interface call information in the running log file using regular expressions, and to store the deduplicated interface call information in the basic data table of a preset database. The interface call information includes the interface request path, request method, and request parameters.

8. A test case generation and execution system for intelligent parking management according to claim 6, characterized in that, The generation unit is specifically used to determine whether all parameters of the current interface are required fields based on the interface design document information corresponding to each interface; if not, it configures the parameter type and parameter settings of the interface to fill only required fields, have both required and non-required fields, or fill all parameters; and configures corresponding interface test cases for each interface according to the parameter type and parameter settings of the interface.

9. A test case generation and execution system for intelligent parking management according to claim 8, characterized in that, The generation unit is further configured to obtain the return value type of each interface based on the interface design document information of each interface; when an interface call fails, obtain the return value of the interface; and set test cases for the interface based on the return value type of the interface and the return value corresponding to the failed interface call.

10. The test case generation and execution system for intelligent parking management as claimed in claim 6 wherein, The storage unit is further configured to delete the service process data with the most used interface if the scene use case table contains data consistent with the number and sequence of the calling interfaces corresponding to the service process with the most used interface.

Images