Vehicle testing method and device, electronic equipment and storage medium

Abstract

The invention discloses a vehicle testing method and device, electronic equipment and a storage medium. The method comprises the steps that a testing task for a to-be-tested program of a vehicle is determined; converting the initial test case in the test task to obtain a target test case; in the process of executing the target test case, obtaining a current image generated by the to-be-tested program in response to an operation simulated by the target test case; and testing the to-be-tested program based on the current image and the target image to obtain a test result. The technical problem of low precision of function test of the vehicle is solved.

Description

Technical Field

[0001] This application relates to the field of vehicles, and more specifically, to a vehicle testing method, apparatus, electronic device, and storage medium. Background Technology

[0002] Currently, facing the exponentially increasing complexity of complete vehicles, traditional manual stress testing methods are gradually revealing multi-dimensional efficiency bottlenecks. For example, a complete stress test of a single vehicle model often requires the monthly labor cost of dozens of people, and the coverage of test cases is limited by the scale of manpower, usually only covering 60%-70% of potential working conditions, resulting in low accuracy in vehicle functional testing.

[0003] There is currently no effective solution to the technical problem of low accuracy in the functional testing of the aforementioned vehicles. Summary of the Invention

[0004] This application provides a vehicle testing method, apparatus, electronic device, and storage medium to at least solve the technical problem of low accuracy in vehicle functional testing.

[0005] According to one aspect of the embodiments of this application, a vehicle testing method is provided. The method includes: determining a test task for a program under test (SUPT) of the vehicle, wherein the test task includes: initial test cases for the SUPT; transforming the initial test cases in the test task to obtain target test cases, wherein the target execution parameters for executing the target test cases are different from the initial execution parameters for executing the initial test cases, and the SUPT generates images in response to different operations simulated by different test cases; during the execution of the target test cases, acquiring a current image generated by the SUPT in response to the operations simulated by the target test cases; and testing the SUPT based on the current image and the target image to obtain a test result, wherein the target image represents the operation simulated by the SUPT in response to the target test cases, and the test result represents the relationship between the functions of the SUPT and normal or abnormal functions.

[0006] Furthermore, the initial test cases in the test task are transformed to obtain target test cases, including: adjusting the initial execution parameters to obtain adjusted initial execution parameters; and generating the initial test cases executed under the adjusted initial execution parameters as target test cases.

[0007] Furthermore, based on the current image and the target image, the program under test is tested to obtain test results, including: determining image difference information between the current image and the target image, wherein the image difference information is used to represent the degree of difference between the current image and the target image; determining the relationship between the degree of difference represented by the image difference information and the degree of difference threshold; and testing the program under test based on the relationship to obtain test results.

[0008] Furthermore, based on the relationship, the program under test is tested to obtain test results, including: in response to the relationship that the degree of difference is less than or equal to the degree of difference threshold, the program under test is tested to obtain a first test result, wherein the first test result is used to indicate that the function belongs to normal function; in response to the relationship that the degree of difference is greater than the degree of difference threshold, the program under test is tested to obtain a second test result, wherein the second test result is used to indicate that the function belongs to abnormal function.

[0009] Furthermore, the method also includes: displaying target execution parameters, execution status data of the target test case, and execution progress data of the test case set to which the target test case belongs. The execution status data is used to represent the execution status of the target test case, and the execution progress data is used to represent the historical test cases that have been executed in the test case set, as well as the remaining test cases to be executed in the test case set. The remaining test cases are the test cases in the test case set other than the historical test cases and the target test case.

[0010] Furthermore, the method also includes: storing target test cases; executing the stored target test cases in response to a next test task that is the same as the test task; during the execution of the stored target test cases, obtaining the next current image generated by the next program under test responding to the operation simulated by the target test cases; and testing the next program under test based on the next current image and the target image to obtain the next test result, wherein the next test result is used to represent the relationship between the function of the next program under test and the normal or abnormal function.

[0011] Furthermore, the method also includes: generating test results into report information, wherein the report information is used to indicate the test results; and storing the report information.

[0012] According to another aspect of the embodiments of this application, a vehicle testing apparatus is also provided. The apparatus includes: a determining unit, configured to determine a test task for a program under test (SUPT) of a vehicle, wherein the test task includes: initial test cases for the SUPT; a conversion unit, configured to convert the initial test cases in the test task to obtain target test cases, wherein the target execution parameters for executing the target test cases are different from the initial execution parameters for executing the initial test cases, and the SUPT generates images in response to different operations simulated by different test cases; a first acquisition unit, configured to acquire, during the execution of the target test cases, a current image generated by the SUPT in response to the operations simulated by the target test cases; and a first testing unit, configured to test the SUPT based on the current image and the target image to obtain test results, wherein the target image represents the image to be generated by the SUPT in response to the operations simulated by the target test cases, and the test results represent the relationship between the functions of the SUPT and normal or abnormal functions.

[0013] According to another aspect of the embodiments of this application, a vehicle is also provided, including: a memory storing an executable program; and a processor for running the program, wherein the program executes the methods in various embodiments of this application when it runs.

[0014] According to another aspect of the embodiments of this application, a computer-readable storage medium is also provided, the computer-readable storage medium including a stored executable program, wherein, when the executable program is running, it controls the device where the computer-readable storage medium is located to perform the methods of various embodiments of this application.

[0015] According to another aspect of the embodiments of this application, a computer program product is also provided, including a computer program that, when executed by a processor, implements the methods of various embodiments of this application.

[0016] According to another aspect of the embodiments of this application, a computer program product is also provided, including a non-volatile computer-readable storage medium storing a computer program that, when executed by a processor, implements the methods in various embodiments of this application.

[0017] According to another aspect of the embodiments of this application, a computer program is also provided, which, when executed by a processor, implements the methods of the various embodiments of this application.

[0018] In this embodiment, when testing a vehicle's program under test (DUT), a test task for the DUT is determined; the initial test cases in the test task are transformed to obtain target test cases; during the execution of the target test cases, the current image generated by the DUT is acquired; based on the current image and the target image, the DUT is tested to obtain test results. Because this embodiment transforms the initial test cases in the test task based on the determined test task to obtain target test cases, and then acquires the current image generated by the DUT during the execution of the transformed target test cases, and then compares the differences between the acquired current image and the target image, the DUT can be tested to obtain the relationship between the DUT's functions and normal or abnormal functions. This avoids the test case coverage being limited by manpower, thus solving the technical problem of low accuracy in vehicle functional testing, and ultimately achieving the technical effect of improving the accuracy of vehicle functional testing. Attached Figure Description

[0019] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments of this application and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0020] Figure 1(a) is a schematic diagram of an application scenario of a vehicle testing method according to an embodiment of this application;

[0021] Figure 1(b) is a flowchart of a vehicle testing method according to an embodiment of this application;

[0022] Figure 2 This is a flowchart of an AVM surround view test method based on the HarmonyOS system according to an embodiment of this application;

[0023] Figure 3 This is a schematic diagram of an AVM surround view test platform based on the HarmonyOS system according to an embodiment of this application;

[0024] Figure 4 This is a flowchart of a method for generating test results according to an embodiment of this application;

[0025] Figure 5 This is a structural block diagram of a vehicle testing device according to an embodiment of this application;

[0026] Figure 6 This is a schematic diagram of an electronic device according to an embodiment of this application. Detailed Implementation

[0027] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0028] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application 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 of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover 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.

[0029] According to an embodiment of this application, an embodiment of a vehicle testing method is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0030] As an optional implementation, the vehicle testing method described above can be applied, but is not limited to, the application scenario shown in Figure 1(a). Figure 1(a) is a schematic diagram of an application scenario of a vehicle testing method according to an embodiment of this application. As shown in Figure 1(a), in the application scenario, the terminal device 10 can communicate with the server 13 via the network 11, but is not limited to. The server 13 can perform operations on the database, such as writing or reading data. The terminal device 10 may include, but is not limited to, a human-machine interface screen, a processor, and a memory. The human-machine interface screen can be used, but is not limited to, to display a virtual machine on the mobile terminal 10. The vehicle 12 can be used, but is not limited to, to respond to the human-machine interface operation, execute the corresponding operation, or generate the corresponding instruction and send the generated instruction to the server 13.

[0031] It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here. The vehicle testing method of this application may include: step S102, determining a test task for the program under test (DUT) for the vehicle; step S104, transforming the initial test cases in the test task to obtain target test cases; step S106, acquiring the current image generated by the DUT during the execution of the target test cases; and step S108, testing the DUT based on the current image and the target image to obtain test results.

[0032] It should be noted that all information and data involved in this application (including but not limited to the program under test and target images) are information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of such data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation portals are provided for users to choose to authorize or refuse.

[0033] Figure 1(b) is a flowchart of a vehicle testing method according to an embodiment of this application. As shown in Figure 1(b), the method may include the following steps:

[0034] Step S112: Determine the test tasks for the program under test for the vehicle, wherein the test tasks include: initial test cases for the program under test.

[0035] In the technical solution provided in step S112 of this application, the test task may include: initial test cases for the program under test, the test environment required for testing the program under test, and execution data for the initial test cases. For example, if the program under test is an Around View Monitor (AVM) program, then the test task is an AVM around view test task for the AVM program under test, and the AVM around view test task may include: initial test cases for the AVM program under test, the test environment required for testing the AVM program under test, and execution data for the initial test cases of the AVM program under test. Furthermore, the AVM program may be an application that implements an AVM around view system; this is only an example and not a specific limitation.

[0036] In this embodiment, the test environment required for testing the program under test may include: the hardware environment, software environment, and network environment required for testing the program under test.

[0037] In this embodiment, the execution data of the initial test case may include: initial execution parameters for executing the initial test case, and execution status data of the initial test case. The initial execution parameters may include: the duration and number of iterations required to execute the initial test case, etc., and the execution status data of the initial test case can be used to represent the execution status of the initial test case. For example, the duration required to execute the initial test case may also be simply referred to as, but is not limited to, execution time.

[0038] In this embodiment, a test task for the program under test (DUT) for a vehicle is determined. Optionally, this embodiment selects the DUT from a plurality of candidate programs, wherein the candidate programs other than the DUT are candidate programs that have completed testing, and the DUT is a candidate program that has not completed testing. After selecting the DUT, a test task for the functionality of the DUT is constructed, thereby achieving the goal of determining the test task for the DUT for the vehicle.

[0039] Optionally, initial test cases matching the functionality of the program under test are selected from the test case list. Then, the execution data for these initial test cases is initialized. Simultaneously, the actual operating environment of the program under test is copied or simulated to obtain the necessary testing environment. Afterward, the initial test cases, the testing environment, and the execution data are imported into a test task generation template to generate a test task for the vehicle-specific program under test. This achieves the goal of determining the test task for the vehicle-specific program under test.

[0040] Step S114: Transform the initial test cases in the test task to obtain target test cases. The target execution parameters used to execute the target test cases are different from the initial execution parameters used to execute the initial test cases. The program under test generates images in response to different operations simulated by different test cases.

[0041] In the technical solution provided in step S114 of this application, the target execution parameters used to execute the target test case are different from the initial execution parameters used to execute the initial test case. The initial execution parameters may include the time and number of loops required to execute the initial test case, while the target execution parameters may include the time and number of loops required to execute the target test case.

[0042] In this embodiment, the program under test (DUT) can generate images in response to different operations simulated by different test cases. These different operations simulated by different test cases may include display operations, switching operations, and masking operations. For example, if the DUT is an AVM program under test, it can generate a first image in response to a display operation simulated by a test case; or it can generate a second image in response to a switching operation simulated by a test case; or it can generate a third image in response to a masking operation simulated by a test case. These are merely illustrative examples and not intended to be specific limitations.

[0043] In this embodiment, after determining the test task for the vehicle's program under test, the initial test cases in the test task are transformed to obtain target test cases. Optionally, based on the determined test task, this embodiment transforms the execution order of multiple sub-initial test cases in the initial test cases, arranges the multiple sub-initial test cases according to the transformed execution order, and uses the arranged multiple sub-initial test cases as target test cases, thereby achieving the purpose of transforming the initial test cases.

[0044] Optionally, based on the determined test task, the number of iterations for multiple sub-initial test cases can be adjusted, and the adjusted multiple sub-initial test cases can be used as target test cases, thereby achieving the purpose of transforming the initial test cases.

[0045] Optionally, based on the determined test task, this embodiment transforms the execution order of multiple sub-initial test cases in the initial test case, arranges multiple sub-initial test cases according to the transformed execution order, adjusts the loop count of the arranged multiple sub-initial test cases, and uses the adjusted and arranged multiple sub-initial test cases as the target test cases, thereby achieving the purpose of transforming the initial test cases.

[0046] Step S116: During the execution of the target test case, obtain the current image generated by the operation simulated by the program under test in response to the target test case.

[0047] In the technical solution provided in step S116 of this application, the format of the current image is an image output format allowed by the program under test. For example, the current image can also be called a current picture.

[0048] In this embodiment, after transforming the initial test cases in the test task to obtain target test cases, during the execution of the target test cases, the current image generated by the program under test responding to the operations simulated by the target test cases is obtained. Optionally, in this embodiment, after obtaining the target test cases, the target test cases are executed, and during the execution of the target test cases, if the program under test has generated a current image in response to the operations simulated by the target test cases, the current image can be obtained from the program under test, thereby achieving the purpose of obtaining the current image during the execution of the target test cases.

[0049] It should be noted that the method described above for obtaining the current image generated by the program under test in response to the simulated operation of the target test case during the execution of the target test case is merely illustrative and is not specifically limited here. Any method that can obtain the current image generated by the program under test during the execution of the target test case is within the protection scope of the embodiments of this application, and will not be described in detail here.

[0050] Step S118: Based on the current image and the target image, test the program under test and obtain the test results. The target image is used to represent the operation simulated by the program under test in response to the target test case, while the image to be generated and the test results are used to represent the relationship between the function of the program under test and the normal or abnormal function.

[0051] In the technical solution provided in step S118 of this application, the target image can be used to represent an image to be generated by the program under test responding to the operation simulated by the target test case. For example, the target image can be a standard image preset for the program under test.

[0052] In this embodiment, the test results can be used to represent the relationship between the function of the program under test and normal or abnormal functions.

[0053] In this embodiment, during the execution of the target test case, after acquiring the current image generated by the operation simulated by the program under test in response to the target test case, the program under test is tested based on the current image and the target image to obtain the test results. Optionally, this embodiment compares the acquired current image with the target image based on the acquired current image to obtain image difference information between the current image and the target image. Based on the above image difference information, the program under test is tested to obtain the test results. That is, the relationship between the function of the program under test and the normal or abnormal function can be obtained, thereby achieving the goal of avoiding the test case coverage being limited by the scale of manpower.

[0054] In steps S112 to S118 of this application, when testing the program under test (DUT) of a vehicle, a test task for the DUT is determined; the initial test cases in the test task are transformed to obtain target test cases; during the execution of the target test cases, the current image generated by the DUT is acquired; based on the current image and the target image, the DUT is tested to obtain test results. Since this embodiment of the application, based on the determined test task, transforms the initial test cases in the aforementioned test task to obtain target test cases, and then during the execution of the transformed target test cases, the current image generated by the DUT can be acquired. Then, by comparing the image differences between the acquired current image and the target image, the DUT can be tested to obtain the relationship between the DUT's functions and normal or abnormal functions. This achieves the goal of avoiding the test case coverage being limited by manpower, thereby solving the technical problem of low accuracy in vehicle functional testing, and ultimately achieving the technical effect of improving the accuracy of vehicle functional testing.

[0055] The following section further describes the steps of converting the initial test cases in the test task to obtain the target test cases in this embodiment.

[0056] As an optional embodiment, step S114 involves transforming the initial test cases in the test task to obtain target test cases, including: adjusting the initial execution parameters to obtain adjusted initial execution parameters; and generating the initial test cases executed under the adjusted initial execution parameters as target test cases.

[0057] In this embodiment, the initial execution parameters may include: the duration and number of loops required to execute the initial test case, etc.

[0058] In this embodiment, after determining the test task for the vehicle-specific program under test, the initial execution parameters are adjusted to obtain the adjusted initial execution parameters. Optionally, based on the determined test task, this embodiment adjusts the duration required to execute the initial test cases to obtain the adjusted duration, and adjusts the number of loops required to execute the initial test cases to obtain the adjusted number of loops, thereby achieving the goal of obtaining the adjusted initial execution parameters.

[0059] In this embodiment, after adjusting the initial execution parameters to obtain the adjusted initial execution parameters, the initial test cases executed under the adjusted initial execution parameters are generated as target test cases. Optionally, based on the adjusted initial execution parameters, this embodiment encapsulates the initial test cases executed under the adjusted initial execution parameters to obtain target test cases. This achieves the purpose of converting the initial test cases, thereby realizing the technical effect of improving the accuracy of the target test cases.

[0060] The following section further explains the steps of testing the program under test based on the current image and the target image to obtain test results in this embodiment.

[0061] As an optional embodiment, step S118, based on the current image and the target image, tests the program under test to obtain test results, including: determining image difference information between the current image and the target image, wherein the image difference information is used to represent the degree of difference between the current image and the target image; determining the relationship between the degree of difference represented by the image difference information and the degree of difference threshold; and testing the program under test based on the relationship to obtain test results.

[0062] In this embodiment, the image difference information described above can be used to represent the degree of difference between the current image and the target image. For example, the image difference information can be used to represent the degree of difference between the current image and a preset standard image.

[0063] In this embodiment, during the execution of the target test case, after acquiring the current image generated by the operation simulated by the program under test in response to the target test case, the image difference information between the current image and the target image is determined. Optionally, this embodiment can obtain the image difference information between the current image and the target image by comparing the acquired current image with the target image based on the acquired current image. Alternatively, the acquired current image and target image can be input into an image difference recognition model for difference recognition to obtain image difference information. The image difference recognition model can be constructed based on variational autoencoders and generative adversarial networks.

[0064] In this embodiment, after determining the image difference information between the current image and the target image, the relationship between the degree of difference represented by the image difference information and a difference degree threshold is determined. Based on this relationship, the program under test is tested to obtain test results. Optionally, this embodiment determines the degree of difference represented by the image difference information based on the determined image difference information, and then compares the aforementioned degree of difference with the difference degree threshold to obtain the relationship between the degree of difference and the difference degree threshold. Then, based on this relationship, the program under test is tested to obtain test results. That is, the relationship between the function of the program under test and its normal or abnormal functions can be obtained. This achieves the goal of avoiding the limitation of test case coverage on manpower scale, thereby realizing the technical effect of improving the accuracy of vehicle functional testing.

[0065] The following section further explains the steps of testing the program under test based on the relationship described in this embodiment to obtain test results.

[0066] As an optional implementation, the program under test is tested based on a relationship to obtain test results, including: in response to a relationship where the degree of difference is less than or equal to a degree of difference threshold, the program under test is tested to obtain a first test result, wherein the first test result is used to indicate that the function is a normal function; in response to a relationship where the degree of difference is greater than the degree of difference threshold, the program under test is tested to obtain a second test result, wherein the second test result is used to indicate that the function is an abnormal function.

[0067] In this embodiment, the test result can be either a first test result or a second test result. The first test result can be used to indicate that the function is a normal function, while the second test result can be used to indicate that the function is an abnormal function.

[0068] In this embodiment, after determining the relationship between the degree of difference represented by the image difference information and the difference degree threshold, in response to the relationship that the degree of difference is less than or equal to the difference degree threshold, the program under test is tested to obtain a first test result. Optionally, if the determined relationship is that the degree of difference is less than or equal to the difference degree threshold, then testing the program under test can obtain a first test result, that is, it can be concluded that the function of the program under test is normal. This achieves the goal of avoiding the limitation of test case coverage by manpower scale, thereby realizing the technical effect of improving the accuracy of vehicle functional testing.

[0069] In this embodiment, after determining the relationship between the degree of difference represented by the image difference information and the difference degree threshold, in response to the relationship that the degree of difference is greater than the difference degree threshold, the program under test is tested to obtain a second test result. Optionally, if the determined relationship is that the degree of difference is greater than the difference degree threshold, then testing the program under test can obtain a second test result, that is, it can be determined that the function of the program under test belongs to an abnormal function. This achieves the goal of avoiding the coverage of test cases being limited by the scale of manpower, thereby realizing the technical effect of improving the accuracy of vehicle functional testing.

[0070] The testing method for the vehicle described in this embodiment will be further explained below.

[0071] As an optional embodiment, the method further includes: displaying target execution parameters, execution status data of the target test case, and execution progress data of the test case set to which the target test case belongs, wherein the execution status data is used to represent the execution status of the target test case, the execution progress data is used to represent the historical test cases that have been executed in the test case set, and the remaining test cases to be executed in the test case set, wherein the remaining test cases are the test cases in the test case set other than the historical test cases and the target test case.

[0072] In this embodiment, the execution status data can be used to represent the execution status of the target test case. The execution status can be any of the following: running, passed, failed, or terminated.

[0073] In this embodiment, the execution progress data can be used to represent the historical test cases that have been executed in the test case set, and the remaining test cases to be executed in the test case set. For example, the execution progress data can be represented by a first total number of historical test cases that have been executed and a second total number of remaining test cases to be executed, or the execution progress data can be represented by the proportion of the first total number to the total number of test cases in the test case set, and the proportion of the second total number to the total number of test cases in the test case set.

[0074] In this embodiment, the remaining test cases are the test cases in the test case set excluding historical test cases and target test cases.

[0075] In this embodiment, the target execution parameters, the execution status data of the target test case, and the execution progress data of the test case set to which the target test case belongs are displayed. Optionally, this embodiment displays the target execution parameters, the execution status data of the target test case, and the execution progress data of the test case set to which the target test case belongs in real time on the main interface of the test task, thereby achieving the purpose of indicating the progress of the test process of the program under test.

[0076] The testing method for the vehicle described in this embodiment will be further explained below.

[0077] As an optional embodiment, the method further includes: storing target test cases; executing the stored target test cases in response to a next test task that is the same as the test task; during the execution of the stored target test cases, obtaining a next current image generated by the next program under test responding to the operation simulated by the target test cases; and testing the next program under test based on the next current image and the target image to obtain a next test result, wherein the next test result is used to represent the relationship between the function of the next program under test and normal or abnormal functions.

[0078] In this embodiment, the above-mentioned next test result can be used to represent the relationship between the function of the next program under test and the normal or abnormal function.

[0079] In this embodiment, after storing the target test case, in response to the next test task which is the same as the test task, the stored target test case is executed. During the execution of the stored target test case, the next current image generated by the operation simulated by the next program under test in response to the target test case is obtained, and the next program under test is tested based on the next current image and the target image to obtain the next test result.

[0080] Optionally, this embodiment compares the next test task with the test task. If the next test task is found to be the same as the test task, the stored target test case is executed. During the execution of the stored target test case, if the next program under test has generated a next current image in response to the operation simulated by the target test case, the next current image is obtained from the next program under test. The difference between the next current image and the target image is compared to obtain the next image difference information between the next current image and the target image. Based on the next image difference information, the next program under test is tested to obtain the next test result. That is, the relationship between the function of the next program under test and the normal or abnormal function can be obtained. This achieves the goal of avoiding the test case coverage being limited by the manpower scale, and thus realizes the technical effect of improving the accuracy of vehicle functional testing.

[0081] Optionally, the aforementioned next image difference information can be used to represent the degree of difference between the next current image and the target image.

[0082] Optionally, the relationship between the degree of difference represented by the next image difference information and a difference degree threshold is determined. If the relationship is that the degree of difference represented by the next image difference information is less than or equal to the difference degree threshold, then the next program to be tested is tested, and the next test result is that the function of the next program to be tested is a normal function. If the relationship is that the degree of difference represented by the next image difference information is greater than the difference degree threshold, then the next program to be tested is tested, and the next test result is that the function of the next program to be tested is an abnormal function.

[0083] The testing method for the vehicle described in this embodiment will be further explained below.

[0084] As an optional embodiment, the method further includes: generating test results into report information, wherein the report information is used to indicate the test results; and storing the report information.

[0085] In this embodiment, the aforementioned report information can be used to indicate test results. For example, the report information can be a report specific to a test task.

[0086] In this embodiment, after generating the test results into report information, the report information is stored. Optionally, based on the obtained test results, this embodiment generates report information according to a report template, and stores the generated report information in a local database or on a cloud server.

[0087] In this embodiment, when testing a vehicle's program under test (DUT), a test task for the DUT is determined; the initial test cases in the test task are transformed to obtain target test cases; during the execution of the target test cases, the current image generated by the DUT is acquired; based on the current image and the target image, the DUT is tested to obtain test results. Because this embodiment transforms the initial test cases in the test task based on the determined test task to obtain target test cases, and then acquires the current image generated by the DUT during the execution of the transformed target test cases, and then compares the differences between the acquired current image and the target image, the DUT can be tested to obtain the relationship between the DUT's functions and normal or abnormal functions. This avoids the test case coverage being limited by manpower, thus solving the technical problem of low accuracy in vehicle functional testing, and ultimately achieving the technical effect of improving the accuracy of vehicle functional testing.

[0088] The technical solutions of the embodiments of this application will be illustrated below with reference to preferred embodiments.

[0089] Currently, facing the exponentially increasing complexity of complete vehicles, traditional manual stress testing methods are gradually revealing multi-dimensional efficiency bottlenecks. For example, a complete stress test of a single vehicle model often requires the monthly labor cost of dozens of people, and the coverage of test cases is limited by the scale of manpower, usually only covering 60%-70% of potential working conditions, resulting in low accuracy in vehicle functional testing.

[0090] However, this application proposes a vehicle testing method. Based on the determined test task, the initial test cases in the test task are transformed to obtain target test cases. Then, during the execution of the transformed target test cases, the current image generated by the program under test can be obtained. By comparing the image difference between the obtained current image and the target image, the program under test can be tested to obtain the relationship between the function of the program under test and the normal or abnormal function. This achieves the goal of avoiding the test case coverage being limited by manpower, thereby solving the technical problem of low accuracy in vehicle functional testing and thus achieving the technical effect of improving the accuracy of vehicle functional testing.

[0091] In this embodiment, the AVM can be tested by executing the AVM testing method based on the HarmonyOS system. For example, Figure 2 This is a flowchart of a HarmonyOS-based AVM surround view testing method according to an embodiment of this application, as shown below. Figure 2 As shown, the method may include the following steps:

[0092] Step S201: Access the tool page through a browser.

[0093] After accessing the tool page through a browser, proceed to step S202 and select the test scenario.

[0094] After selecting the test scenario, proceed to step S203 to create a test task.

[0095] After creating the test task, proceed to step S204 to select the vehicle and test cases.

[0096] After selecting the vehicle and test cases, proceed to step S205 to configure the task parameters.

[0097] In the technical solution provided in step S205 of this application, the test cases within the task are configured in a targeted manner, for example, the execution time and loop count of the test cases are dynamically adjusted.

[0098] After configuring the task parameters, proceed to step S206 to start the task.

[0099] After starting the task, proceed to step S207 to execute the task.

[0100] In the technical solution provided in step S207 of this application, test cases are selected from the test case list, and parameters are configured as needed, including setting the number of times the test cases are executed in a loop and the execution interval for a single test case. After completing the configuration, clicking "Save Task" will automatically save the current configuration parameters. If the same test task needs to be executed repeatedly later, there is no need to reconfigure; simply clicking "Copy Task" will quickly generate a new test task with identical parameters.

[0101] After the task is executed, step S208 is executed to generate historical tasks.

[0102] After generating historical tasks, step S209 is executed to display the historical task data.

[0103] When the task is started, step S210 can also be executed to display real-time task data.

[0104] In this embodiment, after the task configuration is completed and confirmed to be correct, the system immediately triggers the test process in response to the "Execute Task" button being clicked: a bridge connection is established between the test computer (Personal Computer) and the vehicle's infotainment system. Touch commands are simulated based on the Android Debug Bridge (ADB) / Harmony Debug Connector (HDC) protocol to accurately locate the coordinates of interface elements and execute click, swipe, and other operations. During this process, the platform obtains test case execution logs in real time through a WebSocket long connection, allowing testers to view real-time running data on the log monitoring interface at any time. Simultaneously, the main test task interface displays key information, including the total number of executed test cases / total number of test cases to be executed, a percentage progress bar, cumulative execution time, and the real-time status of each test case (running / passed / failed / terminated), forming a multi-dimensional visual monitoring system.

[0105] In this embodiment, the HarmonyOS-based AVM lookaround test platform can be used to execute the HarmonyOS-based AVM lookaround test method. For example, Figure 3 This is a schematic diagram of an AVM surround view test platform based on the HarmonyOS system according to an embodiment of this application, as shown below. Figure 3As shown, the platform 300 may include: a front-end system 301, a back-end service layer 302, and an infrastructure layer 303. The front-end system 301 may include: a reverse proxy server 3011 and a log display module 3012; the back-end service layer 302 may include: an interface service module 3021 and a communication module 3022; the infrastructure layer 303 may include: a tool 3031 and a local disk database 3032; the tool 3031 may include: a local tool 30311 and a vehicle-mounted system 30312.

[0106] In this embodiment, the aforementioned reverse proxy server (Nginx server) 3011 can be used to deploy static resources and optimize their loading speed. The reverse proxy server 3011 can also be used for load balancing; for example, in high-concurrency scenarios, it can distribute requests to multiple backend services using algorithms, avoiding single-server overload and improving system stability. Furthermore, the reverse proxy server 3011 can be used to encrypt transmitted data to prevent theft or tampering, ensuring the security of user information and test data.

[0107] In this embodiment, the log display module 3012 can be used to display test logs obtained from the communication module 3022.

[0108] In this embodiment, the interface service module 3021 can be used to obtain front-end static resources from the reverse proxy server 3011.

[0109] In this embodiment, the communication module 3022 can be used to transmit test logs to the log display module 3012. Specifically, the communication module 3022 can transmit the test logs via the WebSocket protocol.

[0110] In this embodiment, the vehicle-mounted system 30312 can be used to generate result reports and log information, the local tool 30311 can be used to obtain result reports and log information from the vehicle-mounted system 30312, and the local tool 30311 can be used to test AVM using front-end static resources.

[0111] In this embodiment, the local disk database 3032 can be used to store test logs and reports. In the local disk database 3032, data exists as a single file, facilitating management and migration, and offering strong cross-platform compatibility. It also supports a simple Application Programming Interface (API) and employs efficient data structures such as B-trees / B+ trees, exhibiting excellent performance in small to medium-sized datasets and meeting the system's efficient storage and query requirements.

[0112] In this embodiment, by executing the test result generation method, it can be determined whether the AVM's function is a normal function or an abnormal function. For example, Figure 4 This is a flowchart of a method for generating test results according to an embodiment of this application, such as... Figure 4 As shown, the method may include the following steps:

[0113] Step S401: Click to execute the task.

[0114] After clicking "Execute Task", step S402 is executed to determine whether the prerequisites for executing the task are met.

[0115] In the technical solution provided by step S402 of this application, the test cases and preconditions are shown in Table 1 below.

[0116] Table 1 Test Cases and Preconditions

[0117]

[0118] It's important to note that preconditions are the necessary foundation for test case execution, derived from system functional logic analysis. Taking the in-vehicle intervention operation - parameter [Open AVM] test case as an example, if the intelligent driving function is not functioning properly, the control logic and data channels related to screen switching in the system will be inactive. In this case, screen switching will not only lack effective response but may also trigger system anomalies. Therefore, strictly adhering to preconditions is crucial to ensuring that test cases accurately verify system functionality. Combining real-time image comparison with automated scripts allows for a comprehensive evaluation of the system's performance and functionality under stress testing, ensuring system stability and reliability.

[0119] If it is determined that the preconditions for executing the task are met, then step S403 is executed to execute this test case.

[0120] In the technical solution provided in step S403 of this application, the test cases are executed according to Table 2 below.

[0121] If it is determined that the preconditions for executing the task are not met, the execution flow of the test result generation method ends.

[0122] After executing this test case, step S404 is executed to determine whether the generated current image is the same as the preset image.

[0123] In the technical solution provided in step S404 of this application, during task execution, the platform constructs a complete verification system through automated stress testing scripts to rigorously test system functions. Specifically, the script acquires images generated during the test in real time and compares them precisely with preset standard images. It analyzes the differences between the two images pixel by pixel to determine whether the currently displayed content meets expectations. If the comparison passes, it indicates that the system is currently running normally, and the script automatically executes the next operation; if the comparison fails, the system immediately triggers exception handling, recording detailed failure information in the log, providing a basis for subsequent problem investigation and system optimization.

[0124] If it is determined that the current image is the same as the preset image, then step S405 is executed to test the AVM. The test result shows that the AVM function is normal.

[0125] Table 2 Test Case Execution Table

[0126]

[0127] If it is determined that the current image is different from the preset image, then step S406 is executed, and the vehicle system automatically clicks the screen to perform AVM-related operations.

[0128] After the vehicle's infotainment system automatically taps the screen to perform AVM-related operations, it returns to step S403.

[0129] In this embodiment, when testing a vehicle's program under test (DUT), a test task for the DUT is determined; the initial test cases in the test task are transformed to obtain target test cases; during the execution of the target test cases, the current image generated by the DUT is acquired; based on the current image and the target image, the DUT is tested to obtain test results. Because this embodiment transforms the initial test cases in the test task based on the determined test task to obtain target test cases, and then acquires the current image generated by the DUT during the execution of the transformed target test cases, and then compares the image differences between the acquired current image and the target image, the DUT can be tested to obtain the relationship between the DUT's functions and normal or abnormal functions. This achieves the goal of avoiding the test case coverage being limited by manpower, thus solving the technical problem of low accuracy in vehicle functional testing, and ultimately achieving the technical effect of improving the accuracy of vehicle functional testing.

[0130] According to another aspect of the embodiments of this application, corresponding to the embodiments of the above-described vehicle testing method, the embodiments of this application also provide a vehicle testing device. Figure 5 This is a structural block diagram of a vehicle testing device according to an embodiment of this application, such as... Figure 5 As shown, the vehicle testing device 500 may include: a determining unit 502, a conversion unit 504, a first acquisition unit 506, and a first testing unit 508.

[0131] The determining unit 502 is used to determine the test tasks for the program under test for the vehicle, wherein the test tasks include: initial test cases for the program under test.

[0132] The conversion unit 504 is used to convert the initial test cases in the test task to obtain target test cases. The target execution parameters used to execute the target test cases are different from the initial execution parameters used to execute the initial test cases. The program under test generates images in response to different operations simulated by different test cases.

[0133] The first acquisition unit 506 is used to acquire the current image generated by the operation simulated by the program under test in response to the target test case during the execution of the target test case.

[0134] The first test unit 508 is used to test the program under test based on the current image and the target image, and obtain test results. The target image is used to represent the operation simulated by the program under test in response to the target test case, while the image to be generated and the test results are used to represent the relationship between the function of the program under test and the normal or abnormal function.

[0135] Optionally, the conversion unit 504 may include: an adjustment module for adjusting the initial execution parameters to obtain the adjusted initial execution parameters; and a generation module for generating the initial test cases executed under the adjusted initial execution parameters into target test cases.

[0136] Optionally, the first test unit 508 may include: a first determining module, used to determine image difference information between the current image and the target image, wherein the image difference information is used to represent the degree of difference between the current image and the target image; a second determining module, used to determine the relationship between the degree of difference represented by the image difference information and the degree of difference threshold; and a test module, used to test the program under test based on the relationship and obtain test results.

[0137] Optionally, the testing module may include: a first testing submodule, used to test the program under test in response to a relationship where the degree of difference is less than or equal to a degree of difference threshold, and obtain a first test result, wherein the first test result is used to indicate that the function is a normal function; and a second testing submodule, used to test the program under test in response to a relationship where the degree of difference is greater than a degree of difference threshold, and obtain a second test result, wherein the second test result is used to indicate that the function is an abnormal function.

[0138] Optionally, the vehicle testing device 500 may further include: a display unit for displaying target execution parameters, execution status data of the target test case, and execution progress data of the test case set to which the target test case belongs. The execution status data is used to represent the execution status of the target test case, and the execution progress data is used to represent the historical test cases that have been executed in the test case set, as well as the remaining test cases to be executed in the test case set. The remaining test cases are the test cases in the test case set other than the historical test cases and the target test case.

[0139] Optionally, the vehicle testing device 500 may further include: a first storage unit for storing target test cases; an execution unit for executing the stored target test cases in response to a next test task that is the same as the test task; a second acquisition unit for acquiring, during the execution of the stored target test cases, a next current image generated by the next program under test responding to the operation simulated by the target test cases; and a second testing unit for testing the next program under test based on the next current image and the target image to obtain a next test result, wherein the next test result is used to represent the relationship between the function of the next program under test and its normal or abnormal function.

[0140] Optionally, the vehicle testing device 500 may further include: a generation unit for generating test results into report information, wherein the report information is used to indicate the test results; and a second storage unit for storing the report information.

[0141] In this embodiment, the vehicle testing device includes the following units: a determining unit, used to determine a test task for the program under test (DUT) of the vehicle, wherein the test task includes: initial test cases for the DUT; a conversion unit, used to convert the initial test cases in the test task to obtain target test cases, wherein the target execution parameters for executing the target test cases are different from the initial execution parameters for executing the initial test cases, and the DUT generates images in response to different operations simulated by different test cases; a first acquisition unit, used to acquire the current image generated by the DUT in response to the operations simulated by the target test cases during the execution of the target test cases; and a first testing unit, used to test the DUT based on the current image and the target image to obtain test results, wherein the target image represents the operation simulated by the DUT in response to the target test cases, and the test results represent the relationship between the function of the DUT and normal or abnormal functions. This achieves the goal of avoiding the test case coverage being limited by manpower, thereby solving the technical problem of low accuracy in vehicle functional testing and thus achieving the technical effect of improving the accuracy of vehicle functional testing.

[0142] Embodiments of this application also provide a vehicle, including: a memory storing an executable program; and a processor for running the program, wherein the program executes the methods described in various embodiments of this application when it runs.

[0143] Embodiments of this application also provide a computer-readable storage medium including a stored executable program, wherein, when the executable program is running, it controls the device where the computer-readable storage medium is located to perform the methods of various embodiments of this application.

[0144] Embodiments of this application also provide a computer program product, including a computer program that, when executed by a processor, implements the methods of various embodiments of this application.

[0145] Embodiments of this application also provide a computer program product, including a non-volatile computer-readable storage medium for storing a computer program that, when executed by a processor, implements the methods in various embodiments of this application.

[0146] Embodiments of this application also provide a computer program that, when executed by a processor, implements the methods described in the various embodiments of this application.

[0147] In the above embodiments of this application, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0148] According to an embodiment of this application, an electronic device is also provided. Figure 6 This is a schematic diagram of an electronic device according to an embodiment of this application, such as... Figure 6 As shown, the electronic device 600 may include a memory 610 and a processor 620, wherein the memory 610 is used to store an executable program; the processor 620 is used to run the program stored in the memory 610, and the program executes the vehicle testing method of this application when it runs.

[0149] In this application, "multiple" refers to two or more.

[0150] In this application, unless otherwise expressly defined, the terms "installation," "connection," and "linking" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal connection between two components. Those skilled in the art can understand the specific meaning of the above terms in this application based on the specific circumstances.

[0151] The terms “first,” “second,” “third,” “fourth,” etc., in this application (if present) are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0152] In this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, in this application, the character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0153] According to another aspect of the embodiments of this application, a computer-readable storage medium is also provided. The computer-readable storage medium includes a stored program, wherein, when the program is executed, it controls the device where the computer-readable storage medium is located to perform the vehicle testing method of the embodiments.

[0154] Computer-readable storage media, also known as computer storage media, may include data signals propagated in baseband or as part of a carrier wave, carrying readable program code. These propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable storage media can transmit, propagate, or transfer programs for use by or in conjunction with an instruction execution system, apparatus, or device.

[0155] The program code contained in a computer-readable storage medium may be transmitted using any suitable medium, including but not limited to wireless, wired, optical fiber, radio frequency, or any suitable combination thereof.

[0156] Optionally, when the above-mentioned computer program is executed by a processor, the program code implements the following steps: determining a test task for the program under test (SUTT) for a vehicle, wherein the test task includes: initial test cases for the SUTT; transforming the initial test cases in the test task to obtain target test cases, wherein the target execution parameters used to execute the target test cases are different from the initial execution parameters used to execute the initial test cases, and the SUTT generates images in response to different operations simulated by different test cases; during the execution of the target test cases, acquiring the current image generated by the SUTT in response to the operations simulated by the target test cases; testing the SUTT based on the current image and the target image to obtain test results, wherein the target image represents the operation simulated by the SUTT in response to the target test cases, and the test results represent the relationship between the functions of the SUTT and normal or abnormal functions.

[0157] Optionally, when the above computer program is executed by the processor, the program code implements the following steps: adjusting the initial execution parameters to obtain the adjusted initial execution parameters; generating the initial test cases to be executed under the adjusted initial execution parameters as target test cases.

[0158] Optionally, when the above computer program is executed by the processor, the program code implements the following steps: determining image difference information between the current image and the target image, wherein the image difference information is used to represent the degree of difference between the current image and the target image; determining the relationship between the degree of difference represented by the image difference information and the degree of difference threshold; and testing the program to be tested based on the relationship to obtain the test results.

[0159] Optionally, when the above computer program is executed by the processor, the program code implements the following steps: in response to the relation that the degree of difference is less than or equal to the degree of difference threshold, the program to be tested is tested to obtain a first test result, wherein the first test result is used to indicate that the function belongs to normal function; in response to the relation that the degree of difference is greater than the degree of difference threshold, the program to be tested is tested to obtain a second test result, wherein the second test result is used to indicate that the function belongs to abnormal function.

[0160] Optionally, when the above computer program is executed by the processor, the program code implements the following steps: displaying the target execution parameters, the execution status data of the target test case, and the execution progress data of the test case set in which the target test case is located, wherein the execution status data is used to represent the execution status of the target test case, the execution progress data is used to represent the historical test cases that have been executed in the test case set, and the remaining test cases to be executed in the test case set, wherein the remaining test cases are the test cases in the test case set other than the historical test cases and the target test case.

[0161] Optionally, when the above-mentioned computer program is executed by the processor, the program code implements the following steps: storing target test cases; in response to the next test task being the same as the test task, executing the stored target test cases; during the execution of the stored target test cases, obtaining the next current image generated by the operation simulated by the next program under test in response to the target test cases; based on the next current image and the target image, testing the next program under test to obtain the next test result, wherein the next test result is used to represent the relationship between the function of the next program under test and the normal or abnormal function.

[0162] Optionally, when the above computer program is executed by the processor, the program code implements the following steps: generating test results into report information, wherein the report information is used to prompt the test results; and storing the report information.

[0163] In the embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For instance, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling, direct coupling, or communication connection may be through some interfaces; the indirect coupling or communication connection between units or modules may be electrical or other forms.

[0164] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0165] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0166] 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 this application, 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 described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0167] The above description is only a preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A method for testing a vehicle, characterized in that, include: Determine the test tasks for the program under test for the vehicle, wherein the test tasks include: initial test cases for the program under test; The initial test cases in the test task are transformed to obtain target test cases, wherein the target execution parameters for executing the target test cases are different from the initial execution parameters for executing the initial test cases, and the program under test generates images in response to different operations simulated by different test cases; During the execution of the target test case, the current image generated by the operation simulated by the program under test in response to the target test case is obtained; Based on the current image and the target image, the program under test is tested to obtain test results. The target image is used to represent the image to be generated by the program under test responding to the operation simulated by the target test case. The test results are used to represent the relationship between the function of the program under test and normal or abnormal functions.

2. The method according to claim 1, characterized in that, The initial test cases in the test task are transformed to obtain target test cases, including: The initial execution parameters are adjusted to obtain the adjusted initial execution parameters; The initial test cases executed under the adjusted initial execution parameters will be used to generate the target test cases.

3. The method according to claim 1, characterized in that, Based on the current image and the target image, the program under test is tested to obtain test results, including: Determine image difference information between the current image and the target image, wherein the image difference information is used to represent the degree of difference between the current image and the target image; Determine the relationship between the degree of difference represented by the image difference information and the degree of difference threshold; Based on the aforementioned relationship, the program under test is tested, and the test results are obtained.

4. The method according to claim 3, characterized in that, Based on the aforementioned relationship, the program under test is tested to obtain the test results, including: In response to the relationship being such that the degree of difference is less than or equal to the degree of difference threshold, the program under test is tested to obtain a first test result, wherein the first test result is used to indicate that the function belongs to the normal function; In response to the relationship being greater than the difference threshold, the program under test is tested to obtain a second test result, wherein the second test result is used to indicate that the function belongs to the abnormal function.

5. The method according to claim 1, characterized in that, The method further includes: The display shows the target execution parameters, the execution status data of the target test case, and the execution progress data of the test case set to which the target test case belongs. The execution status data is used to represent the execution status of the target test case, and the execution progress data is used to represent the historical test cases that have been executed in the test case set, as well as the remaining test cases to be executed in the test case set. The remaining test cases are the test cases in the test case set other than the historical test cases and the target test case.

6. The method according to claim 1, characterized in that, The method further includes: Store the target test cases; In response to the next test task being the same as the test task, the stored target test cases are executed; During the execution of the stored target test case, the next current image generated by the next operation of the test program in response to the target test case is obtained; Based on the next current image and the target image, the next program to be tested is tested to obtain the next test result, wherein the next test result is used to represent the relationship between the function of the next program to be tested and the normal function or the abnormal function.

7. The method according to any one of claims 1 to 6, characterized in that, The method further includes: The test results are generated into a report, which is used to display the test results. Store the report information.

8. A vehicle testing device, characterized in that, include: A determining unit is configured to determine a test task for the program under test for the vehicle, wherein the test task includes: initial test cases for the program under test; A conversion unit is used to convert the initial test cases in the test task to obtain target test cases, wherein the target execution parameters for executing the target test cases are different from the initial execution parameters for executing the initial test cases, and the program under test is used to generate images in response to different operations simulated by different test cases; The first acquisition unit is used to acquire, during the execution of the target test case, the current image generated by the operation simulated by the program under test in response to the target test case; The first testing unit is used to test the program under test based on the current image and the target image, and obtain test results. The target image is used to represent the image to be generated by the program under test in response to the operation simulated by the target test case. The test results are used to represent the relationship between the function of the program under test and the normal or abnormal function.

9. An electronic device, characterized in that, include: Memory, which stores executable programs; A processor for running the program, wherein the program, when running, performs the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored executable program, wherein, when the executable program is executed, it controls the device on which the storage medium is located to perform the method according to any one of claims 1 to 7.

Images