Vehicle-mounted report automatic test method, device, vehicle, medium and program

Abstract

The invention relates to the technical field of cloud platform testing, in particular to a vehicle-mounted report automatic testing method and device, a vehicle, a medium and a program, and the method comprises the steps: obtaining a scene testing demand of a user; a corresponding signal message is generated according to the scene test requirement, the signal message is sent to the server through a preset protocol, and the server analyzes the signal message to generate a corresponding interesting report and pushes the interesting report to the client; and identifying an expected interesting report corresponding to the scene test requirement, and controlling the test system to execute a corresponding control instruction according to a comparison result of the interesting report and the expected interesting report so as to generate an automatic test result. Therefore, the problems of long test time consumption, difficulty in simulation of complex scenes, low applicability, error proneness to regression test, low efficiency of manual server data checking and the like caused by multi-scene and multi-parameter configuration in related technologies are solved.

Description

Technical Field

[0001] This application relates to the technical field of cloud platform testing, and particularly relates to an automated testing method, device, vehicle, medium and program for in-vehicle reports. Background Art

[0002] With the rapid development of automotive intelligent and connected technologies, the fuel vehicle cloud platform needs to process a large amount of driving behavior data, and generate diverse interesting reports and push messages. The test complexity of such business scenarios has increased significantly, and traditional testing methods face the following technical bottlenecks:

[0003] (1) Low efficiency of manual testing: The interesting reports of fuel vehicles involve multi-dimensional parameters (such as ignition status, mileage, vehicle speed, fuel consumption, etc.), and the push messages and platform data generated under different parameter combinations are significantly different. Testers need to manually configure parameters, execute tests, and check results item by item for each scenario, which is time-consuming and laborious, and it is difficult to cover all scenarios. In performance testing, it is necessary to simulate reporting hundreds of driving behavior signals or push messages in a short period of time. Traditional manual operations cannot accurately simulate high-concurrency scenarios, resulting in insufficient performance verification.

[0004] (2) Poor reliability of regression testing: During the iteration of the cloud platform, regression testing needs to be performed on historical scenarios every time there is an update; manual repeated operations are prone to introducing human oversights, and it is impossible to ensure the consistency of test conditions, resulting in difficulties in reproducing problems. Summary of the Invention

[0005] This application provides an automated testing method, device, vehicle, medium and program for in-vehicle reports to solve the problems in related technologies, such as long testing time due to multi-scenarios and multi-parameter configurations, difficulty in simulating complex scenarios, low applicability, easy errors in regression testing, and low efficiency of manually checking server data.

[0006] In a first aspect embodiment of this application, an automated testing method for in-vehicle reports is provided, including the following steps: obtaining the scenario test requirements of a user; generating a corresponding signal message according to the scenario test requirements, and sending the signal message to a server through a preset protocol, where the server parses the signal message to generate a corresponding interesting report, and pushes the interesting report to a client; identifying the expected interesting report corresponding to the scenario test requirements, and controlling a test system to execute corresponding control instructions according to the comparison result between the interesting report and the expected interesting report to generate an automated test result.

[0007] Optionally, the identifying the expected interesting report corresponding to the scenario test requirements includes: extracting keywords of the scenario test requirements; calling corresponding test cases in a preset database according to each keyword and the expected test results corresponding to the test cases; generating a corresponding expected interesting report according to multiple expected test results.

[0008] Optionally, before identifying the expected interesting report corresponding to the scenario test requirement, it includes: detecting whether the interesting report is successfully pushed; if the push is successful, identifying the expected interesting report corresponding to the scenario test requirement, otherwise triggering a repeated push request until the preset condition is met and the push stops.

[0009] Optionally, controlling the test system to execute the corresponding control instruction according to the comparison result between the interesting report and the expected interesting report to generate an automated test result includes: comparing the content of the interesting report and the expected interesting report; if the comparison result is consistent, parsing the test conditions and parameters of the interesting report to generate the corresponding control instruction; simulating the test according to the control instruction to generate an automated test result.

[0010] Optionally, obtaining the scenario test requirement of the user includes: identifying the input data of the user on the test interface; filtering the corresponding test conditions through multi-level linkage according to the input data to generate a test scenario; identifying the verification test intention of the user, and triggering the target logic according to the verification test intention to process the scenario test requirement of the user.

[0011] Optionally, before identifying the input data of the user on the test interface, it includes: developing a test interface based on a target framework and target components, where the test interface supports cascading filtering of test scenario parameters.

[0012] An embodiment of the second aspect of the present application provides an in-vehicle report automated test device, including: an acquisition module, configured to acquire the scenario test requirement of the user; a generation module, configured to generate a corresponding signal message according to the scenario test requirement, and send the signal message to the server through a preset protocol, where the server parses the signal message to generate a corresponding interesting report and pushes the interesting report to the client; an identification module, configured to identify the expected interesting report corresponding to the scenario test requirement, and control the test system to execute the corresponding control instruction according to the comparison result between the interesting report and the expected interesting report to generate an automated test result.

[0013] An embodiment of the third aspect of the present application provides a vehicle, including: a memory, a processor, and a computer program stored on the memory and executable on the processor, and the processor executes the program to execute the in-vehicle report automated test method as described in the above embodiment.

[0014] An embodiment of the fourth aspect of the present application provides a computer-readable storage medium, on which a computer program is stored, and the program is executed by a processor to execute the in-vehicle report automated test method as described in the above embodiment.

[0015] The fifth aspect of the present application provides a computer program product, including a computer program or instructions, which when executed, implement the vehicle report automated testing method as described in the above embodiments.

[0016] Thus, the present application has at least the following beneficial effects:

[0017] (1) In the embodiments of the present application, through parameterized configuration and dynamic generation of target format messages, hundreds of driving behaviors or driving report scenarios can be simulated with one key, completely solving the problems of long manual testing time and low scenario coverage rate; at the same time, it supports high-concurrency performance testing, and can automatically send thousands of signal messages per unit time, accurately simulating real business pressure and avoiding the verification of performance bottlenecks that cannot be achieved by traditional manual operations.

[0018] (2) In the embodiments of the present application, the server push messages can be captured in real time, and the data displayed in the interesting report is compared field by field to eliminate manual verification errors and ensure that the verification results are exactly the same as expected.

[0019] (3) In the embodiments of the present application, there is no need to rely on in-vehicle hardware such as T-Box. Only parameter configuration is required to simulate full-scenario testing, saving equipment procurement and maintenance costs. The test report is automatically generated and stored in the database, reducing the workload of manual sorting and archiving.

[0020] (4) In the embodiments of the present application, the historical test scenarios and parameter configurations can be stored in the database, supporting one-key triggering of full-scale regression testing, ensuring the consistency of test conditions, avoiding missed testing or misjudgment caused by human operation errors, and improving the reliability of regression testing.

[0021] Additional aspects and advantages of the present application will be given in part in the following description, become apparent in part from the following description, or be learned through the practice of the present application. Description of the Drawings

[0022] The above and / or additional aspects and advantages of the present application will become apparent and easy to understand from the following description of the embodiments in conjunction with the drawings, where:

[0023] Figure 1 is a flowchart of a vehicle report automated testing method provided according to an embodiment of the present application;

[0024] Figure 2 is a test flowchart of a fuel vehicle interesting report automated testing system provided according to an embodiment of the present application;

[0025] Figure 3 is an example diagram of a vehicle report automated testing device provided according to an embodiment of the present application;

[0026] Figure 4Schematic diagram of the structure of a vehicle provided according to an embodiment of the present application. Detailed implementation manners

[0027] The embodiments of the present application will be described in detail below. Examples of the embodiments are shown in the accompanying drawings, where the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described by referring to the accompanying drawings are exemplary and are intended to explain the present application, and should not be construed as a limitation to the present application.

[0028] As the number of vehicle models connected to the company's projects and platforms increases, the scenarios for maintaining and pushing messages in the fuel vehicle fun report are increasing. The push message results generated for different configuration parameters in each scenario are different, and the data information saved by the platform is also different. In these business scenarios, if there is a problem in any link, the test results will be invalid. If each scenario is manually executed and verified, it will take a very long time and many test scenarios cannot be correctly simulated, seriously affecting the system development cycle and consuming a lot of manpower and time costs, and the test accuracy is very low.

[0029] When it comes to regression issues, if each scenario is regressed manually again, the regression will be very slow and error-prone; during performance testing, hundreds of push messages or reporting messages need to be sent per unit time, which cannot be achieved by traditional manual operations.

[0030] To overcome the above technical problems, an automated test tool for the fuel vehicle fun report is provided. Only need to select the business scenarios to be tested, maintain the corresponding parameter information, and click the one-key test, then the corresponding message can be reported, the app can push the corresponding message reminder, and the platform can generate the corresponding detailed information of the fun report.

[0031] The following describes the automated test method, device, vehicle, storage medium and program of the vehicle-mounted report according to the embodiments of the present application with reference to the accompanying drawings.

[0032] Specifically, Figure 1 It is a schematic flowchart of an automated test method for a vehicle-mounted report provided by an embodiment of the present application.

[0033] As Figure 1 shown, the automated test method for the vehicle-mounted report includes the following steps:

[0034] In step S101, obtain the user's scenario test requirements.

[0035] Among them, the scenario test requirements include test scenarios and corresponding configuration parameters.

[0036] It can be understood that the embodiments of the present application can obtain the user's scenario test requirements, so as to generate corresponding signal messages according to the scenario test requirements subsequently.

[0037] It should be noted that the basic parameter configuration includes driving behavior parameters, environmental parameters, and business rule parameters. Among them, the driving behavior parameters may include vehicle status, driving data, and driving events; the environmental parameters include temperature, humidity, and road conditions; the business rule parameters include the type of interesting report and the triggering conditions for message push. The test scenario classification includes function verification scenarios, performance test scenarios, and exception and boundary scenarios.

[0038] Specifically, the present application adds a custom scenario template function to the test interface, allowing users to build complex test scenarios through drag-and-drop components, supporting nested rules. Among them, the drag-and-drop components include parameter input boxes and logical condition branches; for example: if "average vehicle speed > 100 KM / H", then trigger "emergency braking signal reporting", etc.

[0039] In the embodiment of the present application, obtaining the user's scenario test requirements includes: identifying the input data of the user on the test interface; generating a test scenario by filtering the corresponding test conditions through multi-level linkage according to the input data; identifying the user's verification test intention, and triggering the target logic to process the user's scenario test requirements according to the verification test intention.

[0040] It can be understood that the embodiment of the present application can identify the input data of the user on the test interface to improve the user interaction experience and ensure that the input data can be directly used for message generation and logical judgment; generate a test scenario by filtering the corresponding test conditions through multi-level linkage according to the input data, reduce invalid parameter combinations through cascading filtering, improve the scenario configuration efficiency, identify the user's verification test intention, and trigger the target logic to process the user's scenario test requirements according to the verification test intention, avoiding waste of test resources caused by misoperations.

[0041] It should be noted that the present application can develop a responsive test interface based on Vue components to capture the operation data of the user in controls such as input boxes, drop-down menus, and check boxes in real time; perform type verification and normalization processing on the input parameters through the Django backend to avoid format errors affecting subsequent processes. According to the test type selected by the user (such as function test, performance test) and parameter combinations, map them to the preset verification logic, and train a classification model based on historical test records to identify the implicit intention of the user.

[0042] In the embodiment of the present application, before identifying the input data of the user on the test interface, it includes: developing a test interface based on the target framework and target components, where the test interface supports cascading filtering of test scenario parameters.

[0043] It can be understood that the embodiments of the present application can implement intelligent, efficient, and zero error rate of test scenario configuration based on the cascading screening test interface developed by the target framework and components, and provide core support for the automated test of the fuel vehicle cloud platform through dynamic parameter management, logical constraints, and user experience optimization.

[0044] In step S102, a corresponding signal message is generated according to the scenario test requirements, and the signal message is sent to the server through a preset protocol. The server parses the signal message to generate a corresponding interesting report and pushes the interesting report to the client.

[0045] It can be understood that the embodiments of the present application can generate a corresponding signal message according to the scenario test requirements, send the signal message to the server through a preset protocol, realize an automated closed loop from requirement input to report verification, and upgrade the traditional test process that relies on manual labor to an efficient, accurate, and scalable technical solution through full-link automation and intelligent design, significantly improving the test efficiency and quality. At the same time, it reduces the R & D and operation and maintenance costs of vehicle enterprises and provides core support for the development and verification of the intelligent connected vehicle cloud platform.

[0046] In step S103, the expected interesting report corresponding to the scenario test requirements is identified, and the test system is controlled to execute the corresponding control instruction according to the comparison result between the interesting report and the expected interesting report to generate an automated test result.

[0047] It can be understood that the embodiments of the present application can identify the expected interesting report corresponding to the scenario test requirements, control the test system to execute the corresponding control instruction according to the comparison result between the interesting report and the expected interesting report to generate an automated test result, verify the functions and performance of the cloud platform, help testers compare the test results, no longer require testers to manually compare the result information, save the test time, improve the test efficiency, and ensure the test quality.

[0048] In the embodiments of the present application, before identifying the expected interesting report corresponding to the scenario test requirements, it includes: detecting whether the interesting report is successfully pushed; if it is successfully pushed, the expected interesting report corresponding to the scenario test requirements is identified, otherwise, a repeated push request is triggered until the preset condition is met and the push stops.

[0049] Among them, the preset condition can be set according to actual needs. For example, the repeated push request is triggered 3 times, without specific limitation.

[0050] It can be understood that the embodiments of the present application can detect whether the interesting report is successfully pushed; if it is successfully pushed, the expected interesting report corresponding to the scenario test requirements is identified, otherwise, a repeated push request is triggered until the preset condition is met and the push stops, improving the push efficiency.

[0051] In the embodiments of the present application, identifying the expected interesting report corresponding to the scenario test requirements includes: extracting the keywords of the scenario test requirements; calling the corresponding test cases and the expected test results corresponding to the test cases in a preset database according to each keyword; and generating the corresponding expected interesting report according to multiple expected test results.

[0052] It can be understood that the embodiments of the present application can transform the traditional manual-dependent test design into an efficient, accurate, and traceable technical process through intelligent keyword extraction, precise test case matching, and automated report generation, so as to facilitate subsequent scenario regression.

[0053] In the embodiments of the present application, controlling the test system to execute the corresponding control instructions according to the comparison result of the interesting report and the expected interesting report to generate an automated test result includes: comparing the content of the interesting report and the expected interesting report; if the comparison result is consistent, parsing the test conditions and parameters of the interesting report to generate the corresponding control instructions; and simulating the test according to the control instructions to generate the automated test result.

[0054] It can be understood that the embodiments of the present application can quickly locate the root cause of the problem and improve the test efficiency through report comparison and instruction-driven automated testing.

[0055] Specifically, the present application mainly includes the following steps according to the above content:

[0056] (1) Use the Django framework python+vue+E-Charts+psuti+pandas to develop an automated test tool for the interesting report of fuel vehicles. (2) Use python+the fuel vehicle protocol document to generate the corresponding proto according to the mqtt protocol, and parameterize according to the business scenario to generate signal messages of different driving behaviors or daily / monthly / quarterly / annual reports and report them to the platform. (3) Use python to obtain the server message push information. (4) Use python+psuti to obtain the data of the interesting report information display page associated with the driving behavior on the server and compare it with the expected results. (5) Check whether the message push information and the platform information display are consistent and generate the test result.

[0057] The vehicle report automated testing method proposed according to the embodiments of the present application obtains the scenario testing requirements of the user; generates corresponding signal messages according to the scenario testing requirements, and sends the signal messages to the server through a preset protocol; identifies the expected interesting report corresponding to the scenario testing requirements, and controls the test system to execute corresponding control instructions according to the comparison result between the interesting report and the expected interesting report to generate an automated test result. After the user configures the scenario requirements through the interface, the system automatically generates signal messages, reports to the server, captures reports and completes the comparison, realizes algorithm-level verification, avoids manual omissions, supports cascading screening, templatized parameter combination and natural language requirement parsing, can adapt to complex business scenarios, maximizes the utilization rate of test resources, and greatly reduces the human and time costs.

[0058] The following will combine Figure 2 to elaborate in detail on the vehicle report automated testing method of the present application, specifically as follows:

[0059] Step 1, use python+vue to develop a test interface;

[0060] (1) The page includes cascading screening of test scenarios, such as: vehicle ignition - vehicle shutdown - mileage - average speed - maximum speed - number of starts - mileage - driving duration - fuel consumption per 100 kilometers, etc. push message information

[0061] (2) Display of App message push information

[0062] (3) Verification result of App message push information

[0063] (4) Display of information reported to the Tsp platform

[0064] (5) Parsing and verification of information reported to the Tsp platform

[0065] Step 2, use the python language to generate corresponding proto according to the parameters obtained from the interface according to the protocol list, generate the corresponding message format and send it to the platform server through the mqtt protocol

[0066] (1) After selecting a test scenario on the test interface, click to verify the test;

[0067] (2) Generate the corresponding proto assembly through the python language + protocol list to simulate the driving behavior message of the vehicle end to send the corresponding signal

[0068] (3) Use the python language + mqtt to send the message to the gateway

[0069] Step 3, use the python language to capture the app message information pushed by the platform server and compare whether the pushed message is correct

[0070] (1) After selecting the test scenario, click the verification

[0071] (2) Obtain the server push message through Python + psutil, and obtain the specific message copy through regular expressions

[0072] (3) Finally, obtain the driving behavior information through Python

[0073] (4) Compare whether the interesting report result is consistent with the test scenario

[0074] (5) Return the test comparison result. Traditional manual checking requires retrieving in the server according to keywords such as reporting time and then checking word by word. The accuracy and efficiency are relatively low

[0075] (6) After the test results and verification content are returned, they will be displayed on the page of the test tool website for the convenience of testers to view; the test results are stored in the database according to the test time and test scenario

[0076] Step 4, obtain the page data of the driving behavior information of fuel vehicles through Python + E-Charts and compare it with the expected results

[0077] (1) After selecting the test scenario, click the verification

[0078] (2) Finally, enter the reporting result page through Python + E-Charts to verify whether the driving behavior information list is correctly increased

[0079] (3) Use Python to obtain the driving behavior signal information and associated signal information of the currently reported vehicle

[0080] (4) Use Python to verify whether the daily / monthly / quarterly / annual report information of the reported vehicle is correct. There are many fields to verify here. The comparison accuracy is 100% according to the parameters set by the scenario, and the time consumed for comparison is greatly reduced compared with manual checking, and the accuracy and efficiency are greatly improved

[0081] (5) After the test results and verification content are returned, they will be displayed on the page of the test tool website for the convenience of testers to view

[0082] (6) The test results are stored in the database according to the test time and test scenario

[0083] Step 6, use Python to organize the test results (using the pandas library with openpyxl or xlrd) and write them into Excel

[0084] (1) The test tool page displays the test results for the time period and test scenario in a list form

[0085] (2) It can be retrieved according to the test time and test scenario

[0086] (3) Export the summary test report through xlsxwriter or export all according to the search results

[0087] In summary, the present application provides a driving behavior analysis of a fuel vehicle interest report and an automated test method for daily / monthly / quarterly / annual driving reports. It simulates the reporting of associated signal messages of vehicle driving behavior and daily / monthly / quarterly / annual driving reports, captures app message push information in the server, and verifies the functions and performance of the cloud platform. It does not rely on the tbox. Only by following the business scenario of the fuel vehicle interest report and then inputting or selecting the required parameter information can a test request be submitted and a test result be generated. According to the above technical solution, all driving behavior analyses and the sending of associated signals of daily / monthly / quarterly / annual driving reports can be simulated, and function and performance problems can be verified, helping testers compare test results. There is no need for testers to manually compare result information, saving test time, improving test efficiency, and ensuring test quality.

[0088] Next, an on-vehicle report automated test device according to an embodiment of the present application will be described with reference to the accompanying drawings.

[0089] Figure 3 It is a block diagram of an on-vehicle report automated test device according to an embodiment of the present application.

[0090] As Figure 3 shown, the on-vehicle report automated test device 10 includes: an acquisition module 100, a generation module 200, and an identification module 300.

[0091] Among them, the acquisition module 100 is used to acquire the scenario test requirements of the user; the generation module 200 is used to generate corresponding signal messages according to the scenario test requirements and send the signal messages to the server through a preset protocol. The server parses the signal messages to generate corresponding interest reports and pushes the interest reports to the client; the identification module 300 is used to identify the expected interest reports corresponding to the scenario test requirements and control the test system to execute corresponding control instructions according to the comparison result between the interest reports and the expected interest reports to generate an automated test result.

[0092] It should be noted that the foregoing explanation of the embodiment of the on-vehicle report automated test method also applies to the on-vehicle report automated test device of this embodiment, and will not be repeated here.

[0093] The in-vehicle report automated testing device proposed according to the embodiments of the present application obtains the scenario testing requirements of the user; generates corresponding signal messages according to the scenario testing requirements, and sends the signal messages to the server through a preset protocol; identifies the expected interesting report corresponding to the scenario testing requirements, and controls the testing system to execute corresponding control instructions according to the comparison result between the interesting report and the expected interesting report to generate an automated test result. After the user configures the scenario requirements through the interface, the system automatically generates signal messages, reports to the server, captures reports and completes the comparison, realizes algorithm-level verification, avoids manual omissions, supports cascading screening, templated parameter combination and natural language requirement parsing, can adapt to complex business scenarios, maximizes the utilization rate of testing resources, and greatly reduces the human and time costs.

[0094] Figure 4 It is a schematic structural diagram of a vehicle provided by an embodiment of the present application. The vehicle may include:

[0095] A memory 401, a processor 402, and a computer program stored on the memory 401 and executable on the processor 402.

[0096] When the processor 402 executes the program, it implements the in-vehicle report automated testing method provided in the above embodiment.

[0097] Further, the vehicle further includes:

[0098] A communication interface 403 for communication between the memory 401 and the processor 402.

[0099] The memory 401 is used to store a computer program executable on the processor 402.

[0100] The memory 401 may include a high-speed RAM memory, and may also include non-volatile memory, such as at least one disk memory.

[0101] If the memory 401, the processor 402, and the communication interface 403 are independently implemented, the communication interface 403, the memory 401, and the processor 402 may be interconnected through a bus and complete communication with each other. The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. For the sake of representation, Figure 4It is represented only by a thick line, but it does not mean that there is only one bus or one type of bus.

[0102] Optionally, in a specific implementation, if the memory 401, the processor 402, and the communication interface 403 are integrated on a single chip, the memory 401, the processor 402, and the communication interface 403 can communicate with each other through an internal interface.

[0103] The processor 402 may be a central processing unit (CPU for short), or an application specific integrated circuit (ASIC for short), or one or more integrated circuits configured to implement the embodiments of the present application.

[0104] The embodiments of the present application further provide a computer-readable storage medium, on which a computer program or instruction is stored. When the computer program or instruction is executed by a processor, the automated vehicle report testing method as described above is implemented.

[0105] The embodiments of the present application further provide a computer program product, including a computer program or instruction. When the computer program or instruction is executed, the automated vehicle report testing method as described above is implemented.

[0106] In the description of this specification, the descriptions with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples", etc. mean that the specific features, structures, materials, or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described may be combined in any one or N embodiments or examples in a suitable manner. In addition, without contradiction, those skilled in the art can combine and combine the different embodiments or examples described in this specification and the features of different embodiments or examples.

[0107] In addition, the terms "first" and "second" are only used for descriptive purposes and cannot be understood as indicating or implying relative importance or implicitly indicating the quantity of the indicated technical features. Thus, the features defined with "first" and "second" may explicitly or implicitly include at least one of the features. In the description of the present application, the meaning of "N" is at least two, such as two, three, etc., unless otherwise specifically defined.

[0108] Any process or method description depicted in the flowchart or otherwise described herein may be understood to represent a module, segment, or portion of code including one or N executable instructions for implementing a customized logical function or process. The scope of the preferred embodiments of the present application includes additional implementations, where functions may be executed in a substantially simultaneous manner or in a reverse order according to the functions involved, rather than in the order shown or discussed, which should be understood by those skilled in the art to which the embodiments of the present application pertain.

[0109] It should be understood that the various parts of the present application may be implemented using hardware, software, firmware, or a combination thereof. In the above-described embodiments, the N steps or methods may be implemented using software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented using hardware, as in another embodiment, any one or a combination of the following techniques well known in the art may be used: discrete logic circuits having logic gate circuits for implementing logical functions on data signals, application-specific integrated circuits having appropriate combinational logic gate circuits, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), and the like.

[0110] Those of ordinary skill in the art can understand that all or part of the steps carried out in the method of the above-described embodiments can be completed by instructing relevant hardware through a program, and the program can be stored in a computer-readable storage medium. When the program is executed, it includes one or a combination of the steps of the method embodiments.

Claims

1. A vehicle-mounted report automated testing method, characterized in that: The following steps are involved: Obtain the user's scenario testing requirements; Generate a corresponding signal message according to the scenario test requirements, and send the signal message to the server through a preset protocol, wherein the server parses the signal message to generate a corresponding interesting report, and pushes the interesting report to the client; Identify the expected fun report corresponding to the scenario test requirement, and control the test system to execute corresponding control instructions based on the comparison result between the fun report and the expected fun report to generate automated test results.

2. The vehicle-mounted report automated testing method according to claim 1, characterized in that: The identifying of the expected interesting report corresponding to the scenario testing requirement includes: Extract keywords of the scenario test requirements; Calling the test case corresponding to the preset database and the expected test result corresponding to the test case according to each keyword; Generate corresponding expected interesting reports according to multiple expected test results.

3. The vehicle-mounted report automated testing method according to claim 1, characterized in that: Before identifying the expected interesting report corresponding to the scenario test requirement, it includes: Detecting whether the interesting report is pushed successfully; If the push is successful, the expected interesting report corresponding to the scenario test requirement is identified, otherwise a repeated push request is triggered until the preset conditions are met and the push is stopped.

4. The vehicle-mounted report automated testing method according to claim 1, characterized in that: The controlling the test system to execute corresponding control instructions according to the comparison result between the fun report and the expected fun report to generate an automated test result includes: comparing the content of the fun report with the content of the expected fun report; If the comparison results are consistent, the test conditions and parameters of the interesting report are analyzed to generate corresponding control instructions; Generate automated test results based on the control instruction simulation test.

5. The vehicle-mounted report automated testing method according to claim 1, characterized in that: The obtaining of the user's scenario testing requirements includes: Identify the user input data in the test interface; Generate a test scenario based on the multi-level linkage screening of the corresponding test conditions of the input data; Identify the user's verification test intent, and trigger the target logic to process the user's scenario test needs based on the verification test intent.

6. The vehicle-mounted report automated testing method according to claim 5, characterized in that: Before identifying the input data of the user on the test interface, the method includes: A test interface is developed based on a target framework and target components, wherein the test interface supports cascading screening of test scenario parameters.

7. An on-vehicle report automatic test device, characterized in that: include: Acquisition module, used to obtain the user's scenario testing requirements; A generation module, used to generate a corresponding signal message according to the scenario test requirements, and send the signal message to the server through a preset protocol, wherein the server parses the signal message to generate a corresponding interesting report, and pushes the interesting report to the client; An identification module is used to identify the expected fun report corresponding to the scenario test requirement, and control the test system to execute corresponding control instructions according to the comparison result between the fun report and the expected fun report to generate an automated test result.

8. A vehicle, characterized in that: include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the vehicle-mounted report automated testing method as described in any one of claims 1 to 6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: The program is executed by a processor to implement the vehicle-mounted report automatic testing method as described in any one of claims 1-6.

10. A computer program product, characterized in that It includes a computer program, which, when executed by a processor, is used to implement the vehicle-mounted report automatic testing method as described in any one of claims 1-6.

Images