Vehicle-mounted software testing method and device, vehicle and storage medium
By collecting and marking videos, logs and resource information during the on-board software testing process, and generating target test files, the data dependence problem in on-board software testing is solved, the testing efficiency and accuracy are improved, and the stability of the vehicle cockpit function is ensured.
Patent Information
- Application Number
- CN202411216397.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-30
- Publication Date
- 2024-12-06
AI Technical Summary
The lack of detailed data basis in existing on-board software testing, which makes it difficult to reproduce problems efficiently and quickly, affecting the stability and accuracy of the vehicle cockpit function.
By collecting the operation video information of the tester, log information and resource information of the on-board software, and performing positioning and annotation, target test files are generated to achieve efficient positioning and verification of the on-board software test results.
It improves the convenience and accuracy of on-board software verification, realizes efficient backtracking of test problems, and solves the problem of inefficient testing caused by relying on manual inspection in the existing technology.
Smart Images

Figure CN119088706A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of vehicle testing technology, and in particular to a method, device, vehicle and storage medium for testing vehicle-mounted software. Background Art
[0002] As vehicle cockpit functions continue to increase, in-vehicle software applications also become more diverse. Before in-vehicle software is launched on the market, it is necessary to verify it in a large number of complex scenarios to ensure the normal performance of the vehicle's cockpit functions during actual vehicle applications.
[0003] In the related technologies, there are occasional problems, complex link problems and problems caused by insufficient system performance during the vehicle software verification process. In order to discover and verify the above problems, R&D and testing personnel often repeat tests through a large number of operation reproduction methods.
[0004] However, in the relevant technologies, the existing vehicle-mounted software problem reproduction lacks detailed data basis and often relies on manual inspection to trace the problem, which makes it difficult to achieve efficient and fast vehicle-mounted software testing, affecting the stability and accuracy of the vehicle's cockpit functions, and urgently needs to be solved. Summary of the invention
[0005] The present application provides a vehicle-mounted software testing method, device, vehicle and storage medium to solve the problems in the related technology that the existing vehicle-mounted software problem reproduction lacks detailed data basis, often relies on manual inspection to trace the problem, and it is difficult to achieve efficient and fast vehicle-mounted software testing, which affects the stability and accuracy of the vehicle's cockpit functions.
[0006] The first aspect of the present application provides a method for testing vehicle-mounted software, comprising the following steps: receiving a current test task of the vehicle-mounted software, and determining whether a tester has turned on a preset monitoring mode; when the tester has turned on the preset monitoring mode, collecting video information of the tester during the execution of the current test task, and obtaining log information and resource information of the vehicle-mounted software during the execution of the current test task; locating and annotating the video information, the log information and the resource information to obtain annotated test information, and generating a target test file for the vehicle-mounted software under the current test task based on the annotated test information, so as to obtain the test result of the vehicle-mounted software using the target test file.
[0007] Optionally, in one embodiment of the present application, obtaining the log information and resource information of the vehicle-mounted software during the execution of the current test task includes: matching at least one target application of the vehicle-mounted software based on the current test task; extracting historical log records of the at least one target application during the execution of the current test task to generate the log information based on the historical log records.
[0008] Optionally, in one embodiment of the present application, obtaining the log information and resource information of the vehicle-mounted software during the execution of the current test task includes: confirming at least one performance indicator of the vehicle-mounted software based on the current test task; collecting the total load data and memory data of the vehicle-mounted software based on the at least one performance indicator, and obtaining the resource information from the total load data and the memory data.
[0009] Optionally, in one embodiment of the present application, the locating and marking the video information, the log information and the resource information includes: dividing the video information, the log information and the resource information based on preset time intervals to obtain multiple information subsets; locating and marking each information subset based on the timestamp of each information subset in the multiple information subsets, and obtaining the marked test information from the marked information subset.
[0010] Optionally, in one embodiment of the present application, the positioning and marking of each information subset is performed based on the timestamp of each information subset among the multiple information subsets, including: among all information subsets, extracting at least one collaborative information subset that is within a preset floating duration of the timestamp of the current information subset; confirming the collaborative group based on the timestamp of the current information subset, and adding a positioning identifier corresponding to the collaborative group to the at least one collaborative information subset and the current information subset, respectively.
[0011] A second aspect of the present application provides a vehicle-mounted software testing device, including: a judgment module, for receiving a current test task of the vehicle-mounted software, and judging whether a tester turns on a preset monitoring mode;
[0012] An acquisition module, used for collecting video information of the tester in the process of executing the current test task when the tester turns on the preset monitoring mode, and obtaining log information and resource information of the vehicle-mounted software in the process of running the current test task;
[0013] A testing module is used to locate and annotate the video information, the log information and the resource information to obtain annotated test information, and to generate a target test file for the vehicle-mounted software under the current test task based on the annotated test information, so as to obtain the test result of the vehicle-mounted software using the target test file.
[0014] Optionally, in one embodiment of the present application, the acquisition module includes: a matching unit, used to match at least one target application of the vehicle-mounted software based on the current test task; and a generation unit, used to extract historical log records of the at least one target application during the execution of the current test task, so as to generate the log information based on the historical log records.
[0015] Optionally, in one embodiment of the present application, the acquisition module includes: a confirmation unit, used to confirm at least one performance indicator of the vehicle-mounted software based on the current test task; and a collection unit, used to collect total load data and memory data of the vehicle-mounted software based on the at least one performance indicator, and obtain the resource information from the total load data and the memory data.
[0016] Optionally, in one embodiment of the present application, the test module includes: a division unit, used to divide the video information, the log information and the resource information based on a preset time interval to obtain multiple information subsets; a labeling unit, used to locate and label each information subset based on the timestamp of each information subset in the multiple information subsets, and obtain the labeled test information from the labeled information subset.
[0017] Optionally, in one embodiment of the present application, the labeling unit is specifically used to: extract at least one collaborative information subset that is within a preset floating duration of the timestamp of the current information subset from all information subsets; confirm the collaborative group based on the timestamp of the current information subset, and add a positioning identifier corresponding to the collaborative group to the at least one collaborative information subset and the current information subset, respectively.
[0018] A third aspect of the present application provides a vehicle, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the vehicle software testing method as described in the above embodiment.
[0019] The fourth aspect of the present application provides a computer-readable storage medium, which stores a computer program that, when executed by a processor, implements the above-mentioned vehicle-mounted software testing method.
[0020] The fifth aspect of the present application provides a computer program, which implements the above-mentioned vehicle-mounted software testing method when executed.
[0021] The embodiment of the present application can collect and integrate the tester's operating actions and software log and memory resource information during the vehicle software testing process to achieve efficient positioning of test problem backtracking, improve the convenience and accuracy of vehicle software verification, and be more practical. Thus, it solves the problems in the related technology that the existing vehicle software problem reproduction lacks detailed data basis, often relies on manual inspection for problem backtracking, and is difficult to achieve efficient and fast vehicle software testing, which affects the stability and accuracy of the vehicle cockpit function.
[0022] Additional aspects and advantages of the present application will be given in part in the description below, and in part will become apparent from the description below, or will be learned through the practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS
[0023] The above and / or additional aspects and advantages of the present application will become apparent and easily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:
[0024] Figure 1 A flowchart of a method for testing vehicle-mounted software provided according to an embodiment of the present application;
[0025] Figure 2 A schematic diagram of a video acquisition principle according to an embodiment of the present application;
[0026] Figure 3 A schematic diagram of the principle of data stream collection in vehicle-mounted software testing according to an embodiment of the present application;
[0027] Figure 4 Schematic diagram of the structure of a vehicle software testing device according to an embodiment of the present application;
[0028] Figure 5 It is a schematic diagram of the structure of a vehicle according to an embodiment of the present application. DETAILED DESCRIPTION
[0029] Embodiments of the present application are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present application, and should not be construed as limiting the present application.
[0030] The following describes the vehicle software testing method, device, vehicle and storage medium of the embodiment of the present application with reference to the accompanying drawings. In view of the problem that the existing vehicle software problem reproduction in the related technology mentioned in the above background technology lacks detailed data basis, often relies on manual inspection for problem backtracing, and is difficult to achieve efficient and fast vehicle software testing, which affects the stability and accuracy of the vehicle cockpit function, the present application provides a vehicle software testing method, in which the tester's operating actions and software logs and memory resource information can be collected and integrated during the vehicle software testing process to achieve efficient positioning of test problem backtracing, improve the convenience and accuracy of vehicle software verification, and be more practical. As a result, the problem that the existing vehicle software problem reproduction in the related technology lacks detailed data basis, often relies on manual inspection for problem backtracing, and is difficult to achieve efficient and fast vehicle software testing, which affects the stability and accuracy of the vehicle cockpit function, is solved.
[0031] Specifically, Figure 1 A flowchart of a method for testing vehicle-mounted software provided in an embodiment of the present application.
[0032] like Figure 1 As shown, the vehicle software testing method includes the following steps:
[0033] In step S101, the current test task of the vehicle-mounted software is received, and it is determined whether the tester turns on the preset monitoring mode.
[0034] It should be noted that the preset monitoring mode can be set by those skilled in the art according to actual conditions and is not specifically limited here.
[0035] It is understood that in the embodiment of the present application, the preset monitoring mode may be a state where the tester's length test operation is in video recording, and the log and system performance of the vehicle software are enabled for monitoring. Figure 2 As shown, it is a schematic diagram of the video acquisition principle of an embodiment of the present application, component 1 represents the adsorption-type mobile phone holder and the mobile phone, component 2 represents the central control host screen, and the mobile phone holder can be used to fix the mobile phone on the top of the car, and the angle of the holder can be adjusted according to the different layouts of the vehicle to shoot and record the smart cockpit central control screen, and the video can be transmitted to the smart cockpit central control monitoring program.
[0036] Among them, the vehicle software testing tasks can be implemented through the test platform. Testers can create test tasks on the platform and specify the software functions that need to be tested. The test tasks can include various application scenarios of vehicle software,
[0037] In step S102, when the tester turns on the preset monitoring mode, video information of the tester in the process of executing the current test task is collected, and log information and resource information of the vehicle-mounted software in the process of running the current test task is obtained.
[0038] It is understandable that in the embodiments of the present application, the video information of the tester during the execution of the current test task can be obtained by installing multiple cameras inside the test vehicle. The cameras cover the perspectives of the driver, the front, the side and the rear of the vehicle, etc., and are used to record the tester's operating behavior and the environmental conditions around the vehicle. The log information can be the log information generated by the vehicle-mounted software during operation, including the software's operating status, error information, warning information, etc., and the log information can be automatically collected through the smart cockpit central control host monitoring application. The resource information can be the use of system resources such as CPU, memory, storage space, etc. by the vehicle-mounted software during operation. The smart cockpit central control host monitoring application can automatically execute CPU and memory monitoring commands to collect resource performance information.
[0039] Optionally, in one embodiment of the present application, log information and resource information of the vehicle-mounted software during the execution of the current test task are obtained, including: matching at least one target application of the vehicle-mounted software based on the current test task; extracting historical log records of at least one target application during the execution of the current test task to generate log information based on the historical log records.
[0040] During the actual execution process, we can first identify the target vehicle software application related to the current test task, and then extract the historical log records of the target application during the execution of the current test task. Through the log management system, we can extract the entries related to the target application from the log file of the vehicle software. Through the log analysis tool, we can parse the log records and extract key data to generate log information about the behavior of the vehicle software.
[0041] Optionally, in one embodiment of the present application, log information and resource information of the vehicle-mounted software during the execution of the current test task are obtained, including: confirming at least one performance indicator of the vehicle-mounted software based on the current test task; collecting total load data and memory data of the vehicle-mounted software based on at least one performance indicator, and obtaining resource information from the total load data and memory data.
[0042] In the actual execution process, at least one performance indicator of the vehicle software is used as a key parameter to measure the performance of the vehicle software, which may include the software's response time, processing speed, throughput, error rate, etc. The total load data and memory data of the software system environment can be specifically extracted according to the requirements of different performance indicators, wherein the total load data can be the overall workload borne by the vehicle software during operation, and the memory data can be the memory usage during the software operation process, so as to finally obtain resource information.
[0043] In step S103, the video information, log information and resource information are located and annotated to obtain annotated test information, and a target test file of the vehicle-mounted software under the current test task is generated based on the annotated test information, so as to obtain the test result of the vehicle-mounted software using the target test file.
[0044] It is understandable that in an embodiment of the present application, the annotation of the collected video information, log information, and resource information may include timestamps, event descriptions, exception markers, performance indicators, and other information to facilitate subsequent analysis and testing. By annotating the test information, a target test file for the vehicle software under the current test task is generated. The target test file may contain all necessary test data, including annotated video information, log information, and resource information, as well as any relevant test scenarios and expected results. Ultimately, through the target test file, testers can conduct an in-depth analysis of the vehicle software, such as comparing actual performance indicators with expected performance indicators, identifying software defects, evaluating software stability, etc., thereby providing detailed background and context information for the test results, making the test process more traceable.
[0045] Testers can also mark key events based on video content, log records and resource usage, such as key moments of test tasks, descriptions of software behavior, records of performance indicators, etc., to facilitate a more accurate understanding of events that occurred during the test process, thereby improving the accuracy of test analysis.
[0046] Optionally, in one embodiment of the present application, video information, log information and resource information are located and labeled, including: dividing the video information, log information and resource information based on preset time intervals to obtain multiple information subsets; based on the timestamp of each information subset in the multiple information subsets, locating and labeling each information subset, and obtaining labeled test information from the labeled information subsets.
[0047] It should be noted that the preset time interval can be set by those skilled in the art according to actual conditions and is not specifically limited here.
[0048] In the actual implementation process, the information subsets can be divided according to the time interval of every 300 seconds or every five minutes. Among them, since the video information, log information and resource information come from different data sources, it is necessary to align the timeline based on the timestamp of each information subset to ensure that the information subsets from different data sources match at the time level, and finally generate the labeled test information using the labeled information subsets.
[0049] Optionally, in one embodiment of the present application, each information subset is located and marked based on the timestamp of each information subset among multiple information subsets, including: among all information subsets, extracting at least one collaborative information subset that is within a preset floating time length of the timestamp of the current information subset; confirming the collaborative group based on the timestamp of the current information subset, and adding a positioning identifier corresponding to the collaborative group to at least one collaborative information subset and the current information subset, respectively.
[0050] It should be noted that the preset floating time duration can be set by those skilled in the art according to actual conditions and is not specifically limited here.
[0051] In the actual execution process, timestamp information can be extracted from each information subset to determine the time range and order of the information subset. For the current information subset, according to the preset floating time range, all other information subsets that overlap with the current information subset within the specified time and space range are searched and extracted within the floating time to obtain the collaborative information subset. Finally, based on the timestamp of the current information subset, the collaborative group is confirmed, that is, a group of information subsets that are close in time, and the location identifier corresponding to the collaborative group is added to at least one collaborative information subset and the current information subset, so that the test personnel can quickly and flexibly locate the test data of the previous and next time periods when viewing the data of a specific time period in the future, and realize the association of multiple data source information at the time level, so as to better analyze the behavior of the software at different components and levels.
[0052] The working content of the embodiment of the present application is described in detail below with a specific embodiment. Figure 3 The figure is a schematic diagram of the principle of data stream collection in vehicle-mounted software testing according to an embodiment of the present application.
[0053] In the video transmission program application, the adsorption mobile phone holder, Android mobile phone and video transmission program are used to record the video. The adsorption mobile phone holder is adsorbed on the top of the car, and the holder is adjusted to aim at the central control screen for recording. The video transmission program is an application running on the Android phone, which is connected to the central control host through Socket and transmits the video stream data to the central control host monitoring program in real time.
[0054] In the log monitoring program application, it is executed by the Android application installed in the central control host. After the tester clicks the monitoring start button, the program automatically executes the adb logcat command to obtain the log information data stream of the Android system operation, and then transmits the log information data stream to the file system for processing.
[0055] In the performance monitoring program application, the Android application installed in the central control host is executed. After the tester clicks the monitoring start button, the program automatically records the system performance resource usage information every three seconds, and then transmits the performance resource information to the file system for processing. The principle of system performance monitoring is as follows: obtain the current application package name information through the "adb shell dumpsys activity|grep mResume" command; collect the overall CPU load information through the "adb shell top-d 2" command; collect memory information through the "adb shell dumpsysmeminfo|grep packageName" command.
[0056] File processing is performed by the Android application installed in the central control host. The program includes receiving the video data stream, log information data stream and performance resource data stream transmitted by the mobile phone, and writing them to the file system. The file naming rule is named with the current time minute and the video, log, and resource suffixes. For example, if the time is 2023-11-26 08:23:00, the video file is 202311260823.video, the log file is 202311260823.log, and the performance resource occupancy file is 202311260823.res. Combined with video, log, and performance information, it is provided to R&D test personnel to analyze and reproduce problems to improve efficiency.
[0057] According to the vehicle software testing method proposed in the embodiment of the present application, during the vehicle software testing process, the tester's operating actions, software logs and memory resource information can be collected and integrated to achieve efficient positioning of test problem backtracking, thereby improving the convenience and accuracy of vehicle software verification and making it more practical. This solves the problem in the related art that the existing vehicle software problem reproduction lacks detailed data basis, often relies on manual inspection for problem backtracking, and is difficult to achieve efficient and fast vehicle software testing, affecting the stability and accuracy of vehicle cockpit functions.
[0058] Next, a vehicle-mounted software testing device according to an embodiment of the present application will be described with reference to the accompanying drawings.
[0059] Figure 4 It is a structural diagram of a testing device for vehicle-mounted software according to an embodiment of the present application.
[0060] like Figure 4 As shown, the vehicle-mounted software testing device 10 includes: a judgment module 100 , an acquisition module 200 and a testing module 300 .
[0061] The judgment module 100 is used to receive the current test task of the vehicle-mounted software and judge whether the tester turns on the preset monitoring mode.
[0062] The acquisition module 200 is used to collect video information of the tester during the execution of the current test task when the tester turns on the preset monitoring mode, and to obtain log information and resource information of the vehicle-mounted software during the execution of the current test task.
[0063] The test module 300 is used to locate and annotate the video information, log information and resource information to obtain annotated test information, and generate a target test file for the vehicle-mounted software under the current test task based on the annotated test information, so as to obtain the test result of the vehicle-mounted software using the target test file.
[0064] Optionally, in one embodiment of the present application, the acquisition module 200 includes:
[0065] A matching unit is used to match at least one target application of the vehicle software based on the current test task.
[0066] The generating unit is used to extract historical log records of at least one target application during the execution of the current test task, so as to generate log information according to the historical log records.
[0067] Optionally, in one embodiment of the present application, the acquisition module 200 includes:
[0068] The confirmation unit is used to confirm at least one performance indicator of the vehicle software based on the current test task.
[0069] The collection unit is used to collect total load data and memory data of the vehicle-mounted software based on at least one performance indicator, and obtain resource information from the total load data and memory data.
[0070] Optionally, in one embodiment of the present application, the test module 300 includes:
[0071] The dividing unit is used to divide the video information, log information and resource information based on a preset time interval to obtain multiple information subsets.
[0072] The labeling unit is used to locate and label each information subset based on the timestamp of each information subset in the multiple information subsets, and obtain labeling test information from the labeled information subset.
[0073] Optionally, in one embodiment of the present application, the labeling unit is specifically used to: extract, from all information subsets, at least one collaborative information subset that is within a preset floating duration of the timestamp of the current information subset; confirm the collaborative group based on the timestamp of the current information subset, and add a positioning identifier corresponding to the collaborative group to at least one collaborative information subset and the current information subset, respectively.
[0074] It should be noted that the above explanation of the embodiment of the testing method for vehicle-mounted software is also applicable to the testing device for vehicle-mounted software of this embodiment, and will not be repeated here.
[0075] According to the vehicle software testing device proposed in the embodiment of the present application, during the vehicle software testing process, the tester's operating actions, software logs and memory resource information can be collected and integrated to achieve efficient positioning of test problem backtracking, thereby improving the convenience and accuracy of vehicle software verification and making it more practical. This solves the problem in the related art that the existing vehicle software problem reproduction lacks detailed data basis, often relies on manual inspection for problem backtracking, and is difficult to achieve efficient and fast vehicle software testing, affecting the stability and accuracy of the vehicle cockpit function.
[0076] Figure 5 A schematic diagram of the structure of a vehicle provided in an embodiment of the present application. The vehicle may include:
[0077] A memory 501 , a processor 502 , and a computer program stored in the memory 501 and executable on the processor 502 .
[0078] When the processor 502 executes the program, the vehicle-mounted software testing method provided in the above embodiment is implemented.
[0079] Furthermore, the vehicle also includes:
[0080] The communication interface 503 is used for communication between the memory 501 and the processor 502 .
[0081] The memory 501 is used to store computer programs that can be executed on the processor 502 .
[0082] The memory 501 may include a high-speed RAM memory, and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.
[0083] If the memory 501, the processor 502 and the communication interface 503 are implemented independently, the communication interface 503, the memory 501 and the processor 502 can be connected to each other through a bus and communicate with each other. The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 5 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.
[0084] Optionally, in a specific implementation, if the memory 501, the processor 502 and the communication interface 503 are integrated on a chip, the memory 501, the processor 502 and the communication interface 503 can communicate with each other through an internal interface.
[0085] The processor 502 may be a central processing unit (CPU), or an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application.
[0086] This embodiment also provides a computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, the above-mentioned vehicle-mounted software testing method is implemented.
[0087] This embodiment also provides a computer program, which implements the above-mentioned vehicle-mounted software testing method when executed.
[0088] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or N embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, without contradiction.
[0089] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include at least one of the features. In the description of this application, "N" means at least two, such as two, three, etc., unless otherwise clearly and specifically defined.
[0090] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, fragment or portion of code comprising one or N executable instructions for implementing the steps of a custom logical function or process, and the scope of the preferred embodiments of the present application includes alternative implementations in which functions may not be performed in the order shown or discussed, including performing functions in a substantially simultaneous manner or in reverse order depending on the functions involved, which should be understood by technicians in the technical field to which the embodiments of the present application belong.
[0091] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as an ordered list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by an instruction execution system, device or apparatus (such as a computer-based system, a system including a processor, or other system that can fetch instructions from an instruction execution system, device or apparatus and execute instructions), or in combination with these instruction execution systems, devices or apparatuses. For the purpose of this specification, "computer-readable medium" can be any device that can contain, store, communicate, propagate or transmit a program for use by an instruction execution system, device or apparatus, or in combination with these instruction execution systems, devices or apparatuses. More specific examples of computer-readable media (a non-exhaustive list) include the following: an electrical connection with one or N wirings (electronic devices), a portable computer disk box (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable and programmable read-only memory (EPROM or flash memory), a fiber optic device, and a portable compact disk read-only memory (CDROM). In addition, the computer-readable medium may even be paper or other suitable medium on which the program is printed, since the program may be obtained electronically by optically scanning the paper or other medium and then editing, interpreting or processing in other suitable ways as necessary and then storing it in a computer memory.
[0092] It should be understood that the various parts of the present application can be implemented by hardware, software, firmware or a combination thereof. In the above-mentioned embodiment, the N steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented by hardware, as in another embodiment, it can be implemented by any one of the following technologies known in the art or their combination: a discrete logic circuit having a logic gate circuit for implementing a logic function for a data signal, a dedicated integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.
[0093] A person skilled in the art may understand that all or part of the steps in the method for implementing the above-mentioned embodiment may be completed by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, which, when executed, includes one or a combination of the steps of the method embodiment.
[0094] In addition, each functional unit in each embodiment of the present application may be integrated into a processing module, or each unit may exist physically separately, or two or more units may be integrated into one module. The above-mentioned integrated module may be implemented in the form of hardware or in the form of a software functional module. If the integrated module is implemented in the form of a software functional module and sold or used as an independent product, it may also be stored in a computer-readable storage medium.
[0095] The storage medium mentioned above may be a read-only memory, a magnetic disk or an optical disk, etc. Although the embodiments of the present application have been shown and described above, it can be understood that the above embodiments are exemplary and cannot be understood as limiting the present application. A person of ordinary skill in the art may change, modify, replace and modify the above embodiments within the scope of the present application.
Claims
1. A method for testing vehicle-mounted software, characterized in that: The following steps are involved: Receive the current test task of the vehicle software and determine whether the tester turns on the preset monitoring mode; When the tester turns on the preset monitoring mode, video information of the tester in the process of executing the current test task is collected, and log information and resource information of the vehicle-mounted software in the process of running the current test task is obtained; The video information, the log information and the resource information are located and annotated to obtain annotated test information, and a target test file of the vehicle-mounted software under the current test task is generated based on the annotated test information, so as to obtain the test result of the vehicle-mounted software using the target test file.
2. The method according to claim 1, characterized in that The obtaining of log information and resource information of the vehicle-mounted software during the execution of the current test task includes: Matching at least one target application of the vehicle software based on the current test task; Extracting historical log records of the at least one target application during execution of the current test task, to generate the log information according to the historical log records.
3. The method according to claim 1, characterized in that The obtaining of log information and resource information of the vehicle-mounted software during the execution of the current test task includes: confirming at least one performance indicator of the vehicle-mounted software based on the current test task; The total load data and memory data of the vehicle-mounted software are collected based on the at least one performance indicator, and the resource information is obtained from the total load data and the memory data.
4. The method according to claim 1, characterized in that: The positioning and marking of the video information, the log information, and the resource information includes: Dividing the video information, the log information, and the resource information based on a preset time interval to obtain a plurality of information subsets; Based on the timestamp of each information subset among the multiple information subsets, each information subset is positioned and annotated, and the annotated test information is obtained from the annotated information subset.
5. The method according to claim 4, characterized in that The positioning and marking each information subset based on the timestamp of each information subset in the multiple information subsets includes: From all information subsets, extract at least one collaborative information subset that is within a preset floating time length of a timestamp of a current information subset; The coordination group is confirmed based on the timestamp of the current information subset, and a positioning identifier corresponding to the coordination group is added to the at least one coordination information subset and the current information subset respectively.
6. A vehicle software testing device, characterized in that: include: A judgment module is used to receive the current test task of the vehicle software and judge whether the tester turns on the preset monitoring mode; An acquisition module, used for collecting video information of the tester in the process of executing the current test task when the tester turns on the preset monitoring mode, and obtaining log information and resource information of the vehicle-mounted software in the process of running the current test task; A testing module is used to locate and annotate the video information, the log information and the resource information to obtain annotated test information, and to generate a target test file for the vehicle-mounted software under the current test task based on the annotated test information, so as to obtain the test result of the vehicle-mounted software using the target test file.
7. The device according to claim 6, characterized in that The acquisition module comprises: A matching unit, configured to match at least one target application of the vehicle-mounted software based on the current test task; A generating unit is used to extract the historical log records of the at least one target application during the execution of the current test task, so as to generate the log information according to the historical log records.
8. The device according to claim 6, characterized in that The acquisition module comprises: A confirmation unit, configured to confirm at least one performance indicator of the vehicle-mounted software based on the current test task; A collection unit is used to collect total load data and memory data of the vehicle-mounted software based on the at least one performance indicator, and obtain the resource information from the total load data and the memory data.
9. A vehicle, characterized in that: include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the vehicle software testing method as described in any one of claims 1 to 5.
10. A computer-readable storage medium having a computer program stored thereon, characterized in that: The program is executed by a processor to implement the vehicle-mounted software testing method as described in any one of claims 1 to 5.
