Vehicle test assistance method and vehicle test assistance system

Abstract

The invention relates to a vehicle test auxiliary method and a vehicle test auxiliary system, and relates to the technical field of software test and data management. According to the scheme, in response to a vehicle test request, a test session is established based on a selected session mode when a vehicle test starts, and the session mode comprises a new session mode, a continuous writing session mode and the like; in the vehicle testing process, the log operation instruction can be responded, and the log entry is operated based on the corresponding structured format; further, in response to the save instruction, all log entries may be persistently stored based on the trigger opportunity and the session pattern at the end or disruption of the vehicle test. According to the scheme, the recording efficiency of the vehicle test process can be improved, and the recording error rate is reduced; on the basis, vehicle test process records are achieved in a standardized and structured format, subsequent reading and analysis are facilitated, centralized and continuous recording can be achieved, tracing and reproduction are facilitated, and therefore vehicle design, production, distribution and maintenance are better supported.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to the technical field of software testing and data management, in particular, to a vehicle test auxiliary method and a vehicle test auxiliary system. BACKGROUND

[0002] Vehicle testing can refer to a process of a large number of repeated verification tests on functions and performances of a vehicle, such as an automated test on an unmanned transport truck in a closed test field. During the vehicle testing process, a test personnel usually needs to manually record the test process in a paper bill or an electronic table.

[0003] Through manual recording by the test personnel, there are problems of low recording efficiency and high error rate, and non-structured data is difficult to read and analyze. On this basis, when a test fails, it is also inconvenient to trace the record, which leads to difficulties in problem positioning and test reproduction, and when the test is interrupted, another record is usually needed, which leads to scattered records. Therefore, during the vehicle testing process, the recording is cumbersome, inefficient, error-prone, and scattered, which also makes the subsequent sorting and analysis time-consuming and laborious. SUMMARY

[0004] The purpose of the present disclosure is to provide a vehicle test auxiliary method and a vehicle test auxiliary system, which can improve the recording efficiency of the vehicle testing process, reduce the error rate, facilitate reading and analysis in a standardized and structured format, and also realize centralized and continuous recording, which is convenient for tracing and reproduction, thereby better supporting vehicle design, production, distribution and maintenance.

[0005] According to a first aspect of the present disclosure, a vehicle test auxiliary method is provided, which can include: in response to a vehicle test request, establishing a corresponding test session based on a selected session mode; the session mode includes at least one of a new session mode and a continuation session mode; in response to a log operation instruction, operating a log entry based on a structured format corresponding to the log operation instruction; in response to a save instruction, persistently storing all log entries based on a trigger time and a session mode.

[0006] Optionally, the session mode is a new session mode, and in response to the vehicle test request, establishing the corresponding test session based on the selected session mode includes: in response to the vehicle test request, obtaining a vehicle test location and a version number of a program to be tested; dynamically loading a corresponding vehicle identifier set based on the vehicle test location; in response to a vehicle selection instruction for the vehicle identifier set, determining a target vehicle identifier; and based on the vehicle test location, the version number of the program to be tested, and the target vehicle identifier, creating the test session.

[0007] Optionally, the conversation mode is a continuation conversation mode, and the corresponding test session is established based on the selected conversation mode in response to the vehicle test request, including: reading a historical log of a history record file persistent storage in response to the vehicle test request; creating a test session with the historical log, and marking the test session as a history record continuation.

[0008] Optionally, the log operation instruction is a standard operation record instruction, and the log entry is operated based on the structured format corresponding to the log operation instruction in response to the log operation instruction, including: obtaining a system timestamp in response to the log operation instruction; obtaining a predefined operation description and a measured program feedback result for the vehicle test process; and generating a log entry in the structured format in combination with the system timestamp, the operation description, and the measured program feedback result.

[0009] Optionally, the log operation instruction is a to-be-investigated event record instruction, and the log entry is operated based on the structured format corresponding to the log operation instruction in response to the log operation instruction, including: obtaining a system timestamp in response to the log operation instruction; obtaining a predefined standardized event description for a to-be-investigated event in the vehicle test process; and generating a log entry in the structured format in combination with the system timestamp, the standardized event description, and an analysis result placeholder.

[0010] Optionally, the log operation instruction is a process marker record instruction, and the log entry is operated based on the structured format corresponding to the log operation instruction in response to the log operation instruction, including: obtaining a system timestamp in response to the log operation instruction; obtaining a predefined process marker description for the vehicle test process to generate a log entry in the structured format; and the process marker description includes at least one of a test phase marker and a test area identifier.

[0011] Optionally, the log operation instruction is an auxiliary marker record instruction, and the log entry is operated based on the structured format corresponding to the log operation instruction in response to the log operation instruction, including: obtaining an auxiliary description content in the structured format in response to the log operation instruction; the auxiliary description content includes at least one of a system timestamp and a predefined text segment; and the auxiliary description content is inserted into the log entry.

[0012] Optionally, the log operation instruction is a record modification instruction, and the log entry is operated based on the structured format corresponding to the log operation instruction in response to the log operation instruction, including: determining a corresponding log entry in response to the log operation instruction; and performing a modification operation on the log entry in the structured format.

[0013] Optionally, in response to the save instruction, the all log entries are persistently stored based on the trigger time and the session mode, comprising: in response to the save instruction, obtaining all log entries; in the case that the trigger time is the first trigger and the session mode is the new session mode, creating a session record file in a preset path and writing all log entries into the session record file for persistent storage; in the case that the trigger time is the first trigger and the session mode is the continuation session mode, overwriting all log entries into the history record file for persistent storage; in the case that the trigger time is the non-first trigger and the session mode is the new session mode, overwriting all log entries into the session record file for persistent storage; in the case that the trigger time is the non-first trigger and the session mode is the continuation session mode, overwriting all log entries into the history record file for persistent storage.

[0014] Optionally, the method is implemented based on a vehicle test application; the method further comprises: in response to an application start event, performing a singleton check of the shared memory for the vehicle test application; and when the singleton check passes, creating the shared memory corresponding to the vehicle test application.

[0015] Optionally, after the log entries are operated based on the structured format corresponding to the log operation instruction, the method further comprises: setting a modified flag bit at the position of the log entry that is operated; and after all log entries are persistently stored, the method further comprises: resetting the modified flag bit.

[0016] Optionally, the method is implemented based on a vehicle test application; the method further comprises: in response to an application close event, checking the modified flag bit; and in the case that the modified flag bit exists, prompting that there are unsaved log entries.

[0017] According to a second aspect of the present disclosure, a vehicle test auxiliary system is provided, which is configured to implement the vehicle test auxiliary method of the first aspect.

[0018] According to a third aspect of the present disclosure, an electronic device is provided, comprising: a processor; and a memory for storing a computer program of the processor; wherein the processor is configured to implement the vehicle test auxiliary method of the first aspect by executing the computer program.

[0019] According to a fourth aspect of the present disclosure, a computer readable storage medium is provided, which stores a computer program, and the computer program is executed by a processor to implement the vehicle test auxiliary method of the first aspect.

[0020] According to a fifth aspect of the present disclosure, a computer program product is provided, which, when running on an electronic device, causes the electronic device to perform a vehicle test assisting method as described in the first aspect.

[0021] The present disclosure provides a vehicle test assisting method and a vehicle test assisting system. The method can establish a corresponding test session based on a selected session mode at the start of a vehicle test in response to a vehicle test request, where the session mode can include a new session mode, a continuation session mode, etc. Then, the method can operate log entries based on a corresponding structured format in response to a log operation instruction during the vehicle test. Further, the method can persistently store all log entries based on a triggering time and a session mode in response to a save instruction at the end or interruption of the vehicle test. The method can improve the efficiency of vehicle test process recording and reduce the recording error rate. Furthermore, the vehicle test process recording is implemented in a standardized and structured format, which is convenient for subsequent reading and analysis, and can also realize centralized and continuous recording, which is convenient for tracing and reproduction, thereby better supporting vehicle design, production, distribution and maintenance.

[0022] It should be understood that the foregoing general description and the following detailed description are only exemplary and explanatory, and are not limiting to the present disclosure. BRIEF DESCRIPTION OF DRAWINGS

[0023] The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate embodiments consistent with the present disclosure and serve to explain the principles of the present disclosure. It is apparent that the accompanying drawings described below are only some embodiments of the present disclosure, and other drawings can be obtained by those skilled in the art without creative labor based on these drawings.

[0024] Figure 1 One of the step flowcharts of the vehicle test assisting method provided by the embodiments of the present disclosure.

[0025] Figure 2 The second step flowchart of the vehicle test assisting method provided by the embodiments of the present disclosure.

[0026] Figure 3 One of the display interface schematic diagrams provided by the vehicle test assisting system provided by the embodiments of the present disclosure.

[0027] Figure 4 The second display interface schematic diagram provided by the vehicle test assisting system provided by the embodiments of the present disclosure.

[0028] Figure 5 The content display schematic diagram of the session record file provided by the embodiments of the present disclosure.

[0029] Figure 6A structural schematic diagram of an electronic device provided by an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0030] Example implementations are now described with reference to the drawings; however, these descriptions are not intended to limit the scope of the present disclosure, but are intended to provide examples of implementations for the present disclosure as claimed hereinafter. The descriptions as set forth herein are not intended to be exhaustive or otherwise to limit the implementations to the precise forms disclosed. Many modifications and variations are possible in light of this disclosure. For example, while the implementations are described chiefly for a mobile device, they can be implemented by any device capable of wireless communication. Moreover, it should be understood that no limitation of the scope of the concepts disclosed arises from the description of a given example or a given implementation. It is also noted that the examples or implementations described are intended to be illustrative only and that numerous other configurations within the scope of the present disclosure are also envisioned.

[0031] Furthermore, the drawings are diagrammatic and schematic representations of only some embodiments of the present disclosure, and are not necessarily drawn to scale. Identical or similar components are referred to using the same reference numerals throughout the drawings, and thus will not be repeatedly described. Some of the blocks in the diagrams are functional blocks that represent functions implemented by software, hardware, or combinations thereof, and thus the functions performed by each of the blocks are not limited by the names of the blocks. The functional blocks can be implemented as software, or in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0032] It should be noted that the data obtained by the present disclosure is accessed, collected, stored and applied to subsequent analysis and processing with the consent and authorization of the user or the party to which the data belongs after the user or the party to which the data belongs is explicitly informed of the collection content, data use, processing method, etc. of the data, and the user or the party to which the data belongs is sent the way to access, correct, delete the data, and the method to revoke the consent and authorization.

[0033] Figure 1 A step flowchart of a vehicle test auxiliary method provided by an embodiment of the present disclosure is shown. The step flow of the method can be shown in the following steps 101 to 103.

[0034] Step 101, in response to a vehicle test request, establishing a corresponding test session based on a selected session mode; the session mode includes at least one of a new session mode and a continuation session mode.

[0035] In the embodiments of the present disclosure, the vehicle test can be a test and evaluation on the normal operation of the vehicle in a test environment simulating actual working conditions, can include specific function or mode targeted test, such as wake-up and sleep, ignition and shutdown, start and stop, parking and departure, self-driving and manual mode switching test, and can also include multi-link combined test, such as full-process test, obstacle parking test, etc. When the vehicle test starts, the tester can initiate a vehicle test request. In response to the vehicle test request, a corresponding test session can be established, and then the tester can record the process of the vehicle test through the test session. In the vehicle test request, the session mode to which the test session belongs can be selected, wherein the new session mode corresponds to a vehicle test from the beginning, and the continuation session mode corresponds to a vehicle test from the historical test interruption. Wherein, only one test session is run at the same time to avoid data conflicts.

[0036] Step 102, in response to the log operation instruction, operating the log entry based on the structured format corresponding to the log operation instruction.

[0037] In the embodiments of the present disclosure, the log entry can include log data recorded based on a predefined structured format of the vehicle process. During the vehicle test, the tester can trigger a log operation instruction according to the test process. On this basis, in response to the log operation instruction, the log entry can be operated in the corresponding structured format, such as adding a record of the log entry based on the structured format, or adjusting the recorded log entry based on the structured format, etc. The structured format can be a unified predefined standardized log format, which can define the data type, filling position through the field, and can also preset the optional text segment description, and the embodiments of the present disclosure do not make specific limitations.

[0038] Step 103, in response to the save instruction, persistently storing all log entries based on the trigger time and session mode.

[0039] In the embodiments of the present disclosure, when the vehicle test is ended, interrupted or completed, the tester can trigger a save instruction according to the test process. On this basis, in response to the save instruction, all log entries in a vehicle test can be persistently stored. Wherein, according to the different trigger time and session mode, the processing mode of persistent storage is also different. The trigger time can be to distinguish whether the save instruction is triggered for the first time in the vehicle test process, and the session mode can be to distinguish whether the test session belongs to the new session mode or the continuation session mode, on the basis of which the data file is created or called, and the acquisition of all log entries is different, and the person skilled in the art can set it according to the actual situation, and the embodiments of the present disclosure do not make specific settings.

[0040] In an optional embodiment of the method disclosed herein, the session mode is a new session mode, and the aforementioned step 101 may include the following steps A1 to A4.

[0041] Step A1: In response to the vehicle test request, obtain the vehicle test location and the version number of the program under test.

[0042] In this embodiment of the disclosure, in response to a vehicle test request established for a test session in a new session mode, the vehicle test location and the version number of the program under test can be obtained. The vehicle test location can be a location corresponding to a test environment simulating actual working conditions, and can be uniquely identified using a number, coordinates, or other information. The version number of the program under test is used to identify the development version of the program under test, which can be a software program that supports vehicle operation. During vehicle testing, various aspects of the vehicle, including mechanical structure and software programs, can be tested. Obtaining the vehicle test location can be done by obtaining the identifier input by the tester, or by providing the tester with an option for the vehicle test location identifier, and obtaining the vehicle test location based on the tester's selection of the option; similarly, obtaining the version number of the program under test can be done in the same way.

[0043] Step A2: Dynamically load the corresponding vehicle identifier set based on the vehicle test location.

[0044] In this embodiment of the disclosure, the vehicle test location can be pre-set with testable vehicles. Each vehicle can be uniquely identified by a number, model, or other information, thereby forming a corresponding set of vehicle identifiers based on the testable vehicles at each test location. The testable vehicles can be located at or near the test location, or the terrain required for the test can match the simulated working environment of the test location, or there can be other associations between the vehicle and the test location. This embodiment of the disclosure does not impose specific limitations in these aspects.

[0045] In this embodiment, based on the obtained vehicle test location, a corresponding vehicle identifier set can be dynamically loaded. The vehicle identifier set includes the identifiers corresponding to the vehicles that can be tested at that test location, thus allowing testers to select the vehicle to be tested using the vehicle identifier set. During this process, there may be situations where none of the vehicles corresponding to the vehicle identifier set meet the testing requirements. In this case, the vehicle test location provided by the tester after adjustment can be obtained again, and then the vehicle identifier set corresponding to the adjusted vehicle test location can be dynamically loaded.

[0046] Step A3: In response to a vehicle selection instruction for a set of vehicle identifiers, determine the target vehicle identifier.

[0047] In the embodiments of the present disclosure, on the basis of dynamically loading the vehicle identification set, the tester can trigger a vehicle selection instruction on at least one vehicle identification in the vehicle identification set. In this process, the selected vehicle identification can be taken as a target vehicle identification in response to the vehicle selection instruction. The target vehicle identification corresponds to a target vehicle to be tested at the vehicle test site for the measured program version number.

[0048] Step A4, based on the vehicle test site, the measured program version number, and the target vehicle identification, a test session is created.

[0049] In the embodiments of the present disclosure, on the basis of determining the vehicle test site, the measured program version number, and the target vehicle identification, a corresponding test session can be created. The log entry under the test session is empty before the start of the current vehicle test, and is used to assist the tester in recording the test process of the aforementioned target vehicle. Among them, when the tester determines that the test environment metadata such as the vehicle test site, the measured program version number, and the target vehicle identification are correct by triggering the confirmation instruction, the test session corresponding to the current vehicle test can be created in response to the confirmation instruction.

[0050] In an optional method embodiment of the present disclosure, the session mode is a continuation session mode, and the aforementioned step 101 can include the following steps B1 to B2.

[0051] Step B1, in response to a vehicle test request, the historical log persisted in the historical record file is read.

[0052] In the embodiments of the present disclosure, in response to a vehicle test request established for a test session in a continuation session mode, the historical log persisted in the historical record file can be read. The continuation session mode can be for another vehicle test starting from the link where the previous vehicle test is interrupted. The historical record file can include at least the historical log generated from the start of the test to the link where the test is interrupted in the previous vehicle test, and the generation of the historical log can correspond to the description of the log entry in the aforementioned step 102. To avoid repetition, it will not be described here. Among them, the historical log can also include the test environment metadata such as the vehicle test site, the measured program version number, and the target vehicle identification determined in the aforementioned step A4.

[0053] In the embodiments of the present disclosure, the history record file can be specified in the vehicle test request, and the history log stored persistently in the history record file is read in response to the vehicle test request. The specification of the history record file can be achieved by providing the tester with the identification, naming, storage path, and the like of the history record file; the tester can be provided with a multi-level storage directory of the history record file, and the tester can specify the storage path by selecting the multi-level storage directory; or the tester can directly upload the history record file, and the embodiments of the present disclosure do not make specific limitations in this regard.

[0054] Step B2, a test session is created based on the history log, and the test session is marked as history record continuation.

[0055] In the embodiments of the present disclosure, the corresponding test session can be created based on the obtained history log. The log entries under the test session include the history log before the current vehicle test is started to be executed, and are used to assist the tester to record the test process of the target vehicle based on the history log. The test session can be marked as history record continuation, so as to be distinguished from the test session for recording the vehicle test process from the beginning.

[0056] In an optional method embodiment of the present disclosure, the log operation instruction is a standard operation record instruction, and the foregoing step 102 can include the following steps C1 to C3.

[0057] Step C1, in response to the log operation instruction, a system timestamp is obtained.

[0058] Step C2, a predefined operation description and a feedback result of the tested program are obtained for the vehicle test process.

[0059] Step C3, a log entry in a structured format is generated by combining the system timestamp, the operation description, and the feedback result of the tested program.

[0060] In this embodiment, the log operation instruction can be a standard operation recording instruction that instructs the recording of standard operations. A standard operation can correspond to a test event in the vehicle testing process where vehicle operations are tested without abnormalities. For example, if the vehicle starts normally, the start is determined to be a standard operation; if the vehicle shuts off normally, the shutdown is determined to be a standard operation. Based on this, recording standard operations allows for the structured organization of standard operation information to form log entries. The standard operation information can include a system timestamp to describe the time of the standard operation, predefined operation descriptions such as operation type, operation object, and operation process, and predefined feedback results from the tested program, such as a successful wake-up for a wake-up test, normal ignition for an ignition test, and a successful mode switching for a mode switching test. The aforementioned system timestamp can include timestamps corresponding to the start, end, and intermediate steps of the standard operation, and can also include timestamps corresponding to the triggering of the log operation instruction.

[0061] In this embodiment of the disclosure, based on the system timestamp, operation description, and feedback results from the program under test, the data can be organized according to a structured format to generate log entries corresponding to the standard operation. For example, the structured format of a standard operation record can be represented as follows: [System Timestamp] [Operation Description] --- [Feedback Result from the Tested Program].

[0062] In an optional embodiment of the method disclosed herein, the log operation instruction is an event recording instruction to be checked, and the aforementioned step 102 may include the following steps D1 to D3.

[0063] Step D1: In response to the log operation command, obtain the system timestamp.

[0064] Step D2: Obtain predefined standardized event descriptions for the events to be investigated in the vehicle testing process.

[0065] Step D3: Combine system timestamps, standardized event descriptions, and placeholders from analysis results to generate structured log entries.

[0066] In the embodiments of the present disclosure, the log operation instruction can be an event under investigation recording instruction indicating recording of an event under investigation. The event under investigation can correspond to a test event of vehicle operation in a vehicle test process and an abnormal event, such as a vehicle start failure, which is determined as an event under investigation, and a vehicle engine failure, which is determined as an event under investigation. On this basis, recording the event under investigation can structure the information of the event under investigation to form a log entry record. The information of the event under investigation can include a system timestamp to describe the time of the event under investigation, and can include a predefined standardized event description, such as operation type, operation object, operation process, feedback result, etc., such as wake-up test corresponding to wake-up failure, ignition test corresponding to ignition abnormality, mode switching test corresponding to switching failure, etc. The foregoing system timestamp can include timestamps corresponding to the start, end and intermediate steps of the event under investigation, and can also include timestamps corresponding to the triggering of the log operation instruction.

[0067] In the embodiments of the present disclosure, on the basis of obtaining the system timestamp and the standardized event description, the structured format can be used for organization to generate a log entry corresponding to the event under investigation. The structured format of the event under investigation recording instruction can also include an analysis result placeholder for further filling of abnormal phenomena or causes on the basis of subsequent abnormal problem analysis.

[0068] For example, the structured format of the event under investigation recording can be as follows: [system timestamp] [standardized event description] --- [analysis result placeholder].

[0069] In an optional method embodiment of the present disclosure, the log operation instruction is a process marker recording instruction, and the foregoing step 102 can include the following step E1 to step E2.

[0070] Step E1, in response to the log operation instruction, a system timestamp is obtained.

[0071] Step E2, a predefined process marker description is obtained for the vehicle test process, and a structured format log entry is generated; the process marker description includes at least one of a test stage marker and a test area identifier.

[0072] In an embodiment of the present disclosure, the log operation instruction can be a flow mark record instruction indicating to record a flow mark. The flow mark is used to divide the progress of a vehicle test, such as dividing steps, test stages, and test areas. The flow mark can be configured with a predefined flow mark description, such as a test stage mark describing different test stages in the vehicle test, and a test area description describing different test areas in a vehicle test site. The different test stages in the vehicle test and the different test areas in the vehicle test site can be divided according to test flow design, test environment deployment, test, and subsequent analysis requirements, and the present disclosure does not make further specific limitations. For example, the test area mark can include a loading area mark and an unloading area mark.

[0073] In an optional method embodiment of the present disclosure, the log operation instruction is an auxiliary mark record instruction, and the foregoing step 102 can include the following steps F1 to F2.

[0074] Step F1, in response to the log operation instruction, obtaining auxiliary description content in a structured format; the auxiliary description content includes at least one of a system timestamp and a predefined text segment.

[0075] Step F2, inserting the auxiliary description content in the log entry.

[0076] In an embodiment of the present disclosure, the log operation instruction can be an auxiliary mark record instruction indicating to record an auxiliary mark. The auxiliary mark can include custom auxiliary description content, which can be inserted in the log entry in response to the auxiliary mark record instruction. The auxiliary description content can include a system timestamp, and can also include other predefined text segments, such as a prompt text segment and a note text segment, and the present disclosure does not make further specific limitations.

[0077] In an optional method embodiment of the present disclosure, the log operation instruction is a record modification instruction, and the foregoing step 102 can include the following steps J1 to J2.

[0078] Step J1, in response to the log operation instruction, determining a corresponding log entry.

[0079] Step J2, performing a modification operation on the log entry in a structured format.

[0080] In an embodiment of the present disclosure, the log operation instruction can be a record modification instruction indicating to perform a modification operation on a log entry. The modification operation performed on the log entry can be a deletion, an update, or the like, such as deleting an entire log entry, deleting part of the description content, adding part of the description content, updating a system timestamp, and the like. The record modification instruction can trigger one or more log entries, and perform a modification operation on the log entry in a structured format.

[0081] In an alternative method embodiment of the present disclosure, the aforementioned step 103 can comprise steps K1 to K5.

[0082] Step K1, in response to the save instruction, all log entries are acquired.

[0083] In an embodiment of the present disclosure, the save instruction can be an instruction indicating the persistent storage of all log entries under the test session. All log entries in the new session mode can include all log entries operated at the time of triggering the save instruction, such as generated log entries, modified log entries, etc.; in the continuation session mode, it can include the historical logs read at the time of triggering the save instruction, and all log entries operated, such as generated log entries, modified log entries, etc. On this basis, all log entries are acquired for persistent storage.

[0084] Step K2, in the case of first triggering of the triggering time and new session mode of the session mode, a session record file is created in the preset path, and all log entries are written into the session record file for persistent storage.

[0085] In an embodiment of the present disclosure, the first triggering of the triggering time indicates that the save instruction corresponds to the first persistent storage instruction in the vehicle test process; on this basis, in the new session mode, a session record file corresponding to the test session can be created in the preset path for calling through the preset path. After creating the session record file, the log entries acquired in the aforementioned step K1 can be written into the session record file for persistent storage. The session record file can be named by a standardized format, such as a standard number, a timestamp, or a combination of other session metadata, such as test type, vehicle model, presence of an event to be investigated, etc.

[0086] Step K3, in the case of first triggering of the triggering time and continuation session mode of the session mode, all log entries are written into the historical record file for persistent storage.

[0087] In an embodiment of the present disclosure, the first triggering of the triggering time indicates that the save instruction corresponds to the first persistent storage instruction in the vehicle test process; on this basis, in the continuation session mode, the test session corresponds to the historical record file of the persistent storage of the previously interrupted vehicle test. Therefore, the historical record file can be called and emptied, and the log entries acquired in the aforementioned step K1 can be written into the historical record file for persistent storage.

[0088] Step K4, in the case of non-first triggering of the triggering time and new session mode of the session mode, all log entries are written into the session record file for persistent storage.

[0089] In the embodiment of the present disclosure, the trigger is actually a non-first trigger, indicating that the save instruction corresponds to the Nth time of persistent storage indication in the vehicle test process, and N is greater than 1; on this basis, in the new session mode, the session record file created at the preset path at the first trigger can be called and emptied, and the log entries obtained in the foregoing step K1 are overwritten and written into the session record file for persistent storage.

[0090] In the step K5, in the case that the trigger timing is a non-first trigger and the session mode is a continuous writing session mode, all the log entries are overwritten and written into the history record file for persistent storage.

[0091] In the embodiment of the present disclosure, the trigger is actually a non-first trigger, indicating that the save instruction corresponds to the Nth time of persistent storage indication in the vehicle test process, and N is greater than 1; on this basis, in the continuous writing session mode, the history record file created at the preset path at the first trigger can be called and emptied, and the log entries obtained in the foregoing step K1 are overwritten and written into the history record file for persistent storage.

[0092] In an optional method embodiment of the present disclosure, the foregoing step 102 can include the following step L1 after the step 102.

[0093] In the step L1, a modification flag bit is set at the position of the log entry on which the operation occurs.

[0094] In the embodiment of the present disclosure, on the basis of generating, modifying and other operations on the log entries in response to the log operation instruction, a modification flag can also be set at the position of the log entry on which the operation occurs. The modification flag is used to monitor the content change of the log entry, so as to avoid possible omissions and realize data security and protection.

[0095] In an optional method embodiment of the present disclosure, on the basis of the foregoing step L1, the foregoing step 103 can include the following step L2 after the step 103.

[0096] In the step L2, the modification flag bit is reset.

[0097] In the embodiment of the present disclosure, on the basis of the foregoing step L1, after all the log entries are stored persistently in response to the save instruction, the modification flag bit can also be reset, indicating that the content change of the log entry before the trigger timing of the save instruction has been saved, so as to avoid redundant marking information.

[0098] Figure 2 The second step flow chart of the vehicle test auxiliary method provided in the embodiment of the present disclosure is based on a vehicle test application, and the step flow of the method can be as shown in the following steps 201 to 205: Step 201, in response to an application start event, performing a singleton check on shared memory for a vehicle test application.

[0099] In the embodiments of the present disclosure, the vehicle test auxiliary method can be implemented through the developed vehicle test application, and the vehicle test application can include different functional components to trigger corresponding requests and instructions in the interaction with the test personnel, and then perform data generation, modification and other operations, as well as file creation, calling, reading, writing and other operations in response to the requests and instructions. In order to avoid data conflicts, there should be only one application instance of the vehicle test application at a time for a vehicle test, and a test session is running at a time. The start of the vehicle test application depends on the creation of shared memory, and on this basis, in response to the application start event of the vehicle test application, a singleton check can be performed on the shared memory. If the shared memory already exists, it means that the singleton check fails, at which time the existing application instance can be prompted to exit or close the existing application instance; if the shared memory does not exist, it means that the singleton check passes.

[0100] Step 202, when the singleton check passes, creating shared memory corresponding to the vehicle test application.

[0101] In the embodiments of the present disclosure, when the singleton check passes, the conventional vehicle test application start process is performed, the shared memory corresponding to the vehicle test application is created, and the interaction items triggered by different requests, instructions and the like are provided.

[0102] Step 203, in response to a vehicle test request, establishing a corresponding test session based on a selected session mode; the session mode includes at least one of a new session mode and a continuation session mode.

[0103] In the embodiments of the present disclosure, step 203 can correspond to the related description of the foregoing step 101, and to avoid repetition, will not be repeated here.

[0104] Step 204, in response to a log operation instruction, operating the log entry based on a structured format corresponding to the log operation instruction.

[0105] In the embodiments of the present disclosure, step 204 can correspond to the related description of the foregoing step 102, and to avoid repetition, will not be repeated here.

[0106] Step 205, in response to a save instruction, persistently storing all log entries based on a triggering time and a session mode.

[0107] In the embodiments of the present disclosure, step 205 can correspond to the related description of the foregoing step 103, and to avoid repetition, will not be repeated here.

[0108] In an optional method embodiment of the present disclosure, based on the foregoing steps L1 and L2, when the method is implemented based on a vehicle test application, the method can further include the following steps M1 to M2.

[0109] Step M1, in response to the application closing event, check the modification flag.

[0110] Step M2, in the presence of the modification flag, prompt the presence of unsaved log entries.

[0111] In the embodiments of the present disclosure, when the application closing event is triggered, the modification flag can be checked first. In the presence of the modification flag, it indicates that there are log entries that have been operated but not saved. At this time, directly closing the application may cause data loss or damage, and the test personnel can be prompted that there are unsaved log entries. In an optional method embodiment of the present disclosure, an interactive item for saving instructions can also be provided to improve data security.

[0112] The vehicle test auxiliary method provided by the present disclosure can respond to a vehicle test request and establish a corresponding test session based on a selected session mode when the vehicle test starts, where the session mode can include a new session mode, a continuation session mode, etc. On this basis, during the vehicle test, log entries can be operated based on a corresponding structured format in response to a log operation instruction. Further, in response to a save instruction, all log entries can be persistently stored based on a trigger timing and a session mode when the vehicle test ends. The method can improve the efficiency of vehicle test process recording and reduce the recording error rate. On this basis, the vehicle test process recording is implemented in a standardized and structured format, which is convenient for subsequent reading and analysis, and can also realize centralized and continuous recording, which is convenient for tracing and reproduction, thereby better supporting vehicle design, production, distribution and maintenance.

[0113] The embodiments of the present disclosure also provide a vehicle test auxiliary system, which is used to implement the vehicle test auxiliary method of any one of the foregoing Figures 1 to 2 The embodiments of the present disclosure also provide a vehicle test auxiliary system, which is used to implement the vehicle test auxiliary method of any one of the foregoing

[0114] In the embodiments of the present disclosure, in the scenario where a test personnel performs a vehicle test, the vehicle test auxiliary system can provide a display interface for interaction to the test personnel. The display interface can provide predefined functional components, so as to trigger a corresponding request, instruction, etc. when the test personnel selects a corresponding functional component, and then execute a corresponding test auxiliary function in response to the request, instruction, etc.

[0115] For example, a vehicle test application developed based on the Qt framework (a cross-platform application development framework) is taken as an example. The vehicle test application is implemented based on a desktop application developed based on the Qt framework, and the vehicle test auxiliary process can be as shown in the following steps N1 to NX. Step N1: In response to the application startup event, perform a singleton check on the shared memory. If the singleton check fails, a warning will pop up and the application will exit; if the singleton check passes, a QSharedMemory object will be created in the main function, and a preview interface will be displayed on the display screen.

[0116] In this embodiment of the disclosure, the preview interface may be a display interface provided by a vehicle testing application that receives vehicle testing requests to create a test session. Figure 3 One of the schematic diagrams of the display interface provided by a vehicle testing assistance system is provided, such as... Figure 3 As shown, the preview interface includes three input boxes: "Test Location", "Test Vehicle", and "Test Version", as well as two interactive items: "OK" and "Open History File".

[0117] Step N2: After obtaining the test location (test site of Mine No. 2) inputted by the tester through the "Test Location" input box, the target vehicle identifier (58#) selected by the tester from the dynamically loaded vehicle identifier set [15#, 16#...90#] through the "Test Vehicle" input box, and the version number of the program under test (V2.5.0) input by the tester through the "Test Version" input box, in response to the tester's click operation on the "OK" interaction item, the aforementioned test environment metadata is sent to MainWindow via the signal sendValue_mainwindow and displayed on the display interface. At the same time, the session flag Flag_NewOrOldFile = 1 (new file) is set to create a test session in the new session mode.

[0118] Alternatively, in step N3, in response to the tester's click on the "Open History File" interactive item, the corresponding history file "2024-05-27 14_30 testlog.txt" is called, the history log is read, and sent to the MainWindow interface via the signal sendValue_preview_localFileContent and displayed on the display interface. At the same time, the session flag Flag_NewOrOldFile = 2 (old file) is set, and the file storage path LocalFilePath of the history file is recorded.

[0119] Figure 4 A second schematic diagram of the display interface provided by a vehicle testing assistance system is provided, such as... Figure 4As shown, the display interface includes a log area (textEdit_Show) 410 and a function area 420. The log area 410 can display the test environment metadata and log entries corresponding to the current vehicle test. The test environment metadata can be obtained by test personnel input or selection in the new session mode, and can be obtained by reading the historical log in the continuation session mode. The function area 420 can include interactive items corresponding to different functional components, corresponding to triggering instructions, requests, events, etc. For example, the "background wake-up", "background sleep", "background ignition", "background engine off", "start", "stop", "parking", "start", "switch to self-driving", "switch to manual" and other interactive items corresponding to the standard operation recording instruction; "abnormal parking", "start without moving", "moving and stopping", "accelerator intermittent", and other abnormal states, and "obstacle parking", "deviation parking", "level 3 fault parking", "level 4 fault parking" and other parking types corresponding to the event to be checked recording instruction; "full process test", "obstacle parking test" and other starting stages of basic tests corresponding to the process marker recording instruction, "loading area", "unloading area", "empty main road", "heavy load main road", "start main road", "parking lot" and other area selection; "time" interactive item corresponding to the auxiliary recording marker instruction, used to obtain the system timestamp as auxiliary description content inserted into the log entry; "save local" interactive item corresponding to the save instruction, used to persistently store the log entry.

[0120] On this basis, other functional interactive items can also be included. For example, for the basic operation of the vehicle, it can include the "replace test program" interactive item for replacing the version number of the tested program, the "restart system" interactive item for restarting the test program of the vehicle, and the "issue task" interactive item for issuing a task to the vehicle, the "watering" interactive item for instructing the vehicle to perform the watering work, and the like; there are also test items for the tested program to instruct the vehicle to perform the function corresponding to the tested program for testing, such as test item 1, test item 2, …, test item 9, and the like. As shown in the display interface, as follows: Figure 4 Step N4, in response to the test personnel clicking the "background start" interactive item on the MainWindow interface, the vehicle test application executes the slot function on_pushButton_StartCmd_clicked(), generates the log entry "17:19:22 issue start instruction --- vehicle start", and appends and displays it in the log area 410.

[0121] ​Step N5, during the vehicle test, the vehicle suddenly stops in operation, in response to the test personnel clicking the "third level failure stop" interactive item on the MainWindow interface, the vehicle test application executes on_pushButton_ThirdLevelStop_clicked(), and generates a log entry "14:36:15 vehicle third level failure---failure reason: []". Among them, "failure reason: []" represents the analysis result to be filled in. For example, the test personnel inputs the investigation result "sensor X communication timeout" for the vehicle third level failure in the analysis result placeholder corresponding to the log entry.

[0122] Step N6, during the vehicle test, the vehicle enters the loading area, in response to the test personnel clicking the "loading area" interactive item on the MainWindow interface, the vehicle test application executes on_pushButton_LA_clicked(), and inserts the text "loading area" in the log entry to mark the current test area.

[0123] Step N7, during the vehicle test, in response to the test personnel clicking the "save" interactive item on the MainWindow interface for the first time, the vehicle test application checks that Flag_NewOrOldFile = 1 (new file) and Flag_CreatedFile = 1 (not created), then creates the session record file 2024-05-27 14_35testlog.txt under the preset path of / home, writes all the log entries in the log area 410, and sets Flag_CreatedFile = 2 (created) and isModified = false (saved).

[0124] Step N8, during the vehicle test, in response to the test personnel clicking the "save" interactive item on the MainWindow interface for the first time, the vehicle test application checks that Flag_NewOrOldFile = 2 (old file), then empties the history record file 2024-05-27 14_30testlog.txt, and writes all the log entries in the log area 410 again.

[0125] In an optional embodiment of the present disclosure, in the case of successful persistent storage, a dialog box can also be popped up to prompt the test personnel that the log entry has been appended to the corresponding session record file or history record file, so as to enable the test personnel to confirm the data saving progress.

[0126] Step N9, in response to the application close event (closeEvent) triggered by the tester closing the MainWindow interface, the vehicle test system checks the modified flag bit isModified = true (unsaved), and then prompts the tester with a pop-up dialog box: "The document has unsaved changes, do you want to save it?". The dialog box can include a "Save" interactive item for automatically executing the aforementioned save logic of steps N7 or N8 and then safely closing the vehicle test application when the tester clicks it; it can also include a "Don't save" interactive item for directly closing the vehicle test application when the tester clicks it; and it can also include a "Cancel" interactive item for canceling the application close event when the tester clicks it.

[0127] Figure 5 A content display diagram of a session log file is provided, as shown in Figure 5 The session log file generated by the vehicle test auxiliary system includes a function bar 510 and a display area 520 in the display interface. The function bar 510 includes the naming of the session log file "2024-05-27 14_35 testlog.txt", and "row" and "column" displays, interactive item 511, minimized interactive item 512, maximized interactive item 513, and interactive item 514 for closing the file display, etc. The display area 520 displays the saved log entries as follows: 1 2024-05-27 14_35 testlog.txt; 2 Test site: No. 2 mine test site; 3 Test vehicle: 58#; 4 Test version: V2.5.0; 5 17:18:46 Background wake-up - wake-up successful; 6 17:18:47 Issue ignition instruction - normal ignition; 7 17:19:20 Switch to self-driving mode - switch successful; 8 17:19:22 Issue start instruction - vehicle starts (loading area); 9 17:19:28 Obstacle parking; 10 17:19:31 Switch to manual mode - switch successful; 11 17:19:36 Switch to self-driving mode - switch successful; 12 17:19:37 Switch to manual and then back to self-driving; 13 17:19:55 Task update (update type 1); 14 17:19:58 Start test item 7; 15 17:20:05 Issuance of vehicle closure instruction ------- Vehicles enter the main closure road.

[0128] This disclosure provides a vehicle testing assistance system. In response to a vehicle testing request, the system establishes a corresponding test session at the start of the test based on a selected session mode, which may include a new session mode, a continuation session mode, etc. During the vehicle testing process, it can respond to log operation commands and manipulate log entries based on a corresponding structured format. Furthermore, in response to a save command, it can persistently store all log entries at the end of the test based on the trigger timing and session mode. This system improves the efficiency of vehicle testing process recording and reduces the recording error rate. Furthermore, the vehicle testing process recording is implemented in a standardized and structured format, facilitating subsequent reading and analysis. It also enables centralized and continuous recording, facilitating traceability and reproducibility, thereby better supporting vehicle design, production, allocation, and maintenance.

[0129] It should be noted that although several modules or units for the device used to perform actions have been mentioned in the detailed description above, this division is not mandatory. In fact, according to embodiments of this disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0130] Furthermore, although the steps of the method in this disclosure are described in a specific order in the accompanying drawings, this does not require or imply that the steps must be performed in that specific order, or that all the steps shown must be performed to achieve the desired result. Additional or alternative steps may be omitted, multiple steps may be combined into one step, and / or a step may be broken down into multiple steps.

[0131] From the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of this disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, server, mobile terminal, or network device, etc.) to execute the methods according to the embodiments of this disclosure.

[0132] In an exemplary embodiment of this disclosure, an electronic device capable of implementing the above-described method is also provided.

[0133] Those skilled in the art can understand that each aspect of the present disclosure can be implemented as a system, a method or a program product. Therefore, each aspect of the present disclosure can be embodied in a form of entirely hardware, entirely software (including firmware, microcode, etc.), or a combination of hardware and software, which can be collectively referred to as "circuitry", "module" or "system".

[0134] The electronic device 600 according to this embodiment of the present disclosure will be described below with reference to Figure 6 Figure 6 The electronic device 600 is merely an example and should not impose any limitation on the function and scope of use of the embodiments of the present disclosure.

[0135] As shown in Figure 6 The electronic device 600 is in the form of a general computing device. The components of the electronic device 600 can include, but are not limited to, the at least one processing unit 610 described above, the at least one storage unit 620 described above, and a bus 630 connecting different system components, including the storage unit 620 and the processing unit 610.

[0136] The storage unit stores program codes which can be executed by the processing unit 610, so that the processing unit 610 performs the steps according to various exemplary embodiments of the present disclosure described in the "Exemplary Method" section of the present specification.

[0137] The storage unit 620 can include a readable medium in the form of a volatile storage unit, such as a random access memory (RAM) 6201 and / or a cache memory unit 6202, and can further include a read-only memory (ROM) 6203.

[0138] The storage unit 620 can further include a program / utility 6204 having a set of program modules 6205, including but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which can include implementation of a network environment, alone or in combination.

[0139] The bus 630 can represent one or more of several types of bus structures, including a storage unit bus or storage unit controller, a peripheral bus, a graphics acceleration port, a processing unit bus, or a local bus using any of a variety of bus architectures.

[0140] ​The electronic device 600 can also communicate with one or more external devices such as a keyboard or a pointing device, through the I / O interface 650 and the display unit 640. Furthermore, the electronic device 600 can communicate with one or more devices that enable a user to interact with the electronic device 600, and / or one or more devices that enable the electronic device 600 to communicate with one or more other computing devices. Such communication can occur via the display unit 640 and the I / O interface 650. Still yet, the electronic device 600 can communicate with one or more networks (such as a local area network (LAN), a wide area network (WAN), and / or the Internet) through the network adapter 660. As depicted, the network adapter 660 communicates with the other components of the electronic device 600 via the bus 630. It should be appreciated that the electronic device 600 can be a part of a larger system, including but not limited to a distributed computing environment, a grid computing environment, a mobile computing environment, or any other system in which electronic devices are coupled to a network.

[0141] Those skilled in the art will readily understand that the example embodiments described herein can be implemented by software and / or by hardware coupled with software, as described above. Thus, the technical solutions according to the embodiments of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, a USB flash disk, a mobile hard disk, or the like) or a network, and includes a number of instructions to enable a computing device (such as a personal computer, a server, a terminal device, or a network device, etc.) to perform the methods according to the embodiments of the present disclosure.

[0142] In the example embodiments of the present disclosure, a computer-readable storage medium having stored thereon a program product capable of implementing the above-described methods of the present disclosure is also provided. In some possible embodiments, various aspects of the present disclosure can also be implemented in the form of a program product, which includes program codes for causing an end device to perform the steps described in the above-mentioned “example method” section according to various example embodiments of the present disclosure when the program product is run on the end device.

[0143] In the embodiments of the present disclosure, a program product for implementing the above-described methods is also provided, which can take the form of a portable compact disc read-only memory (CD-ROM) and include program codes, and can be run on an end device, such as a personal computer. However, the program product of the present disclosure is not limited to this, and in this document, a readable storage medium can be any tangible medium containing or storing a program, which can be used by or in conjunction with an instruction execution system, device, or apparatus.

[0144] A program product can take any combination of one or more computer-readable media. The computer-readable media can be a computer-readable storage medium or a computer-readable signal medium. The computer-readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the above. More specific examples (a non-exhaustive list) of the computer-readable storage medium include an electrical connection having one or more wires, a portable disc, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0145] The computer-readable signal medium can include a computer-readable storage medium that is propagated as a carrier wave in a baseband or propagated as part of a propagated data signal in a carrier, such as a propagated signal. The propagated signal can take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer-readable signal medium can be any computer-readable medium that is not a computer-readable storage medium and that can communicate, propagate, or transport programming for use by or in connection with an instruction execution system, apparatus, or device.

[0146] The program code embodied on the computer-readable media can be transmitted using any appropriate medium, including but not limited to wireless, wired, optical fiber cable, RF, etc., or any suitable combination of the above.

[0147] Program code used to carry out operations of the present disclosure can be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++, or the like, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code can execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's device and partly on a remote computing device or entirely on the remote computing device or server. In the latter scenario, the remote computing device can be connected to the user's device through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computing device, such as through the Internet using an Internet Service Provider. The present disclosure can be implemented in a computing system that includes a back-end component, or a middleware component, or a front-end component, or any combination of the three, or a client-side component, or a server-side component, or a component of another computing system that is explicitly identified herein.

[0148] In addition, the above-described flowcharts are merely illustrative examples of the processes included in the method according to the exemplary embodiments of the present disclosure, and are not intended to limit the present disclosure. It is readily understood that the processes shown in the above-described flowcharts do not indicate or limit the time sequence of the processes. In addition, it is readily understood that the processes can be executed synchronously or asynchronously, for example, in a plurality of modules.

[0149] Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the features disclosed herein. It is intended that the disclosure be construed as including any variations, uses, or adaptations of the specific embodiments following, including equivalents thereof, which are within the scope of the disclosure and including such as come within the general scope of the following claims. The specification and examples given are only intended to be exemplary and are not intended to limit the true scope and spirit of the disclosure.

Claims

1. A vehicle testing assistance method, characterized in that, The method includes: In response to a vehicle test request, a corresponding test session is established based on the selected session mode; the session mode includes at least one of a new session mode and a continuation session mode. In response to log operation instructions, operations are performed on log entries based on the structured format corresponding to the log operation instructions; In response to the save command, all the log entries are persistently stored based on the triggering time and the session mode.

2. The method according to claim 1, characterized in that, The session mode is a new session mode. The step of responding to a vehicle test request and establishing a corresponding test session based on the selected session mode includes: In response to a vehicle testing request, obtain the vehicle testing location and the version number of the program under test; Dynamically load the corresponding vehicle identifier set based on the vehicle test location; In response to a vehicle selection instruction for the set of vehicle identifiers, a target vehicle identifier is determined; The test session is created based on the vehicle test location, the version number of the program under test, and the target vehicle identifier.

3. The method according to claim 1, characterized in that, The session mode is a continuation session mode. The step of responding to a vehicle test request and establishing a corresponding test session based on the selected session mode includes: In response to a vehicle test request, read the historical logs persistently stored in the history file; The test session is created using the historical logs, and the test session is marked as a history continuation.

4. The method according to claim 1, characterized in that, The log operation command is a standard operation recording command. The operation on log entries in response to the log operation command, based on the structured format corresponding to the log operation command, includes: In response to log operation commands, obtain the system timestamp; For vehicle testing processes, obtain predefined operation descriptions and feedback results from the tested program; A structured log entry is generated by combining the system timestamp, the operation description, and the feedback result from the program under test.

5. The method according to claim 1, characterized in that, The log operation instruction is an instruction for recording an event to be queried. The step of responding to the log operation instruction and operating on the log entry based on the structured format corresponding to the log operation instruction includes: In response to log operation commands, obtain the system timestamp; Obtain predefined standardized event descriptions for events to be investigated in the vehicle testing process; The system timestamp, the standardized event description, and the analysis results placeholders are combined to generate structured log entries.

6. The method according to claim 1, characterized in that, The log operation instruction is a process marking and recording instruction. The operation on log entries in response to the log operation instruction, based on the structured format corresponding to the instruction, includes: In response to log operation commands, obtain the system timestamp; For the vehicle testing process, a predefined process tag description is obtained, and a structured log entry is generated; the process tag description includes at least one of test phase tag and test area identifier.

7. The method according to claim 1, characterized in that, The log operation instruction is an auxiliary marking and recording instruction. The operation on log entries in response to the log operation instruction, based on the structured format corresponding to the log operation instruction, includes: In response to a log operation command, obtain structured auxiliary description content; the auxiliary description content includes at least one of a system timestamp and a predefined text fragment. Insert the auxiliary description content into the log entry.

8. The method according to claim 1, characterized in that, The log operation instruction is a record modification instruction. The step of responding to the log operation instruction and operating on the log entry based on the structured format corresponding to the log operation instruction includes: In response to a log operation command, determine the corresponding log entry; Modification operations are performed on the log entries in a structured format.

9. The method according to claim 1, characterized in that, In response to the save command, based on the triggering timing and the session mode, all log entries are persistently stored, including: In response to the save command, retrieve all the log entries; When the triggering time is the first triggering and the session mode is the newly created session mode, a session log file is created in a preset path, and all the log entries are written to the session log file for persistent storage. If the triggering time is the first triggering and the session mode is the continuation session mode, all the log entries are written to the history file for persistent storage. If the triggering time is not the first triggering and the session mode is the newly created session mode, all the log entries are written to the session record file for persistent storage. If the triggering time is not the first triggering and the session mode is the continuation session mode, all the log entries are overwritten and persistently stored in the history file.

10. The method according to any one of claims 1 to 9, characterized in that, The method is implemented based on a vehicle testing application; the method also includes: In response to the application launch event, a singleton check of shared memory is performed on the vehicle test application; When the singleton check passes, the shared memory corresponding to the vehicle test application is created.

11. The method according to any one of claims 1 to 9, characterized in that, After operating on the log entries based on the structured format corresponding to the log operation instructions, the process further includes: Set the modification flag at the location of the log entry where the operation occurred; Furthermore, after persistently storing all the log entries, the process further includes: Reset the modified flag.

12. The method according to claim 11, characterized in that, The method is implemented based on a vehicle testing application; the method also includes: In response to an application close event, check the modified flag bit; If the modified flag is present, a message will be displayed indicating that there are unsaved log entries.

13. A vehicle testing assistance system, characterized in that, The system is used to implement the vehicle testing assistance method according to any one of claims 1 to 12.

Images