Test methods, apparatus, equipment, and storage media for on-board diagnostic applications

Abstract

This application relates to a testing method, apparatus, computer equipment, storage medium, and computer program product for an on-board diagnostic application. The method includes: acquiring a display log sent by the on-board diagnostic application during concurrent fault testing; sending the display log to a first host computer, the display log instructing the first host computer to verify the display status of the on-board diagnostic application based on the display log; upon receiving a diagnostic command from the first host computer, determining that the display status is abnormal, and acquiring a transmission log sent by a vehicle remote terminal; and determining the cause of the display abnormality in the on-board diagnostic application based on the display log and the transmission log. This improves the testing effectiveness of the on-board diagnostic application.

Description

Technical Field

[0001] This application relates to the field of vehicle testing technology, and in particular to a testing method, apparatus, computer equipment, storage medium, and computer program product for on-board diagnostic applications. Background Technology

[0002] With the development of vehicle technology, vehicles are becoming increasingly intelligent. In order to enable drivers to promptly grasp the vehicle's fault status and ensure driving safety, in-vehicle large screen diagnostic applications are usually used to display vehicle fault information in a timely manner, presenting the vehicle's faults in a visual way.

[0003] To ensure the accuracy of diagnostic applications, it is often necessary to test them. One approach involves simulating a vehicle fault and sending it to the diagnostic application for display, thus testing for errors. However, this method often fails to pinpoint the cause of the error, resulting in ineffective testing. Summary of the Invention

[0004] Therefore, it is necessary to provide a testing method, apparatus, computer equipment, computer-readable storage medium, and computer program product for vehicle diagnostic applications that can improve the testing effect of vehicle diagnostic application testing, in response to the above-mentioned technical problems.

[0005] Firstly, this application provides a testing method for on-board diagnostic applications, including:

[0006] During concurrent fault testing of the vehicle diagnostic application, the display logs sent by the vehicle diagnostic application are obtained.

[0007] The display log is sent to the first host computer, and the display log is used to instruct the first host computer to verify the display status of the vehicle diagnostic application according to the display log;

[0008] Upon receiving a diagnostic command from the first host computer, the system determines that the display status is abnormal and obtains the transmission log sent by the vehicle's remote terminal.

[0009] Based on the display log and the transmission log, determine the cause of the display anomaly in the vehicle diagnostic application.

[0010] Secondly, this application also provides a testing device for on-board diagnostic applications, comprising:

[0011] The display log acquisition module is used to acquire the display logs sent by the vehicle diagnostic application during the concurrent fault testing of the vehicle diagnostic application.

[0012] A log sending module is used to send the display log to a first host computer, wherein the display log is used to instruct the first host computer to verify the display status of the vehicle diagnostic application based on the display log;

[0013] The transmission log acquisition module is used to determine that the display status is abnormal and acquire the transmission log sent by the vehicle remote terminal when a diagnostic command is received from the first host computer.

[0014] The determination module is used to determine the cause of the display abnormality in the vehicle diagnostic application based on the display log and the transmission log.

[0015] Thirdly, this application also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0016] During concurrent fault testing of the vehicle diagnostic application, the display logs sent by the vehicle diagnostic application are obtained.

[0017] The display log is sent to the first host computer, and the display log is used to instruct the first host computer to verify the display status of the vehicle diagnostic application according to the display log;

[0018] Upon receiving a diagnostic command from the first host computer, the system determines that the display status is abnormal and obtains the transmission log sent by the vehicle's remote terminal.

[0019] Based on the display log and the transmission log, determine the cause of the display anomaly in the vehicle diagnostic application.

[0020] Fourthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, performs the following steps:

[0021] During concurrent fault testing of the vehicle diagnostic application, the display logs sent by the vehicle diagnostic application are obtained.

[0022] The display log is sent to the first host computer, and the display log is used to instruct the first host computer to verify the display status of the vehicle diagnostic application according to the display log;

[0023] Upon receiving a diagnostic command from the first host computer, the system determines that the display status is abnormal and obtains the transmission log sent by the vehicle's remote terminal.

[0024] Based on the display log and the transmission log, determine the cause of the display anomaly in the vehicle diagnostic application.

[0025] Fifthly, this application also provides a computer program product, including a computer program that, when executed by a processor, performs the following steps:

[0026] During concurrent fault testing of the vehicle diagnostic application, the display logs sent by the vehicle diagnostic application are obtained.

[0027] The display log is sent to the first host computer, and the display log is used to instruct the first host computer to verify the display status of the vehicle diagnostic application according to the display log;

[0028] Upon receiving a diagnostic command from the first host computer, the system determines that the display status is abnormal and obtains the transmission log sent by the vehicle's remote terminal.

[0029] Based on the display log and the transmission log, determine the cause of the display anomaly in the vehicle diagnostic application.

[0030] The aforementioned testing method, apparatus, computer equipment, storage medium, and computer program product for vehicle diagnostic applications directly acquire the display logs sent by the vehicle diagnostic application during concurrent fault testing. These display logs are then sent to a first host computer, which instructs the host computer to verify the display status of the vehicle diagnostic application based on the logs. Thus, the first host computer makes a preliminary judgment on the vehicle diagnostic application, enabling timely screening for any anomalies in the current concurrent fault test. Upon receiving a diagnostic command from the first host computer, an anomaly is determined, meaning the vehicle diagnostic application cannot display the tested fault during the concurrent fault test. At this point, the transmission logs sent by the vehicle's remote terminal are acquired; based on the display logs and transmission logs, the cause of the display anomaly in the vehicle diagnostic application is further accurately determined. Therefore, during concurrent fault testing, not only can the vehicle diagnostic application be tested, but once an error is detected, the cause of the error can be accurately located, improving the testing effectiveness of the vehicle diagnostic application. Attached Figure Description

[0031] To more clearly illustrate the technical solutions in the embodiments or related technologies of this application, the drawings used in the description of the embodiments or related technologies will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0032] Figure 1 This is an application environment diagram of a test method for an on-board diagnostic application in one embodiment;

[0033] Figure 2 This is a flowchart illustrating a testing method for an on-board diagnostic application in one embodiment;

[0034] Figure 3 This is a schematic diagram of the cause determination steps in one embodiment;

[0035] Figure 4 This is a schematic diagram of the testing steps for an on-board diagnostic application in one embodiment;

[0036] Figure 5 This is a structural block diagram of a test device for an on-board diagnostic application in one embodiment;

[0037] Figure 6 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0038] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0039] The testing method for on-board diagnostic applications provided in this application embodiment can be applied to, for example... Figure 1 In the application environment shown, the target host computer 102 communicates with the first host computer 104 via a network. Both the vehicle remote terminal 106 and the on-board diagnostic application 108 are deployed in a vehicle, for example, both are deployed in a vehicle. Optionally, the on-board diagnostic application 108 is deployed on the vehicle screen. The vehicle remote terminal 106 communicates with the on-board diagnostic application 108, which can be wired communication, for example, via a USB (Universal Serial Bus) cable, or via a network. The vehicle remote terminal 106 communicates wirelessly with the target host computer 102. The on-board diagnostic application 108 communicates with the target host computer 102, which can be wired communication, for example, via a USB cable, or wireless communication; the specific method is not limited.

[0040] During concurrent fault testing of the on-board diagnostic application 108, the target host computer 102 acquires the display log sent by the on-board diagnostic application. The target host computer 102 sends the display log to the first host computer 104, which instructs the first host computer 104 to verify the display status of the on-board diagnostic application based on the display log. Upon receiving a diagnostic command from the first host computer, the target host computer 102 determines that the display status is abnormal and acquires the transmission log sent by the vehicle remote terminal 106. Based on the display log and the transmission log, the target host computer 102 determines the cause of the display abnormality in the on-board diagnostic application 108.

[0041] In this embodiment, the target host computer 102 and the first host computer 104 can be the same host computer or different host computers; this embodiment uses different host computers as an example. A host computer is a computer device, which can be a terminal or a server. The data storage system can store the data that the server needs to process. The data storage system can be integrated on the server or placed on the cloud or other network servers. The terminal can be, but is not limited to, various personal computers, laptops, smartphones, and tablets. The server can be implemented using a standalone server or a server cluster composed of multiple servers. The vehicle diagnostic application is used to display vehicle faults. The vehicle remote terminal can be considered a telematics box (T-BOX), with networking capabilities, meaning the vehicle can be positioned with a satellite system, and vehicle information can be collected in real time for fault detection; it also has real-time vehicle status monitoring capabilities, acquiring various information, including real-time fuel consumption, remaining fuel, and other driving data; and it also has remote vehicle control capabilities, such as remotely closing car doors.

[0042] In one exemplary embodiment, such as Figure 2 As shown, an on-board diagnostic application method is provided, which is applied to... Figure 1 Taking the target host computer 102 as an example, the explanation includes the following steps S202 to S208. Wherein:

[0043] Step S202: During the concurrent fault test of the vehicle diagnostic application, obtain the display log sent by the vehicle diagnostic application.

[0044] The on-board diagnostic application is an in-vehicle application used to display the results of vehicle diagnostics, such as displaying vehicle faults. Concurrent fault testing involves simulating fault data from multiple fault types simultaneously and sending this data to the on-board diagnostic application for display. This tests whether the application can display all simulated fault types completely and correctly. If the display is complete and correct, the application is error-free and the test passes. If the display is incomplete or incorrect, the application malfunctions and the test fails. The display log records the data displayed by the on-board diagnostic application. Optionally, the log records the actual fault data displayed by the application during each test.

[0045] Optionally, during the concurrent fault testing of the vehicle diagnostic application, the vehicle diagnostic application generates a display log of the current concurrent fault test based on the actual fault data displayed by the vehicle diagnostic application and the actual fault data received, and sends the display log to the target host computer, which then obtains the display log of the current concurrent fault test.

[0046] For example, during the concurrent fault test of the vehicle's on-board diagnostic application, the on-board diagnostic application receives fault data sent from the vehicle's remote terminal, obtains the actually received fault data, and performs format conversion based on the actually received fault data to obtain the fault data for display, i.e., the actually displayed fault data. The on-board diagnostic application generates a display log based on the actually received fault data and the actually displayed fault data. The on-board diagnostic application sends this display log to the target host computer, which receives and stores the display log corresponding to the vehicle in the current concurrent fault test. For example, the target host computer associates the vehicle identifier of the vehicle on which the on-board diagnostic application is mounted and the test number of the current concurrent fault test with the display log before storing it.

[0047] In some embodiments, the method further includes: in response to a test request for an on-board diagnostic application, determining a fault simulation device currently being tested, and activating the fault simulation device so that the fault simulation device generates test fault data and sends it to a vehicle remote terminal, and sends it to the on-board diagnostic application for display via the vehicle remote terminal, wherein the test fault data contains test information for multiple types of test faults.

[0048] The fault simulation equipment is used to simulate concurrent fault tests. For example, it can be a simulation device equipped with a fault injection system or a simulation device based on a vehicle test bench. Vehicle test benches generate fault data relevant to actual vehicles, resulting in faster simulation speeds. However, for some scenarios, such as extreme environments, vehicle test benches cannot simulate the corresponding fault data. In such cases, a fault injection system can be used for simulation. The fault injection system includes units such as sensor fault injection boards, actuator fault injection boards, and high-current injection boards, used to automatically simulate and generate fault data from the vehicle. This fault injection system can simulate not only all fault data that a vehicle test bench can simulate, but also fault data under extreme conditions. The test fault data contains multiple test fault types and test information for each type.

[0049] Optionally, in response to a test request for an on-board diagnostic application, the target host computer determines the fault simulation device currently being tested from the simulation devices of the vehicle test bench and the fault injection system, and controls the fault simulation device to start simulation, so that the fault simulation device generates test fault data for the current test and sends it to the vehicle remote terminal. The vehicle remote terminal sends the actually received test fault data to the on-board diagnostic application, which performs format conversion based on the actually received test fault data to obtain the actual displayed fault test data, and then displays it.

[0050] For example, in response to a test request for an on-board diagnostic application, the target host computer queries a pre-stored test database to see if there is a record of a historical test corresponding to the vehicle identifier carried in the test request. If so, it determines the fault simulation device for the current test based on the historical test record. If not, it determines the fault simulation device for the current test based on actual needs.

[0051] It should be noted that, to ensure the effectiveness of multiple concurrent fault tests, the test fault data involved in each concurrent fault test is different. Therefore, in determining the fault simulation device for the current test (i.e., the current concurrent fault test), the records of historical concurrent fault tests that have already been conducted can be queried first. These records contain the test fault data simulated in the historical concurrent fault tests. Based on these records, fault data for other untested fault types are selected, thereby determining the fault simulation device capable of simulating these untested fault data. It should also be noted that if historical concurrent fault tests have already tested fault data from all extreme environments, then for the current concurrent fault test, it is not necessary to test the fault data from extreme environments again; instead, it is necessary to test faults in the actual vehicle. Therefore, it is not necessary to use a fault injection system for simulation; simulation can be performed solely using a vehicle test bench. That is, the simulation device on the vehicle test bench is determined as the current fault simulation device. For example, electrical faults such as power supply short circuits, ground short circuits, open circuits, and switch sticking can be simulated solely using a vehicle test bench. This improves the efficiency of fault simulation. For example, if historical concurrent fault testing has not tested fault data in extreme environments, then the simulation device for fault injection into the system needs to be determined as the current fault simulation device.

[0052] In this embodiment, in response to a test request for an on-board diagnostic application, the required fault simulation device is determined and activated. This allows the fault simulation device to promptly generate test fault data, which is then sent to the vehicle's remote terminal and subsequently displayed on the on-board diagnostic application. The test fault data includes test information for various fault types. This rapid response to the test request and generation of corresponding test fault data improves testing efficiency.

[0053] Step S204: The display log is sent to the first host computer. The display log is used to instruct the first host computer to verify the display status of the vehicle diagnostic application based on the display log.

[0054] The first host computer is a computer device used to determine whether the on-board diagnostic application is displaying correctly. The display status indicates whether the on-board diagnostic application is displaying correctly.

[0055] Optionally, the first host computer receives the display log sent by the target host computer, and the first host computer obtains the test fault data simulated by the pre-stored fault simulation device. The first host computer parses the actual displayed fault data in the display log, and verifies the display status of the vehicle diagnostic application based on the actual displayed fault data and the test fault data.

[0056] In some embodiments, the display log includes first fault data displayed by the vehicle diagnostic application. Sending the display log to the first host computer includes: upon receiving a query instruction sent by the first host computer, sending the display log to the first host computer. The display log is used to instruct the first host computer to compare the first fault data with pre-stored test fault data. If the first fault data and the test fault data are inconsistent, the display status is determined to be abnormal, and a diagnostic instruction is generated.

[0057] The query command includes the vehicle identifier of the vehicle on which the on-board diagnostic application is installed. The diagnostic command is used to indicate the reason for the abnormality displayed by the first host computer diagnostic. The first fault data is the fault data actually displayed by the on-board diagnostic application.

[0058] Optionally, the first host computer obtains the vehicle identifier and test number of the vehicle currently undergoing concurrent testing, and generates a query command based on the vehicle identifier and test number. The first host computer sends the query command to the target host computer. The target host computer sends the display log corresponding to the vehicle identifier and test number to the first host computer. After receiving the display log, the first host computer parses the display log and obtains the first fault data displayed by the vehicle diagnostic application. The first host computer queries the test fault data corresponding to the vehicle identifier and test number and compares the first fault data with the test fault data. If the first fault data and the test fault data are consistent, the first host computer determines that the vehicle diagnostic application has not made any errors in the current concurrent fault test, i.e., the display status is normal, and sends the result of the normal display status to the target host computer for corresponding storage, and ends the current concurrent fault test. If the first fault data and the test fault data are inconsistent, it determines that the display status is abnormal, generates a diagnostic command, and sends the diagnostic command to the target host computer. After receiving the diagnostic command, the target host computer returns to step S206 to continue execution.

[0059] For example, the first fault data includes first fault information of at least one first fault type, and the test fault data includes test fault information of multiple test fault types. If the number of first fault types is the same as the number of test fault types, and each first fault type has the same test fault type, then it is further verified whether the first fault information of each first fault type is consistent with the test fault information of its corresponding test fault type. If they are all consistent, then the first fault data and the test fault data are consistent. If at least one of the following is satisfied: the number of first fault types is different from the number of test fault types, there is a first fault type that does not have the same test fault type, or there is a first fault type whose first fault information is inconsistent with the test fault information of its corresponding test fault type, then it is determined that the first fault data and the test fault data are inconsistent.

[0060] In this embodiment, upon receiving a query command from the first host computer, the display log is directly sent to the first host computer. The display log instructs the first host computer to compare the first fault data with pre-stored test fault data to pre-verify whether the on-board diagnostic application is displaying an error. If the first fault data and the test fault data are inconsistent, an abnormal display condition is determined, and a diagnostic command is generated. This allows for accurate identification of the cause of the error based on the diagnostic command, improving the testing effectiveness of the on-board diagnostic application.

[0061] Step S206: Upon receiving a diagnostic command from the first host computer, determine that the display status is abnormal and obtain the transmission log sent by the vehicle remote terminal.

[0062] The transmission log records the process of fault data transmission between the vehicle's remote terminal and the on-board diagnostic application.

[0063] Optionally, upon receiving a diagnostic command from the first host computer, the target host computer determines that the display status corresponding to the current concurrent fault test is abnormal. The target host computer identifies the vehicle identifier of the vehicle on which the on-board diagnostic application is installed, and sends a log retrieval command to the vehicle remote terminal matching the vehicle identifier based on the test identifier. Upon receiving the log retrieval command, the vehicle remote terminal retrieves the transmission log corresponding to the test identifier from multiple pre-stored transmission logs and sends the transmission log corresponding to the test identifier to the target host computer.

[0064] Step S208: Determine the cause of the display anomaly in the vehicle diagnostic application based on the display log and transmission log.

[0065] Optionally, the target host computer verifies whether the format conversion of the on-board diagnostic application is incorrect based on the display log, obtaining a first verification result. Then, based on the display log and transmission log, it verifies whether the transmission between the on-board diagnostic application and the vehicle remote terminal is incorrect, obtaining a second verification result. The target host computer then uses the first and second verification results to pinpoint the cause of the display anomaly in the on-board diagnostic application.

[0066] Understandably, the first verification result can reflect whether the display anomaly is caused by an error in the on-board diagnostic application itself, i.e., whether there are errors or omissions in the format conversion process of the on-board diagnostic application. The second verification result can reflect whether the display anomaly is caused by a transmission error between the on-board diagnostic application and the vehicle's remote terminal.

[0067] It's important to note that in the entire fault data transmission chain, the fault simulation device first generates test fault data and sends it to the vehicle's remote terminal, which is then conducting the concurrent fault test. The vehicle's remote terminal then transmits the received test fault data to the on-board diagnostic application via a USB cable. The on-board diagnostic application converts the received fault data to its correct format to obtain the displayed fault data. During this process, any error, whether in transmission or format conversion, will result in incorrect fault data displayed by the on-board diagnostic application.

[0068] Especially in concurrent fault testing scenarios, where a large number of fault data types are transmitted simultaneously in a single test, data loss or omissions may occur in the fault data transmission chain. These factors can prevent the on-board diagnostic application from accurately and comprehensively displaying all fault data. Therefore, after the on-board diagnostic application displays the data, a pre-detection is performed by the first host computer to check whether the on-board diagnostic application is malfunctioning in the current concurrent fault test. If no errors are found, the current concurrent fault test ends. If errors are found, after obtaining the first and second verification results, the cause of the display anomaly in the on-board diagnostic application can be located based on the first and second verification results.

[0069] The aforementioned testing method for on-board diagnostic applications directly acquires the display logs sent by the on-board diagnostic application during concurrent fault testing. These logs are then sent to a first host computer, instructing it to verify the display status of the on-board diagnostic application. This allows the first host computer to make a preliminary judgment on the on-board diagnostic application, enabling timely screening for any anomalies in the concurrent fault testing. Upon receiving a diagnostic command from the first host computer, an anomaly is confirmed, meaning the on-board diagnostic application cannot display the tested fault during the concurrent fault testing. At this point, the transmission logs sent by the vehicle's remote terminal are acquired; based on the display and transmission logs, the cause of the display anomaly in the on-board diagnostic application is further accurately determined. Therefore, during concurrent fault testing, not only can the on-board diagnostic application be tested, but once an error is detected, the cause of the error can be precisely located, improving the testing effectiveness of the on-board diagnostic application.

[0070] In some embodiments, such as Figure 3 The diagram illustrates the cause determination steps in one embodiment. The display log also includes second fault data received by the on-board diagnostic application, and the transmission log includes third fault data sent to the on-board diagnostic application. Based on the display log and the transmission log, the cause of the display anomaly in the on-board diagnostic application is determined, including:

[0071] Step S302: Convert the format of the second fault data to obtain the converted second fault data, and compare the converted second fault data with the first fault data to obtain the first comparison result for the vehicle diagnostic application.

[0072] Format conversion involves transforming fault data from one format to another for display. This embodiment refers to a normal format conversion, meaning no omissions or missing data occur. However, in actual vehicle diagnostic applications, when converting second fault data to third fault data, the conversion may not be a normal format conversion; therefore, the first comparison result needs to be verified.

[0073] Optionally, after obtaining the display log, the target host computer parses the second fault data from the display log and converts the format of the second fault data to obtain the converted second fault data. The target host computer compares the converted second fault data with the first fault data to obtain a first comparison result. If the converted second fault data is the same as the first fault data, the first comparison result indicates that the comparison is consistent. If the converted second fault data is different from the first fault data, the first comparison result indicates that the comparison is inconsistent. The first comparison result mentioned here can be understood as the first verification result mentioned above.

[0074] In some embodiments, the converted second fault data includes at least one second fault type and corresponding second fault information, and the first fault data includes at least one first fault type and corresponding first fault information; comparing the converted second fault data and the first fault data to obtain a first comparison result for the vehicle diagnostic application includes: for each second fault type, comparing the second fault type with each first fault type respectively; if a first fault type is found to be consistent with the second fault type, comparing the second fault information of the verified second fault type with the first fault information of the first fault type to obtain a comparison result for the second fault type; if the comparison results for each second fault type all indicate that the comparison is consistent, determining that the first comparison result indicates that the comparison is consistent.

[0075] For example, the target host computer compares whether the number of the first fault type and the number of the second fault type are the same. If they are not the same, the target host computer directly determines that the first comparison result for the vehicle diagnostic application is inconsistent. If they are the same, the target host computer compares each second fault type with the first fault type.

[0076] If no first fault type is found to be the same as the second fault type, the target host computer will directly determine the first comparison result as inconsistent.

[0077] If a first fault type and a second fault type are found to be the same, the target host computer compares the first fault information corresponding to the first fault type with the second fault information of the second fault type. If they are different, the target host computer directly determines that the first comparison result is inconsistent. If they are the same, the target host computer determines that the first comparison result is consistent.

[0078] In this embodiment, for each second fault type, the second fault type is compared with each of the first fault types. If a first fault type and a second fault type are found to be consistent, it indicates that no fault data was omitted during the format conversion process. In this case, the second fault information of the verified second fault type is further compared with the first fault information of the first fault type to obtain the comparison result of the second fault type. If the comparison results of each second fault type all indicate consistency, it indicates that no fault information was missing during the format conversion process. In this case, it can be determined that the first comparison result indicates consistency. Furthermore, it can be determined that the error was not caused by the format conversion of the on-board diagnostic application.

[0079] Step S304: Compare the second fault data and the third fault data to obtain the second comparison result regarding the transmission between the vehicle remote terminal and the on-board diagnostic application.

[0080] The second fault data is the fault data actually received by the on-board diagnostic application. The third fault data is the fault data actually sent by the vehicle's remote terminal.

[0081] Optionally, after obtaining the transmission log, the target host computer parses the third fault data from the transmission log. The target host computer compares the second fault data and the third fault data to obtain a second comparison result. If the second fault data and the third fault data are the same, the target host computer determines that the second comparison result indicates a consistent comparison. If the third fault data and the third fault data are different, the target host computer determines that the third comparison result indicates an inconsistent comparison. The second comparison result mentioned here is the second verification result mentioned above.

[0082] The second fault data undergoes a format conversion to obtain the converted second fault data. This format conversion is a normal conversion; therefore, the fault type in the converted second fault data is consistent with the corresponding fault information and the second fault data itself. Thus, the second fault data includes at least one second fault type and its corresponding second fault information. The third fault data includes multiple third fault types and their corresponding third fault information.

[0083] For example, for each second fault type, the second fault type is compared with each third fault type; if it is found that a third fault type is consistent with the second fault type, the second fault information of the verified second fault type is compared with the third fault information of the third fault type to obtain the comparison result of the second fault type; if the comparison result of each second fault type indicates that the comparison is consistent, the second comparison result is determined to indicate that the comparison is consistent.

[0084] For example, the target host computer compares the number of third fault types with the number of second fault types. If they do not match, the target host computer directly determines that the second comparison result transmitted between the on-board diagnostic application and the vehicle remote terminal is inconsistent. If they match, the target host computer compares each second fault type with the third fault type.

[0085] If no third fault type is found to be the same as the second fault type, the target host computer will directly determine that the second comparison result is inconsistent.

[0086] If a third fault type is found to be the same as the second fault type, the target host computer compares the third fault information corresponding to the third fault type with the second fault information of the second fault type. If they are different, the target host computer directly determines that the second comparison result is inconsistent. If they are the same, the target host computer determines that the second comparison result is consistent.

[0087] Step S306: If the first comparison result is inconsistent and the second comparison result is consistent, determine that the cause of the display abnormality is a display abnormality in the vehicle diagnostic application.

[0088] In this embodiment, firstly, the second fault data is format-converted to obtain converted second fault data. By comparing the converted second fault data with the first fault data, a first comparison result regarding the on-board diagnostic application is obtained. Therefore, based on the first comparison result, it is possible to promptly verify whether the display error is caused by an incorrect format conversion in the on-board diagnostic application. The second fault data and the third fault data are then compared to obtain a second comparison result regarding the transmission between the vehicle remote terminal and the on-board diagnostic application. Therefore, based on the second comparison result, it is possible to promptly verify whether the display error is caused by a transmission error between the vehicle remote terminal and the on-board diagnostic application. When the first comparison result shows inconsistency, but the second comparison result shows consistency, the cause of the display anomaly can be accurately located as a display anomaly in the on-board diagnostic application, thereby improving the testing effectiveness of the on-board diagnostic application.

[0089] In some embodiments, the method further includes: if the first comparison result characterization is consistent and the second comparison result characterization is inconsistent, determining that the cause of the display anomaly is an abnormal transmission between the vehicle remote terminal and the vehicle diagnostic application.

[0090] In other examples, where the first comparison result indicates inconsistency and the second comparison result indicates inconsistency, the cause of the display anomaly is determined to be abnormal transmission between the vehicle remote terminal and the on-board diagnostic application, and a display anomaly in the on-board diagnostic application.

[0091] Furthermore, if the first comparison result is consistent and the second comparison result is consistent, the target host computer determines that the current concurrent fault test is abnormal and records the transmission log and display log of the current concurrent fault test to instruct the corresponding maintenance personnel to perform further troubleshooting based on the transmission log and display log.

[0092] In this embodiment, when the first comparison result is consistent and the second comparison result is inconsistent, the cause of the display anomaly can be accurately located as abnormal transmission between the vehicle remote terminal and the vehicle diagnostic application, thereby improving the testing effect of the vehicle diagnostic application.

[0093] In a specific embodiment, such as Figure 4The diagram illustrates the testing steps for an on-board diagnostic application in one embodiment. This embodiment involves a first host computer, a second host computer, and a third host computer. In some instances, the first, second, and third host computers can be the same host computer; for example, they can all be considered as target host computers. In some instances, for further distinction, both the second and third host computers can be considered as target host computers, i.e., either the second or third host computer is selected as the target host computer. In this example, the first host computer is used to pre-verify whether the current concurrent fault test has failed. If an error occurs, the target host computer is used to locate the cause of the error; that is, the target host computer and the first host computer have different roles in this example. The following explanation uses either the second or third host computer as the target host computer as an example.

[0094] Figure 4 The system uses a conversion unit to switch between the simulation equipment of the fault injection system and the simulation equipment of the vehicle test bench. Based on this conversion unit, the fault simulation equipment for the current concurrent fault test is determined. The test fault data simulated by the fault simulation equipment is stored in the first host computer via a CAN (Controller Area Network) unit. The first host computer detects and records the test fault data generated by the fault simulation equipment via the CAN unit. The cloud backend is used to store data stored by the vehicle's remote terminal, such as transmission logs. The target host computer (second or third host computer) reads data from the on-board diagnostic application via ADB (Android Debug Bridge) debugging commands, such as displaying logs. Figure 4 The vehicle-mounted remote terminal connects to the vehicle diagnostic application via a USB cable, and the vehicle diagnostic application connects to a third host computer via a USB cable. The second host computer can communicate with the vehicle remote terminal and the vehicle diagnostic application via a network. Similarly, the third host computer can communicate with the vehicle remote terminal and the vehicle diagnostic application via a network.

[0095] The testing process of the vehicle diagnostic application in this embodiment will be explained in detail below. During concurrent fault testing of the vehicle diagnostic application, the target host computer responds to the test request for the vehicle diagnostic application, determines the fault simulation device currently being tested, and activates the fault simulation device. This causes the fault simulation device to generate test fault data, which is then sent to the vehicle remote terminal and displayed on the vehicle diagnostic application via the vehicle remote terminal. The test fault data includes test information for various types of test faults. The target host computer obtains the display log sent by the vehicle diagnostic application. The target host computer sends the display log to the first host computer. The first host computer compares the first fault data with pre-stored test fault data. If the first fault data and the test fault data are inconsistent, it determines that the display status is abnormal, generates a diagnostic command, and sends it to the target host computer.

[0096] Upon receiving a diagnostic command from the first host computer, the target host computer will send a display log to the first host computer. The display log includes second fault data received by the on-board diagnostic application, and the transmission log includes third fault data sent to the on-board diagnostic application. The second fault data is then format-converted to obtain converted second fault data. The converted second fault data includes at least one second fault type and corresponding second fault information, while the first fault data includes at least one first fault type and corresponding first fault information. The target host computer compares the number of first fault types and second fault types. If they do not match, the target host computer directly determines the first comparison result for the on-board diagnostic application as inconsistent. If they match, for each second fault type, the target host computer compares the second fault type with the first fault type. If no first fault type matches the second fault type, the target host computer directly determines the first comparison result as inconsistent. If a first fault type and a second fault type are found to be the same, the target host computer compares the first fault information corresponding to the first fault type with the second fault information of the second fault type. If they are different, the target host computer directly determines that the first comparison result is inconsistent. If they are the same, the target host computer determines that the first comparison result is consistent.

[0097] Since the second fault data includes at least one second fault type and corresponding second fault information, and the third fault data includes multiple third fault types and corresponding third fault information, the target host computer compares the number of third fault types with the number of second fault types. If they are inconsistent, the target host computer directly determines that the second comparison result regarding the transmission between the on-board diagnostic application and the vehicle remote terminal is inconsistent. If they are consistent, for each second fault type, the target host computer compares the second fault type with the third fault type respectively. If no third fault type is found to be the same as the second fault type, the target host computer directly determines that the second comparison result is inconsistent. If a third fault type is found to be the same as the second fault type, the target host computer compares whether the third fault information corresponding to the verified third fault type is the same as the second fault information of the second fault type. If they are different, the target host computer directly determines that the second comparison result is inconsistent; if they are the same, the target host computer determines that the second comparison result is consistent.

[0098] If the first comparison result is inconsistent but the second comparison result is consistent, the cause of the display anomaly is determined to be a display anomaly in the on-board diagnostic application. If the first comparison result is consistent but the second comparison result is inconsistent, the cause of the display anomaly is determined to be abnormal transmission between the vehicle remote terminal and the on-board diagnostic application.

[0099] In this embodiment, during concurrent fault testing of the vehicle diagnostic application, the display log sent by the application is directly acquired. This log is then sent to a first host computer, which instructs the host computer to verify the display status of the vehicle diagnostic application. Thus, the host computer makes a preliminary judgment on the vehicle diagnostic application, enabling timely screening for any anomalies in the concurrent fault test. Upon receiving a diagnostic command from the host computer, an anomaly is determined, meaning the vehicle diagnostic application cannot display the tested fault during the concurrent fault test. At this point, the transmission log sent by the vehicle's remote terminal is acquired; based on the display log and transmission log, the cause of the display anomaly in the vehicle diagnostic application is further accurately determined. Therefore, during concurrent fault testing, not only can the vehicle diagnostic application be tested, but once an error is detected, the cause of the error can be precisely located, improving the testing effectiveness of the vehicle diagnostic application. Furthermore, by setting up simulation equipment for the fault injection system and simulation equipment for the whole vehicle test bench, it is possible to flexibly switch between automatic and manual modes, adapt to more test scenario requirements, and have higher test coverage. In other words, it can achieve complementarity between real vehicle operating conditions and complete simulation, which can test fault modes under extreme operating conditions while ensuring the safety and integrity of the test. At the same time, it can perform comparative tests between the fault injection system and the whole vehicle test bench, better ensuring the accuracy of the test.

[0100] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0101] Based on the same inventive concept, this application also provides a testing device for an on-board diagnostic application to implement the testing method for the on-board diagnostic application described above. The solution provided by this device is similar to the solution described in the above method. Therefore, the specific limitations of one or more on-board diagnostic application testing device embodiments provided below can be found in the limitations of the on-board diagnostic application testing method described above, and will not be repeated here.

[0102] In one exemplary embodiment, such as Figure 5 As shown, a test device 500 for vehicle diagnostic applications is provided, including: a log display acquisition module 502, a log sending module 504, a log transmission acquisition module 506, and a determination module 508, wherein:

[0103] The display log acquisition module 502 is used to acquire the display logs sent by the vehicle diagnostic application during the concurrent fault testing of the vehicle diagnostic application.

[0104] The log sending module 504 is used to send the display log to the first host computer. The display log is used to instruct the first host computer to verify the display status of the vehicle diagnostic application based on the display log.

[0105] The transmission log acquisition module 506 is used to determine that the display status is abnormal and acquire the transmission log sent by the vehicle remote terminal when a diagnostic command is received from the first host computer.

[0106] The determination module 508 is used to determine the cause of the display abnormality in the vehicle diagnostic application based on the display log and the transmission log.

[0107] In some embodiments, the apparatus further includes a data transmission module, which is configured to, in response to a test request for an on-board diagnostic application, determine the fault simulation device currently being tested and activate the fault simulation device so that the fault simulation device generates test fault data and sends it to a vehicle remote terminal, and then sends it to the on-board diagnostic application for display via the vehicle remote terminal. The test fault data includes test information for various types of test faults.

[0108] In some embodiments, the display log includes first fault data displayed by the vehicle diagnostic application. The log sending module 504 is used to send the display log to the first host computer when it receives a query instruction sent by the first host computer. The display log is used to instruct the first host computer to compare the first fault data with pre-stored test fault data. If the first fault data and the test fault data are inconsistent, the display status is determined to be abnormal and a diagnostic instruction is generated.

[0109] In some embodiments, the display log further includes second fault data received by the vehicle diagnostic application, and the transmission log includes third fault data sent to the vehicle diagnostic application; the log sending module 504 is used to convert the format of the second fault data to obtain converted second fault data, and compare the converted second fault data with the first fault data to obtain a first comparison result regarding the vehicle diagnostic application; compare the second fault data and the third fault data to obtain a second comparison result regarding the transmission between the vehicle remote terminal and the vehicle diagnostic application; if the first comparison result indicates inconsistency and the second comparison result indicates consistency, it is determined that the cause of the display abnormality is a display abnormality in the vehicle diagnostic application.

[0110] In some embodiments, the converted second fault data includes at least one second fault type and corresponding second fault information, and the first fault data includes at least one first fault type and corresponding first fault information; the log sending module 504 is used to compare the second fault type with each first fault type for each second fault type; if it is found that a first fault type is consistent with the second fault type, the second fault information of the verified second fault type is compared with the first fault information of the first fault type to obtain the comparison result of the second fault type; if the comparison result of each second fault type indicates that the comparison is consistent, the first comparison result is determined to indicate that the comparison is consistent.

[0111] In some embodiments, the determining module 508 is further configured to determine that the cause of the display anomaly is an abnormal transmission between the vehicle remote terminal and the on-board diagnostic application when the first comparison result characterization is consistent and the second comparison result characterization is inconsistent.

[0112] The modules in the aforementioned on-board diagnostic application testing device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the corresponding operations of each module.

[0113] In one exemplary embodiment, a computer device is provided, which is any of the host computers mentioned above. The computer device can be a server or a terminal. Its internal structure diagram can be as follows: Figure 6As shown, this computer device includes a processor, memory, input / output (I / O) interfaces, and a communication interface. The processor, memory, and I / O interfaces are connected via a system bus, and the communication interface is also connected to the system bus via the I / O interfaces. The processor provides computational and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and databases. The internal memory provides the environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The I / O interfaces are used for exchanging information between the processor and external devices. The communication interface is used for communication with external terminals via a network connection. When the computer program is executed by the processor, it implements a testing method for an on-board diagnostic application.

[0114] Those skilled in the art will understand that Figure 6 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0115] In one exemplary embodiment, a computer device is provided, including a memory and a processor. The memory stores a computer program, and the processor executes the computer program to perform the following steps: During concurrent fault testing of an on-board diagnostic application, acquiring a display log sent by the on-board diagnostic application; sending the display log to a first host computer, the display log instructing the first host computer to verify the display status of the on-board diagnostic application based on the display log; upon receiving a diagnostic command from the first host computer, determining that the display status is abnormal, and acquiring a transmission log sent by a vehicle remote terminal; and determining the cause of the display abnormality in the on-board diagnostic application based on the display log and the transmission log.

[0116] In one embodiment, when the processor executes the computer program, it further performs the following steps: in response to a test request for an on-board diagnostic application, it determines the fault simulation device currently being tested and activates the fault simulation device so that the fault simulation device generates test fault data and sends it to a vehicle remote terminal, and sends it to the on-board diagnostic application for display via the vehicle remote terminal. The test fault data contains test information for various types of test faults.

[0117] In one embodiment, the display log includes first fault data displayed by the vehicle diagnostic application. When the processor executes the computer program, it also performs the following steps: upon receiving a query instruction sent by a first host computer, the display log is sent to the first host computer. The display log is used to instruct the first host computer to compare the first fault data with pre-stored test fault data. If the first fault data and the test fault data are inconsistent, the display status is determined to be abnormal, and a diagnostic instruction is generated.

[0118] In one embodiment, the display log further includes second fault data received by the vehicle diagnostic application, and the transmission log includes third fault data sent to the vehicle diagnostic application; when the processor executes the computer program, it also performs the following steps: converting the format of the second fault data to obtain converted second fault data, and comparing the converted second fault data with the first fault data to obtain a first comparison result regarding the vehicle diagnostic application; comparing the second fault data with the third fault data to obtain a second comparison result regarding the transmission between the vehicle remote terminal and the vehicle diagnostic application; if the first comparison result indicates inconsistency and the second comparison result indicates consistency, it is determined that the cause of the display anomaly is a display anomaly in the vehicle diagnostic application.

[0119] In one embodiment, the converted second fault data includes at least one second fault type and corresponding second fault information, and the first fault data includes at least one first fault type and corresponding first fault information. When the processor executes the computer program, it further implements the following steps: for each second fault type, the second fault type is compared with each first fault type; if a first fault type is found to be consistent with a second fault type, the second fault information of the verified second fault type is compared with the first fault information of the first fault type to obtain a comparison result of the second fault type; if the comparison results of each second fault type indicate that the comparison is consistent, the first comparison result is determined to indicate that the comparison is consistent.

[0120] In one embodiment, when the processor executes the computer program, it further performs the following steps: if the first comparison result characterization is consistent and the second comparison result characterization is inconsistent, it determines that the cause of the display anomaly is an abnormal transmission between the vehicle remote terminal and the on-board diagnostic application.

[0121] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When executed by a processor, the computer program performs the following steps: During concurrent fault testing of an on-board diagnostic application, acquiring display logs sent by the on-board diagnostic application; sending the display logs to a first host computer, the display logs instructing the first host computer to verify the display status of the on-board diagnostic application based on the display logs; upon receiving a diagnostic command from the first host computer, determining that the display status is abnormal, and acquiring transmission logs sent by a vehicle remote terminal; and determining the cause of the display abnormality in the on-board diagnostic application based on the display logs and transmission logs.

[0122] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: in response to a test request for an on-board diagnostic application, it determines the fault simulation device currently being tested and activates the fault simulation device so that the fault simulation device generates test fault data and sends it to a vehicle remote terminal, and sends it to the on-board diagnostic application for display via the vehicle remote terminal. The test fault data contains test information for various types of test faults.

[0123] In one embodiment, the display log includes first fault data displayed by the vehicle diagnostic application. When the computer program is executed by the processor, it also performs the following steps: upon receiving a query instruction sent by a first host computer, the display log is sent to the first host computer. The display log is used to instruct the first host computer to compare the first fault data with pre-stored test fault data. If the first fault data and the test fault data are inconsistent, the display status is determined to be abnormal, and a diagnostic instruction is generated.

[0124] In one embodiment, the display log further includes second fault data received by the vehicle diagnostic application, and the transmission log includes third fault data sent to the vehicle diagnostic application; when the computer program is executed by the processor, it further performs the following steps: converting the format of the second fault data to obtain converted second fault data, and comparing the converted second fault data with the first fault data to obtain a first comparison result regarding the vehicle diagnostic application; comparing the second fault data with the third fault data to obtain a second comparison result regarding the transmission between the vehicle remote terminal and the vehicle diagnostic application; if the first comparison result indicates inconsistency and the second comparison result indicates consistency, it is determined that the cause of the display anomaly is a display anomaly in the vehicle diagnostic application.

[0125] In one embodiment, the converted second fault data includes at least one second fault type and corresponding second fault information, and the first fault data includes at least one first fault type and corresponding first fault information; when the computer program is executed by the processor, it further implements the following steps: for each second fault type, the second fault type is compared with each first fault type respectively; if it is found that a first fault type is consistent with the second fault type, the second fault information of the verified second fault type is compared with the first fault information of the first fault type to obtain the comparison result of the second fault type; if the comparison results of each second fault type indicate that the comparison is consistent, the first comparison result is determined to indicate that the comparison is consistent.

[0126] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: if the first comparison result characterization is consistent and the second comparison result characterization is inconsistent, determine that the cause of the display anomaly is an abnormal transmission between the vehicle remote terminal and the on-board diagnostic application.

[0127] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, performs the following steps: During concurrent fault testing of an on-board diagnostic application, acquiring display logs sent by the on-board diagnostic application; sending the display logs to a first host computer, the display logs instructing the first host computer to verify the display status of the on-board diagnostic application based on the display logs; upon receiving a diagnostic command from the first host computer, determining that the display status is abnormal, and acquiring transmission logs sent by a vehicle remote terminal; and determining the cause of the display abnormality in the on-board diagnostic application based on the display logs and transmission logs.

[0128] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: in response to a test request for an on-board diagnostic application, it determines the fault simulation device currently being tested and activates the fault simulation device so that the fault simulation device generates test fault data and sends it to a vehicle remote terminal, and sends it to the on-board diagnostic application for display via the vehicle remote terminal. The test fault data contains test information for various types of test faults.

[0129] In one embodiment, the display log includes first fault data displayed by the vehicle diagnostic application. When the computer program is executed by the processor, it also performs the following steps: upon receiving a query instruction sent by a first host computer, the display log is sent to the first host computer. The display log is used to instruct the first host computer to compare the first fault data with pre-stored test fault data. If the first fault data and the test fault data are inconsistent, the display status is determined to be abnormal, and a diagnostic instruction is generated.

[0130] In one embodiment, the display log further includes second fault data received by the vehicle diagnostic application, and the transmission log includes third fault data sent to the vehicle diagnostic application; when the computer program is executed by the processor, it further performs the following steps: converting the format of the second fault data to obtain converted second fault data, and comparing the converted second fault data with the first fault data to obtain a first comparison result regarding the vehicle diagnostic application; comparing the second fault data with the third fault data to obtain a second comparison result regarding the transmission between the vehicle remote terminal and the vehicle diagnostic application; if the first comparison result indicates inconsistency and the second comparison result indicates consistency, it is determined that the cause of the display anomaly is a display anomaly in the vehicle diagnostic application.

[0131] In one embodiment, the converted second fault data includes at least one second fault type and corresponding second fault information, and the first fault data includes at least one first fault type and corresponding first fault information; when the computer program is executed by the processor, it further implements the following steps: for each second fault type, the second fault type is compared with each first fault type respectively; if it is found that a first fault type is consistent with the second fault type, the second fault information of the verified second fault type is compared with the first fault information of the first fault type to obtain the comparison result of the second fault type; if the comparison results of each second fault type indicate that the comparison is consistent, the first comparison result is determined to indicate that the comparison is consistent.

[0132] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: if the first comparison result characterization is consistent and the second comparison result characterization is inconsistent, determine that the cause of the display anomaly is an abnormal transmission between the vehicle remote terminal and the on-board diagnostic application.

[0133] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data must comply with relevant regulations.

[0134] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0135] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0136] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A testing method for on-board diagnostic applications, characterized in that, The method includes: During concurrent fault testing of the vehicle diagnostic application, the display log sent by the vehicle diagnostic application is obtained. The display log includes the first fault data displayed by the vehicle diagnostic application and the second fault data received by the vehicle diagnostic application. The display log is sent to the first host computer, and the display log is used to instruct the first host computer to verify the display status of the vehicle diagnostic application according to the display log; Upon receiving a diagnostic command from the first host computer, it is determined that the display status is abnormal, and the transmission log sent by the vehicle remote terminal is obtained. The transmission log includes third fault data sent to the vehicle diagnostic application. The second fault data is converted to a new format to obtain the converted second fault data. The converted second fault data is then compared with the first fault data to obtain a first comparison result for the on-board diagnostic application. The second fault data and the third fault data are compared to obtain a second comparison result regarding the transmission between the vehicle remote terminal and the vehicle diagnostic application; If the first comparison result is inconsistent and the second comparison result is consistent, the cause of the display anomaly is determined to be a display anomaly in the vehicle diagnostic application.

2. The method according to claim 1, characterized in that, The method further includes: In response to a test request for the on-board diagnostic application, the fault simulation device for the current test is determined and activated, so that the fault simulation device generates test fault data and sends it to the vehicle remote terminal, and then sends it to the on-board diagnostic application for display through the vehicle remote terminal. The test fault data contains test information for various types of test faults.

3. The method according to claim 1, characterized in that, Sending the display log to the first host computer includes: Upon receiving a query command from the first host computer, the display log is sent to the first host computer. The display log is used to instruct the first host computer to compare the first fault data with pre-stored test fault data. If the first fault data and the test fault data are inconsistent, the display status is determined to be abnormal, and a diagnostic command is generated.

4. The method according to claim 1, characterized in that, The converted second fault data includes at least one second fault type and corresponding second fault information, and the first fault data includes at least one first fault type and corresponding first fault information; The comparison of the converted second fault data and the first fault data yields a first comparison result regarding the on-board diagnostic application, including: For each second fault type, the second fault type is compared with each of the first fault types; If a first fault type is found to be consistent with the second fault type, the second fault information of the found second fault type is compared with the first fault information of the first fault type to obtain the comparison result of the second fault type. If the comparison results for each of the second fault types all indicate that the comparisons are consistent, then the first comparison result is determined to indicate that the comparisons are consistent.

5. The method according to claim 3, characterized in that, The method further includes: If the first comparison result indicates that the comparison is consistent, but the second comparison result indicates that the comparison is inconsistent, the cause of the display anomaly is determined to be an abnormal transmission between the vehicle remote terminal and the vehicle diagnostic application.

6. A testing device for on-board diagnostic applications, characterized in that, The device includes: The display log acquisition module is used to acquire the display log sent by the vehicle diagnostic application during the concurrent fault test of the vehicle diagnostic application. The display log includes the first fault data displayed by the vehicle diagnostic application and the second fault data received by the vehicle diagnostic application. A log sending module is used to send the display log to a first host computer, wherein the display log is used to instruct the first host computer to verify the display status of the vehicle diagnostic application based on the display log; The transmission log acquisition module is used to determine that the display status is abnormal when receiving a diagnostic command sent by the first host computer, and to acquire the transmission log sent by the vehicle remote terminal. The transmission log includes third fault data sent to the vehicle diagnostic application. The determination module is used to convert the format of the second fault data to obtain converted second fault data, and compare the converted second fault data with the first fault data to obtain a first comparison result regarding the vehicle diagnostic application; compare the second fault data with the third fault data to obtain a second comparison result regarding the transmission between the vehicle remote terminal and the vehicle diagnostic application; if the first comparison result indicates inconsistency and the second comparison result indicates consistency, the module determines that the display abnormality is caused by a display abnormality in the vehicle diagnostic application.

7. The apparatus according to claim 6, characterized in that, The device further includes a data transmission module, which, in response to a test request for the vehicle diagnostic application, determines the fault simulation device currently being tested, and activates the fault simulation device so that the fault simulation device generates test fault data and sends it to the vehicle remote terminal, and then sends it to the vehicle diagnostic application for display through the vehicle remote terminal. The test fault data includes test information for various types of test faults.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 5.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 5.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 5.

Images