Test case generation method and device based on scenario data back annotation

Abstract

The application relates to the technical field of automatic driving vehicle testing, in particular to a test case generation method and device based on scene data back annotation, wherein the method comprises the following steps: determining a software interface to be detected in a test case of a measured scene, extracting expected values of measured scene information and an automatic driving controller output interface, finding and recording start and end time points of the measured scene on a time axis in driving record video data in a standard data packet, calculating a relative position of a detection time point relative to a data start time, determining all output values and / or change rules of the software interface to be detected at the start and end time points, and writing at least one test case according to the expected values. The embodiment of the application can generate an automatic driving test case based on scene data back annotation, the generated test case has wide coverage and strong pertinence, the writing efficiency and the standardization degree of the automatic driving test case generation process are improved, and the application is more reliable and practical.

Description

Technical Field

[0001] This application relates to the field of autonomous vehicle testing technology, and in particular to a test case generation method and apparatus based on scene data back-injection. Background Technology

[0002] With the development of autonomous driving technology, testing technology for autonomous driving is also constantly being innovated. The development phase of autonomous driving has shifted from function-based automated testing to scenario-based automated testing.

[0003] In related technologies, test case generation is an essential part of the testing process during the autonomous driving development phase. However, scenario-based testing and function-based testing differ significantly in their test case writing approaches.

[0004] However, in related technologies, test cases are often written in a generalized manner by using logical judgment. This makes it difficult to standardize the test case generation process when generating test cases for fixed and known scenario data. At the same time, the data analysis time is long, the generation efficiency is low, and the generated test cases are difficult to cover all possible problems of autonomous driving controllers in specific scenarios. As a result, the generated test cases lack specificity and comprehensiveness, which urgently needs to be solved. Summary of the Invention

[0005] This application provides a test case generation method and apparatus based on scenario data back-injection to solve the problems in related technologies, where test cases are often written in a generalized manner by logical judgment. This leads to difficulties in standardizing the test case generation process when generating test cases for fixed and known scenario data, as well as long data analysis time, low generation efficiency, and the inability of the generated test cases to simultaneously cover all possible problems of autonomous driving controllers in specific scenarios, resulting in insufficient relevance and comprehensiveness of the generated test cases.

[0006] The first aspect of this application provides a test case generation method based on scenario data back-injection, comprising the following steps: obtaining a software interface table, standard data package, real vehicle test issue sheet, and user scenario requirement document of a real vehicle during the testing process; performing requirement analysis based on the software interface table, the standard data package, the real vehicle test issue sheet, and / or the user scenario requirement document to determine the software interfaces to be tested in the test cases of the tested scenario, and extracting the tested scenario information and the expected values ​​of the output interfaces of the autonomous driving controller; based on the software interfaces to be tested, simultaneously opening the driving recording video data in the standard data package and the scenario data in the standard data package in different windows, finding the tested scenario based on the tested scenario information, and recording the start and end times of the tested scenario on the timeline of the driving recording video data in the standard data package; based on the start and end times, calculating the relative position of the detection time point with respect to the data start time, and determining all output values ​​and / or change patterns of the software interfaces to be tested at the start and end times according to the description of product functional requirements in the user scenario requirement document or by user evaluation, so as to write at least one test case according to the expected values.

[0007] Based on the above technical means, the embodiments of this application can identify video data in standard data packets by human intervention and use time-based marking to more specifically mark the scene under test in the scene data, perform multi-dimensional detection on the autonomous driving controller to write test cases, thereby making the generated autonomous driving test cases based on scene data back-injection cover a wide range of test points and be highly targeted, improving the writing efficiency and standardization of the autonomous driving test case generation process, and making it more reliable and practical.

[0008] Optionally, in one embodiment of this application, determining all output values ​​and / or change patterns of the software interface to be tested at the start and end times based on the description of product functional requirements in the user scenario requirements document or by means of user evaluation includes: identifying the first output value or change pattern of the first output value of the vertical control interface, the second output value or change pattern of the second output value of the horizontal control interface, the third output value or change pattern of the third output value of the user-displayed control interface, and the fourth output value or change pattern of the fourth output value of the state machine control interface.

[0009] Based on the above technical means, the embodiments of this application can identify the values ​​or value change patterns of each control interface, thereby enabling the detection of all output states of the controller in a specific scenario, broadening the detection coverage, and making the generated test cases more comprehensive.

[0010] Optionally, in one embodiment of this application, determining all output values ​​and / or change patterns of the software interface to be detected at the start and end times based on the description of product functional requirements in the user scenario requirements document or by means of user evaluation further includes: identifying the fifth output value or the change pattern of the fifth output value of all signals of each application layer software module within the autonomous driving control system.

[0011] Based on the above technical means, the embodiments of this application can identify the values ​​or value change patterns of all signals of each application layer software module inside the autonomous driving control, thereby further detecting the internal output state of the controller, deeply mining the test data, and making the generated test cases more complete.

[0012] Optionally, in one embodiment of this application, the standard data packet records the values ​​of any input interfaces that would cause any output interface value of the autonomous driving controller to change within a preset time period.

[0013] Based on the above technical means, in the embodiments of this application, the standard data packet records the value of any input interface that will cause any output interface value of the autonomous driving controller to change within a preset time period. By expanding the data coverage of the standard data packet, the level of detail in data acquisition during the test case generation process is further enriched.

[0014] A second aspect of this application provides a test case generation device based on scenario data back-injection, comprising: an acquisition module for acquiring a software interface table, standard data package, real vehicle test problem sheet, and user scenario requirement document of a real vehicle during the testing process; an analysis module for performing requirement analysis based on the software interface table, the standard data package, the real vehicle test problem sheet, and / or the user scenario requirement document, determining the software interfaces to be detected in the test cases of the tested scenario, and extracting the tested scenario information and the expected values ​​of the output interfaces of the autonomous driving controller; and a recording module for recording the test cases in different windows based on the software interfaces to be detected. The system opens the driving record video data and scene data in the standard data package, locates the scene under test based on the scene information, and records the start and end times of the scene under test on the timeline of the driving record video data in the standard data package. A generation module is used to calculate the relative position of the detection time point to the data start time based on the start and end times, and determines all output values ​​and / or change patterns of the software interface to be tested at the start and end times according to the description of product function requirements in the user scenario requirement document or user evaluation, so as to write at least one test case according to the expected value.

[0015] Optionally, in one embodiment of this application, the generation module includes: a first identification unit, used to identify the first output value of the longitudinal control interface or the variation pattern of the first output value, the second output value of the lateral control interface or the variation pattern of the second output value, the third output value of the user-displayed control interface or the variation pattern of the third output value, and the fourth output value of the state machine control interface or the variation pattern of the fourth output value.

[0016] Optionally, in one embodiment of this application, the generation module further includes: a second identification unit, used to identify the fifth output value or the variation pattern of the fifth output value of all signals of each application layer software module within the autonomous driving control.

[0017] Optionally, in one embodiment of this application, the standard data packet records the values ​​of any input interfaces that would cause any output interface value of the autonomous driving controller to change within a preset time period.

[0018] A third aspect of this application provides an electronic device, including: 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 test case generation method based on scenario data back-injection as described in the above embodiments.

[0019] A fourth aspect of this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described method for generating test cases based on scenario data back-injection.

[0020] The beneficial effects of this application are:

[0021] (1) In this embodiment, the video data in the standard data packet can be identified by human, and the scene under test can be marked more specifically in the scene data by time-pointing method. The autonomous driving controller can be detected from multiple angles to write test cases, so that the generated autonomous driving test cases based on scene data back-injection cover a wide range of test points and are highly targeted, improving the writing efficiency and standardization of the autonomous driving test case generation process, making it more reliable and practical.

[0022] (2) In this embodiment, the standard data packet records the value of any input interface that will cause any output interface value of the autonomous driving controller to change within a preset time period. By expanding the data coverage of the standard data packet, the level of detail of data acquisition during the test case generation process is further enriched.

[0023] (3) Based on the above technical means, the embodiments of this application can identify the values ​​or value change patterns of each control interface, thereby enabling the detection of all output states of the controller in a specific scenario, broadening the detection coverage, and making the generated test cases more comprehensive.

[0024] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0025] The above and / or additional aspects and advantages of this application will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, wherein:

[0026] Figure 1 This is a flowchart illustrating a test case generation method based on scenario data back-injection provided in an embodiment of this application;

[0027] Figure 2 This is a schematic diagram of a standard data packet timeline according to an embodiment of this application;

[0028] Figure 3 A flowchart for generating test cases based on scenario data back-injection according to one embodiment of this application;

[0029] Figure 4 This is a schematic diagram of the test case generation device based on scene data back-injection according to an embodiment of this application;

[0030] Figure 5 This is a schematic diagram of the structure of an electronic device according to an embodiment of this application.

[0031] Among them, 10-test case generation device based on scenario data back injection; 100-acquisition module, 200-analysis module, 300-recording module and 400-generation module; 501-memory, 502-processor and 503-communication interface. Detailed Implementation

[0032] The embodiments of this application are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this application, and should not be construed as limiting this application.

[0033] The following describes a test case generation method and apparatus based on scenario data back-annotation according to embodiments of this application, with reference to the accompanying drawings. In the related technologies mentioned in the background section, test cases are often written in a generalized manner using logical judgments. This leads to difficulties in standardizing the test case generation process when generating test cases for fixed and known scenario data, resulting in long data analysis times, low generation efficiency, and the inability of the generated test cases to simultaneously cover all possible problem points of the autonomous driving controller in a specific scenario, thus lacking specificity and comprehensiveness. This application provides a test case generation method based on scenario data back-annotation. It can obtain software interface tables, standard data packages, real vehicle test problem sheets, and user scenario requirement documents from the actual vehicle during testing. Based on the software interface tables, standard data packages, real vehicle test problem sheets, and / or user scenario requirement documents, it performs requirement analysis to determine the software interfaces to be tested in the test cases of the scenario under test and extracts the scenario under test. The expected values ​​of the information and autonomous driving controller output interfaces are determined based on the software interface to be tested. Simultaneously, the driving record video data and scene data from the standard data package are opened in different windows. The tested scene is located according to the tested scene information, and the start and end times of the tested scene on the timeline of the driving record video data in the standard data package are recorded. Based on the start and end times, the relative position of the detection time point with respect to the data start time is calculated. All output values ​​and / or change patterns of the software interface to be tested at the start and end times are determined according to the description of product functional requirements in the user scenario requirement document or user evaluation. At least one test case is written according to the expected values, thus enabling the generated autonomous driving test cases based on scene data back-injection to cover a wide range of test points and be highly targeted. This improves the efficiency and standardization of the autonomous driving test case generation process, making it more reliable and practical. This solves the problems in related technologies, where test cases are often written in a generalized manner based on logical judgments. This leads to difficulties in standardizing the test case generation process when generating test cases for fixed and known scenario data. Additionally, the data analysis time is long, the generation efficiency is low, and the generated test cases cannot simultaneously cover all possible problems of the autonomous driving controller in a specific scenario, resulting in insufficient relevance and comprehensiveness of the generated test cases.

[0034] Specifically, Figure 1 This is a flowchart illustrating a test case generation method based on scenario data back-injection provided in an embodiment of this application.

[0035] like Figure 1 As shown, this test case generation method based on scenario data back-injection includes the following steps:

[0036] In step S101, the software interface table, standard data package, real vehicle test problem sheet, and user usage scenario requirement document of the actual vehicle during the testing process are obtained.

[0037] It is understood that the embodiments of this application can obtain the software interface table, standard data package, real vehicle test problem sheet, and user usage scenario requirement document of the actual vehicle during the testing process. By acquiring various data of the actual vehicle during the testing process, the required data can be collected from multiple perspectives, thereby improving the comprehensiveness of data acquisition during the test case generation process.

[0038] The software interface table provides detailed descriptions of all software interfaces output by the controller, including descriptions of each interface to provide the testing targets for test cases. The scenario data in the standard data package can be typical usage scenarios or scenario data from actual vehicle issues. A single actual vehicle standard data package represents one test case or a set of multiple test cases. The actual vehicle test issue sheet can contain actual vehicle issue information, providing a basis for data analysis. For example, the descriptions in the actual vehicle issue sheet can be used to locate the various scenarios to be tested in the standard data package. The user scenario requirement document contains the scenario requirements that the product must meet, providing a basis for data analysis. For example, the descriptions in the scenario requirement document can be used to locate the various scenarios to be tested in the standard data package.

[0039] Optionally, in one embodiment of this application, the standard data packet records the values ​​of any input interfaces that would cause any output interface value of the autonomous driving controller to change within a preset time period.

[0040] It is understood that the preset duration in this application embodiment is the predetermined time length for recording the value of any input interface that causes any output interface value of the autonomous driving controller to change in the standard data packet. The standard data packet may include scene data input to the test object during the test execution process, and trip recording video data synchronized with the scene data time, similar to the video data of a dashcam, that is, each frame corresponds to the scene data at the same time.

[0041] It should be noted that the preset duration is set by those skilled in the art based on the actual situation, and no specific limitation is made here.

[0042] The standard data packet in this application embodiment records the values ​​of any input interfaces that will cause any output interface value of the autonomous driving controller to change within a preset time period. By expanding the data coverage of the standard data packet, the level of detail in data acquisition during the test case generation process is further enriched.

[0043] In step S102, requirements analysis is performed based on the software interface table, standard data package, real vehicle test problem sheet and / or user scenario requirement document to determine the software interfaces to be tested in the test cases of the tested scenario, and extract the tested scenario information and the expected values ​​of the output interface of the autonomous driving controller.

[0044] In actual execution, after acquiring the standard data package collected during real-vehicle testing, the data in the standard data package can be analyzed based on the testers' descriptions of the problems encountered in the real vehicle during testing or user scenario requirement documents. The requirement analysis process may include identifying the software interfaces to be tested in the test cases based on the scenario, entering the names of the interfaces to be tested into the test cases, extracting the tested scenario information by analyzing the real-vehicle test problem sheets, and extracting the expected values ​​of the autonomous driving controller output interfaces based on the scenario by analyzing the user scenario requirement documents.

[0045] This application embodiment can perform requirements analysis based on software interface tables, standard data packages, real vehicle test problem sheets, and / or user scenario requirement documents to determine the software interfaces that need to be tested in the test cases of the tested scenario, extract the test scenario information and the expected values ​​of the output interfaces of the autonomous driving controller, and obtain the corresponding content required in the test case generation process by analyzing and processing the data obtained in the real vehicle test process, thereby improving the completeness of the test case writing process.

[0046] In step S103, based on the software interface to be detected, the driving record video data and scene data in the standard data package are opened simultaneously in different windows. The scene to be tested is found according to the scene information and the start and end times of the scene to be tested on the timeline in the driving record video data in the standard data package are recorded.

[0047] It is understood that in this embodiment of the application, the test scene can be found by manually identifying video data in the standard data packet, thereby finding the test scene and locking the time or time period of the test scene.

[0048] In some embodiments, a dedicated visualization tool can be used to simultaneously open the dashcam data and scene data in the standard data package in different windows. The dedicated data visualization tool is used to open the dashcam data in the standard data package, and then the test scene data in the standard data package is opened through the interface data analysis window of the visualization tool. The specific interface name to be opened is consistent with the interface to be detected. The test scene is found by watching the dashcam data in the standard data package, and the start and end times of the scene on the timeline in the dashcam data in the standard data package are recorded.

[0049] This application embodiment can analyze the data in the standard data packet, find the test scenario based on the scenario information, and determine the start and end times of the test scenario on the timeline of the standard data packet, thereby improving the data processing efficiency, shortening the analysis time of the test case generation process, and using time-marking to mark the required test scenario, which improves the relevance of the data analysis results and makes them more explicit.

[0050] In step S104, based on the start and end times, the relative position of the detection time point with respect to the data start time is calculated. Based on the description of product functional requirements in the user scenario requirement document or by user evaluation, all output values ​​and / or change patterns of the software interface to be tested at the start and end times are determined, so as to write at least one test case according to the expected value.

[0051] It is understood that, in the embodiments of this application, the relative position of the detection time point with respect to the data start time can be calculated after determining the start and end times of the tested scenario on the standard data packet timeline. The code can be used to compare whether the actual output of the controller is consistent with the expected value, and then the test cases can be written according to the expected value.

[0052] For example, such as Figure 2 The diagram shown is a schematic representation of a standard data packet timeline according to an embodiment of this application, providing a calculation method for...

[0053] ΔT1=T1-T0

[0054] ΔT2=T2-T0

[0055] Wherein, ΔT1 is the difference between the start time of the tested scenario and the start time of the standard data packet, ΔT2 is the difference between the end time of the tested scenario and the start time of the standard data packet, T0 is the start time of the standard data packet, T1 is the start time of the tested scenario, and T2 is the end time of the tested scenario. The value of ΔT1 is used to locate the position of time T1 in the standard data packet on the time axis, and the value of ΔT2 is used to locate the position of time T2 in the standard data packet on the time axis. This relative time can be used for writing automated test code.

[0056] In actual execution, after calculating the relative position of the detection time point with respect to the data start time, the output values ​​of the interface to be detected at times T1 and T2 can be determined based on the description of product functional requirements in the user scenario requirement document or by user evaluation. Alternatively, the change pattern of some interfaces between times T1 and T2 can be detected.

[0057] The embodiments of this application can calculate the relative position of the detection time point with respect to the data start time, determine all output values ​​and / or change patterns of the software interface to be detected at the start and end times, and write at least one test case according to the expected value, thereby improving the standardization of the autonomous driving test case generation process and making it more practical.

[0058] Optionally, in one embodiment of this application, the software interface to be tested is determined based on the description of product functional requirements in the user scenario requirements document or by user evaluation, including: identifying the first output value or the change pattern of the first output value of the vertical control interface, the second output value or the change pattern of the second output value of the horizontal control interface, the third output value or the change pattern of the third output value of the user-displayed control interface, and the fourth output value or the change pattern of the fourth output value of the state machine control interface.

[0059] It is understood that in the embodiments of this application, the method of simultaneously detecting the lateral control signal, longitudinal control signal, and user-displayed control signal of the autonomous driving controller can be adopted, that is, simultaneously judging the output value or value change pattern of the longitudinal control interface, the output value or value change pattern of the lateral control interface, the output value or value change pattern of the user-displayed control interface, and the control interface value or value change pattern of the state machine.

[0060] The embodiments of this application can identify the values ​​or value change patterns of each control interface, thereby enabling the detection of all output states of the controller in a specific scenario, broadening the detection coverage, and making the generated test cases more comprehensive.

[0061] Optionally, in one embodiment of this application, determining all output values ​​and / or change patterns of the software interface to be detected at the start and end times based on the description of product functional requirements in the user scenario requirements document or by means of user evaluation, further includes: identifying the fifth output value or the change pattern of the fifth output value of all signals of each application layer software module within the autonomous driving control.

[0062] In actual execution, in addition to identifying the values ​​of the vehicle's lateral control output interface, longitudinal control output interface, user display control output interface, and state machine control output interface in the above steps, as well as the objects that detect the change patterns of some of these interfaces, it may also include the output of all signals of all software modules inside the tested object in this scenario, including but not limited to the signal output values ​​or value change patterns of the perception, fusion, prediction, planning, and control modules.

[0063] The embodiments of this application can identify the values ​​or value change patterns of all signals in each application layer software module within the autonomous driving control system, thereby further detecting the internal output state of the controller, deeply mining test data, and making the generated test cases more complete.

[0064] like Figure 4 As shown below, the working content of the embodiment of this application will be described in detail with a specific example.

[0065] Step S301: Obtain the required information and standard data package.

[0066] In other words, the requirements and standard data packages need to be obtained, including: a software interface table, standard data packages, a real-vehicle test issue sheet, and a user scenario requirement document. The software interface table should describe in detail all software interfaces output by the controller, along with descriptions of each interface, and provide the objects to be tested in the test cases. The standard data package must contain two main parts: the first part is the scene data input to the tested object during test execution; the second part is the recorded video data synchronized with the scene data, similar to dashcam video data, where each frame of this dashcam-like video data corresponds to the scene data at the same time. The real-vehicle test issue sheet contains real-vehicle problem information, providing a basis for data analysis. Based on the descriptions in the real-vehicle test issue sheet, the various scenarios to be tested are located in the standard data package. The user scenario requirement document contains the scenario requirements that the product must meet, providing a basis for data analysis. Based on the descriptions in the user scenario requirement document, the various scenarios to be tested are located in the standard data package.

[0067] Step S302: Requirements Analysis.

[0068] In other words, after obtaining the aforementioned software interface table, standard data package, real vehicle test issue sheet, or user scenario requirement document, a requirement analysis is performed. The purpose of the requirement analysis is to determine the software interfaces that need to be tested in the test cases based on the scenario, including longitudinal control interfaces, lateral control interfaces, user display control interfaces, and state machine state control output interfaces. The names of the interfaces to be tested are recorded in the test cases. By analyzing the real vehicle test issue sheet, the information of the tested scenario is extracted. And by analyzing the user scenario requirement document, the expected values ​​of the output interfaces of the autonomous driving controller based on the scenario are extracted.

[0069] Step S303: Data analysis.

[0070] In other words, after requirements analysis, data analysis is performed using a dedicated visualization tool. This tool can simultaneously open the dashcam video data and scene data from the standard data package in different windows. Using this dedicated data visualization tool, the dashcam video data from the standard data package is opened separately, and then the test scene data from the standard data package is opened through the interface data analysis window of the visualization tool. The specific interface name to be opened is consistent with the interface to be tested during requirements analysis S302. By viewing the dashcam video data in the standard data package, the test scene in S302 is identified, and the start and end times of this scene on the timeline of the dashcam video data in the standard data package are recorded.

[0071] Step S304: Calculate the relative position of the detection time point with respect to the data start time.

[0072] In other words, after determining the start and end times of the tested scenario on the standard data packet timeline, the relative position of the detection time point with respect to the data start time is calculated. After calculating the relative position of the detection time point with respect to the data start time, the output values ​​of the interfaces to be tested at the corresponding time are determined based on the description of product functional requirements in the user scenario requirement document or by user evaluation, or the change patterns of some detection interfaces in S302 at the corresponding time.

[0073] Step S305: Determine the longitudinal control interface.

[0074] In other words, it involves determining the output value or the pattern of change of the value of the longitudinal control interface.

[0075] Step S306: Determine the horizontal control interface.

[0076] In other words, it is necessary to determine the output value or the pattern of change of the value of the horizontal control interface.

[0077] Step S307: Determine the control interface displayed by the user.

[0078] In other words, it involves determining the output value or the pattern of change of the value displayed by the user's control interface.

[0079] Step S308: Determine the control interface of the state machine.

[0080] In other words, it involves determining the output value or the pattern of change of the control interface of the state machine.

[0081] Step S309: Optional: Determine and control the internal software interfaces.

[0082] In other words, it selectively judges the signal output values ​​or the changing patterns of all signal values ​​in each application layer software module within the autonomous driving control system.

[0083] Step S310: Test case writing.

[0084] In other words, test cases are written based on the conclusions drawn.

[0085] According to the test case generation method based on scenario data back-injection proposed in this application, the software interface table, standard data package, real vehicle test problem sheet, and user scenario requirement document of the actual vehicle during the testing process can be obtained. Based on the software interface table, standard data package, real vehicle test problem sheet, and / or user scenario requirement document, requirement analysis is performed to determine the software interfaces to be tested in the test cases of the tested scenario. The expected values ​​of the output interfaces of the autonomous driving controller are extracted from the tested scenario information. Based on the software interfaces to be tested, the driving recording video data and scenario data in the standard data package are simultaneously opened in different windows. Based on the tested scenario information... The system identifies the test scenario and records its start and end times on the timeline of the driving recording video data within the standard data package. Based on these times, it calculates the relative position of the detection time point to the data start time. It then determines all output values ​​and / or variation patterns of the software interface to be tested at the start and end times based on the description of product functional requirements in the user scenario requirement document or user evaluations. At least one test case is then written according to the expected values. This results in autonomous driving test cases generated based on scenario data back-injection, covering a wide range of test points with strong targeting. This improves the efficiency and standardization of autonomous driving test case generation, making it more reliable and practical. This addresses the problems in related technologies where test cases are often generalized through logical judgments, leading to difficulties in standardizing the test case generation process for fixed and known scenario data. Furthermore, this results in long data analysis times, low generation efficiency, and the inability to simultaneously cover all possible problems of the autonomous driving controller in a specific scenario, leading to insufficient targeting and comprehensiveness of the generated test cases.

[0086] Next, referring to the accompanying drawings, a test case generation device based on scenario data back-injection proposed according to an embodiment of this application is described.

[0087] Figure 4 This is a block diagram of a test case generation device based on scenario data back-injection according to an embodiment of this application.

[0088] like Figure 4 As shown, the test case generation device 10 based on scenario data back-injection includes: an acquisition module 100, an analysis module 200, a recording module 300, and a generation module 400.

[0089] The acquisition module 100 is used to acquire the software interface table, standard data package, real vehicle test problem sheet, and user usage scenario requirement document of the actual vehicle during the testing process.

[0090] The analysis module 200 is used to perform requirements analysis based on the software interface table, standard data package, real vehicle test problem sheet and / or user scenario requirement document, determine the software interfaces that need to be tested in the test cases of the tested scenario, and extract the tested scenario information and the expected values ​​of the output interface of the autonomous driving controller.

[0091] The recording module 300 is used to simultaneously open the driving record video data and scene data in the standard data package in different windows based on the software interface to be detected, find the scene to be tested according to the scene information, and record the start and end times of the scene to be tested on the timeline of the driving record video data in the standard data package.

[0092] The generation module 400 is used to calculate the relative position of the detection time point with respect to the data start time based on the start and end times, and to determine all output values ​​and / or change patterns of the software interface to be tested at the start and end times based on the description of product functional requirements in the user scenario requirement document or by user evaluation, so as to write at least one test case according to the expected value.

[0093] Optionally, in one embodiment of this application, the generation module 400 includes: a first identification unit.

[0094] The first identification unit is used to identify the first output value or the change pattern of the first output value of the longitudinal control interface, the second output value or the change pattern of the second output value of the lateral control interface, the third output value or the change pattern of the third output value of the user-displayed control interface, and the fourth output value or the change pattern of the fourth output value of the state machine control interface.

[0095] Optionally, in one embodiment of this application, the generation module 400 further includes a second identification unit.

[0096] The second identification unit is used to identify the fifth output value or the change pattern of the fifth output value of all signals of each application layer software module inside the autonomous driving control.

[0097] Optionally, in one embodiment of this application, the standard data packet records the values ​​of any input interfaces that would cause any output interface value of the autonomous driving controller to change within a preset time period.

[0098] It should be noted that the foregoing explanation of the test case generation method embodiment based on scenario data back-injection also applies to the test case generation device based on scenario data back-injection in this embodiment, and will not be repeated here.

[0099] According to the test case generation device based on scenario data back-injection proposed in the embodiments of this application, it can acquire the software interface table, standard data package, real vehicle test problem sheet, and user usage scenario requirement document of the actual vehicle during the testing process. Based on the software interface table, standard data package, real vehicle test problem sheet, and / or user usage scenario requirement document, it performs requirement analysis to determine the software interfaces to be tested in the test cases of the tested scenario. It extracts the tested scenario information and the expected values ​​of the output interfaces of the autonomous driving controller. Based on the software interfaces to be tested, it simultaneously opens the driving recording video data and scenario data in the standard data package in different windows. Based on the tested scenario information... The system identifies the test scenario and records its start and end times on the timeline of the driving recording video data within the standard data package. Based on these times, it calculates the relative position of the detection time point to the data start time. It then determines all output values ​​and / or variation patterns of the software interface to be tested at the start and end times based on the description of product functional requirements in the user scenario requirement document or user evaluations. At least one test case is then written according to the expected values. This results in autonomous driving test cases generated based on scenario data back-injection, covering a wide range of test points with strong targeting. This improves the efficiency and standardization of autonomous driving test case generation, making it more reliable and practical. This addresses the problems in related technologies where test cases are often generalized through logical judgments, leading to difficulties in standardizing the test case generation process for fixed and known scenario data. Furthermore, this results in long data analysis times, low generation efficiency, and the inability to simultaneously cover all possible problems of the autonomous driving controller in a specific scenario, leading to insufficient targeting and comprehensiveness of the generated test cases.

[0100] Figure 5 A schematic diagram of the structure of an electronic device provided in an embodiment of this application. The electronic device may include:

[0101] The memory 501, the processor 502, and the computer program stored on the memory 501 and capable of running on the processor 502.

[0102] When processor 502 executes the program, it implements the test case generation method based on scenario data back-injection provided in the above embodiments.

[0103] Furthermore, electronic devices also include:

[0104] Communication interface 503 is used for communication between memory 501 and processor 502.

[0105] The memory 501 is used to store computer programs that can run on the processor 502.

[0106] The memory 501 may include high-speed RAM memory, and may also include non-volatile memory, such as at least one disk storage device.

[0107] If the memory 501, processor 502, and communication interface 503 are implemented independently, then the communication interface 503, memory 501, and processor 502 can be interconnected via a bus to complete communication between them. The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of representation, Figure 5 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0108] Optionally, in a specific implementation, if the memory 501, processor 502, and communication interface 503 are integrated on a single chip, then the memory 501, processor 502, and communication interface 503 can communicate with each other through an internal interface.

[0109] Processor 502 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this application.

[0110] This embodiment also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described test case generation method based on scenario data back-injection.

[0111] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0112] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "N" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0113] Any process or method described in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or N executable instructions for implementing custom logic functions or processes, and the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functions involved, as should be understood by those skilled in the art to which embodiments of this application pertain.

[0114] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-included system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of computer-readable media include: an electrical connection having one or more wires (electronic device), a portable computer disk drive (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Alternatively, the computer-readable medium may be paper or other suitable media on which the program can be printed, since the program can be obtained electronically by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in a computer memory.

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

[0116] Those skilled in the art will understand that all or part of the steps of the methods in the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, the program includes one or a combination of the steps of the method embodiments.

[0117] Furthermore, the functional units in the various embodiments of this application can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into a module. The integrated module can be implemented in hardware or as a software functional module. If the integrated module is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium.

[0118] The storage medium mentioned above can be a read-only memory, a disk, or an optical disk, etc. Although embodiments of this application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting this application. Those skilled in the art can make changes, modifications, substitutions, and variations to the above embodiments within the scope of this application.

Claims

1. A test case generation method based on scenario data back injection, characterized in that, Includes the following steps: Obtain the software interface table, standard data package, real vehicle test problem sheet, and user scenario requirement document of the actual vehicle during the testing process; Based on the software interface table, the standard data package, the real vehicle test problem sheet and / or the user usage scenario requirement document, a requirement analysis is performed to determine the software interfaces that need to be tested in the test cases of the tested scenario, and to extract the test scenario information and the expected values ​​of the output interface of the autonomous driving controller. Based on the software interface to be detected, the driving record video data and scene data in the standard data package are simultaneously opened in different windows. The scene to be tested is located according to the information of the scene under test, and the start and end times of the scene under test on the timeline of the driving record video data in the standard data package are recorded; and Based on the start and end times, calculate the relative position of the detection time point with respect to the data start time, and determine all output values ​​and / or change patterns of the software interface to be tested at the start and end times according to the description of product functional requirements in the user scenario requirement document or by user evaluation, so as to write at least one test case according to the expected value. The standard data packet records the values ​​of any input interfaces that, within a preset time period, would cause any output interface value of the autonomous driving controller to change.

2. The method according to claim 1, characterized in that, The determination of all output values ​​and / or change patterns of the software interface to be tested at the start and end times, based on the description of product functional requirements in the user scenario requirement document or through user evaluation, includes: Identify the first output value or the variation pattern of the first output value of the longitudinal control interface, the second output value or the variation pattern of the second output value of the lateral control interface, the third output value or the variation pattern of the third output value of the user-displayed control interface, and the fourth output value or the variation pattern of the fourth output value of the state machine control interface.

3. The method according to claim 2, characterized in that, The step of determining all output values ​​and / or change patterns of the software interface to be tested at the start and end times based on the description of product functional requirements in the user scenario requirement document or through user evaluation also includes: Identify the fifth output value or the variation pattern of the fifth output value of all signals of each application layer software module within the autonomous driving control system.

4. A test case generation device based on scenario data back-injection, characterized in that, include: The acquisition module is used to acquire the software interface table, standard data package, real vehicle test problem sheet, and user scenario requirement document of the actual vehicle during the testing process; The analysis module is used to perform requirements analysis based on the software interface table, the standard data package, the real vehicle test problem sheet and / or the user usage scenario requirement document, determine the software interfaces that need to be tested in the test cases of the tested scenario, and extract the tested scenario information and the expected values ​​of the output interface of the autonomous driving controller. The recording module is used to simultaneously open the driving record video data and the scene data in the standard data package in different windows based on the software interface to be detected, find the scene to be tested according to the scene information, and record the start and end times of the scene to be tested on the timeline in the driving record video data in the standard data package. as well as The generation module is used to calculate the relative position of the detection time point with respect to the data start time based on the start and end times, and to determine all output values ​​and / or change patterns of the software interface to be tested at the start and end times according to the description of product functional requirements in the user scenario requirement document or by means of user evaluation, so as to write at least one test case according to the expected value. The standard data packet records the values ​​of any input interfaces that, within a preset time period, would cause any output interface value of the autonomous driving controller to change.

5. The apparatus according to claim 4, characterized in that, The generation module includes: The first identification unit is used to identify the first output value or the variation pattern of the first output value of the longitudinal control interface, the second output value or the variation pattern of the second output value of the lateral control interface, the third output value or the variation pattern of the third output value of the user-displayed control interface, and the fourth output value or the variation pattern of the fourth output value of the state machine control interface.

6. The apparatus according to claim 5, characterized in that, The generation module further includes: The second identification unit is used to identify the fifth output value or the variation pattern of the fifth output value of all signals of each application layer software module inside the autonomous driving control.

7. An electronic device, characterized in that, include: The memory, the processor, and the computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the test case generation method based on scenario data back-injection as described in any one of claims 1-3.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that, The program is executed by the processor to implement the test case generation method based on scenario data back-injection as described in any one of claims 1-3.

Images