Automatic testing method and device for in-vehicle infotainment system, storage medium and electronic equipment

Abstract

The embodiment of the invention provides an automatic testing method and device for an in-vehicle infotainment device, a storage medium and electronic equipment, and the method comprises the steps: obtaining first in-vehicle infotainment device software data through a testing server when the in-vehicle infotainment device software data is changed, and transmitting the first in-vehicle infotainment device software data to a testing data generation server; the test data generation server obtains vehicle machine unit test data and vehicle machine system test data according to the first vehicle machine software data; sending the in-vehicle unit test data and the in-vehicle system test data to a test server; the test server sends the automatic test script, the in-vehicle unit test data, the in-vehicle system test data and the third in-vehicle software data to the in-vehicle; the vehicle machine performs vehicle machine software updating according to the automatic test script and the third vehicle machine software data, the updated vehicle machine software is tested according to the vehicle machine unit test data and the vehicle machine system test data, and a test result is obtained. According to the embodiment of the invention, the test cost can be reduced, and the test efficiency can be improved.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of in-vehicle infotainment system testing, and particularly to an in-vehicle infotainment system automated testing method, device, storage medium, and electronic device. Background Art

[0002] Currently, with the development of intelligent vehicles, the in-vehicle infotainment system, also known as the intelligent cockpit system, in-vehicle infotainment system, or in-vehicle infotainment (hereinafter referred to as in-vehicle infotainment), as an important part of the interaction between users and vehicles, integrates functions such as in-vehicle navigation, Bluetooth, Wi-Fi (wireless network), radio, audio and video, and intelligent voice prompts.

[0003] To continuously meet user needs, in-vehicle infotainment software often undergoes continuous iteration; every time the in-vehicle infotainment software version is updated, test engineers need to consume a large amount of time and labor costs for testing, which is time-consuming, laborious, and inefficient. Summary of the Invention

[0004] To overcome the problems in the related art, the present application provides an in-vehicle infotainment system automated testing method, device, storage medium, and electronic device, which can reduce testing costs and improve testing efficiency.

[0005] According to the first aspect of the embodiments of the present application, an in-vehicle infotainment system automated testing method is provided, including the following steps:

[0006] When the in-vehicle infotainment software data changes, the test server obtains the first in-vehicle infotainment software data and sends the first in-vehicle infotainment software data to the test data generation server; wherein, the first in-vehicle infotainment software data is used to indicate the newly added or modified software code data between the changed third in-vehicle infotainment software data and the previous second in-vehicle infotainment software data; the first in-vehicle infotainment software data includes at least one software interface function and software components related to the software interface function;

[0007] The test data generation server obtains in-vehicle unit test data and in-vehicle system test data according to the software interface function and software components; and sends the in-vehicle unit test data and in-vehicle system test data to the test server;

[0008] The test server sends the automated test script, in-vehicle unit test data, in-vehicle system test data, and third in-vehicle infotainment software data to the in-vehicle infotainment system;

[0009] The in-vehicle infotainment system updates the in-vehicle infotainment software according to the automated test script and the third in-vehicle infotainment software data, and tests the updated in-vehicle infotainment software according to the in-vehicle unit test data and in-vehicle system test data to obtain a test result.

[0010] In the embodiment of the present application, when the vehicle-mounted software data changes, the test server obtains the first vehicle-mounted software data and sends the first vehicle-mounted software data to the test data generation server; wherein, the first vehicle-mounted software data is used to indicate at least one software interface function newly added or modified between the changed third vehicle-mounted software data and the second vehicle-mounted software data before the change, and the software components related to the software interface function; the test data generation server obtains the vehicle unit test data and the vehicle system test data according to the software interface function and the software components; sends the vehicle unit test data and the vehicle system test data to the test server; the test server sends the automated test script, the vehicle unit test data, the vehicle system test data, and the third vehicle-mounted software data to the vehicle; the vehicle updates the vehicle-mounted software according to the automated test script and the third vehicle-mounted software data, and tests the updated vehicle-mounted software according to the vehicle unit test data and the vehicle system test data to obtain the test result, so that there is no need to manually write test data and no need to manually execute test operations, which can reduce the test cost and improve the test efficiency; and can avoid the risk of missing test points in manual testing by performing automated comprehensive testing according to the newly added or modified software code data.

[0011] In an optional embodiment, the software components include the first software component where the interface function is located and the second software component associated with the first software component; the steps for the test data generation server to obtain the vehicle unit test data and the vehicle system test data according to the software interface function and the software components include:

[0012] The test data generation server determines whether there is a first unit test case set corresponding to the first software component stored. If there is, it determines whether there is a test case corresponding to the software interface function stored in the first unit test case set. If there is, it obtains the stored first unit test case set; determines whether there is a second unit test case set corresponding to the second software component stored. If there is, it obtains the stored second unit test case set; and obtains the vehicle unit test data according to the first unit test case set and the second unit test case set.

[0013] The test data generation server determines whether there is a first system test case set corresponding to the first software component stored. If there is, it obtains the stored first system test case set; determines whether there is a second system test case set corresponding to the second software component stored. If there is, it obtains the stored second system test case set; and obtains the vehicle system test data according to the first system test case set and the second system test case set.

[0014] In the embodiments of the present application, by testing both the first software component where the interface function is located and the second software component associated with the first software component, comprehensive testing of the changed software data can be performed to avoid missing test points; the stored test cases can be directly obtained from the test data generation server, and the test case data can be quickly obtained, improving the test efficiency.

[0015] In an optional embodiment, the method further includes the steps of: if the test data generation server determines that the first unit test case set corresponding to the first software component is not stored, generating a first unit test case set identifier according to the name of the first software component; obtaining the corresponding source code from the third in-vehicle software data according to the software interface function, and obtaining the interface function data according to the source code; generating a first software interface test case according to the interface function data; and obtaining the first unit test case set according to the first unit test case set identifier and the first software interface test case.

[0016] When the test data generation server does not store the first unit test case set in the embodiments of the present application, the first unit test case set is automatically generated according to the first software component and the software interface function, without the need for users to write test cases, which can reduce the test cost.

[0017] In an optional embodiment, the interface function data includes: function name, judgment condition, and output parameter; the steps for the test data generation server to generate the first software interface test case according to the interface function data include: the test data generation server generating a first software interface test case identifier according to the function name; generating a stub function according to the judgment condition; generating an expected result comparison function according to the output function; and generating the first software interface test case according to the first software interface test case identifier, the stub function, and the expected result comparison function.

[0018] In the embodiments of the present application, the interface function data is obtained according to the software interface function, and thus the first software interface test case is automatically generated according to the interface function data, without the need for users to write, which can reduce the test cost and improve the test efficiency.

[0019] In an optional embodiment, if the test data generation server determines that the first unit test case set is stored but the test case corresponding to the software interface function is not stored, it obtains the corresponding source code from the third in-vehicle software data according to the software interface function, obtains the interface function data according to the source code; generates a first software interface test case according to the interface function data; adds the first software interface test case to the first unit test case set, and updates the first unit test case set.

[0020] When the test data generation server in the embodiment of the present application stores the first unit test case set but does not store the test cases corresponding to the software interface functions, by automatically generating the first software interface test cases and adding them to the first unit test case set for testing, the first unit test case set can be enriched to achieve comprehensive testing of the first software component unit.

[0021] In an optional embodiment, if the test data generation server determines that the first system test case set corresponding to the first software component is not stored, it generates the first system test case set identifier and the first application startup function of the application where the first software component is located according to the name of the first software component; obtains the first position coordinates of the first software component on the in-vehicle screen and generates the first resource data comparison function after touching the first software component according to the resource library; and uses the in-vehicle automation test tool to generate the first system test case set according to the first system test case set identifier, the first application startup function, the first position coordinates, and the first resource data comparison function.

[0022] In the embodiment of the present application, the test data generation server automatically generates the first system test case according to the first software component by using the in-vehicle automation test tool, so that the in-vehicle device can directly perform tests according to the first system test case without compilation, improving the test efficiency.

[0023] In an optional embodiment, the in-vehicle automation test method further includes the following steps: the test server performs a static scan on the third in-vehicle software data to obtain the static scan test result.

[0024] In the embodiment of the present application, by performing a static scan on the third in-vehicle software data by the test server to obtain the static scan test result, potential vulnerabilities and coding error problems in the code can be detected in a timely manner.

[0025] In an optional embodiment, the steps for the in-vehicle device to update the in-vehicle software according to the automation test script according to the third in-vehicle software data and test the updated in-vehicle software according to the in-vehicle unit test data and the in-vehicle system test data to obtain the test result include: the in-vehicle device updates the in-vehicle software according to the automation test script according to the third in-vehicle software data, performs software component testing on the updated in-vehicle software according to the in-vehicle unit test data to obtain the unit test result; and tests the updated in-vehicle software according to the in-vehicle system test data to obtain the system test result.

[0026] In the embodiment of the present application, by performing software component testing on the updated in-vehicle software according to the in-vehicle unit test data to obtain unit test results, and then testing the updated in-vehicle software according to the in-vehicle system test data to obtain system test results, when an error occurs in the third in-vehicle software code, it is possible to first determine from the unit test results whether there is a problem with the component code itself, and then determine from the system test results whether there is a problem with the interaction of the component among the entire system, so as to quickly locate the problems in the test.

[0027] According to the second aspect of the embodiment of the present application, there is provided an in-vehicle automation testing method, including the following steps:

[0028] When the in-vehicle software data changes, obtain the first in-vehicle software data; wherein, the first in-vehicle software data is used to indicate the newly added or modified software code data between the changed third in-vehicle software data and the previous second in-vehicle software data; the first in-vehicle software data includes at least one software interface function and the software components related to the software interface function;

[0029] Obtain the in-vehicle unit test data and the in-vehicle system test data according to the software interface function and the software components;

[0030] Send the automation test script, the in-vehicle unit test data, the in-vehicle system test data, and the third in-vehicle software data to the in-vehicle device, so that the in-vehicle device updates the in-vehicle software according to the third in-vehicle software according to the automation test script, and tests the updated in-vehicle software according to the in-vehicle unit test data and the in-vehicle system test data to obtain the test results.

[0031] According to the third aspect of the embodiment of the present application, there is provided an in-vehicle automation testing device, including:

[0032] A software data acquisition module, configured to obtain the first in-vehicle software data when the in-vehicle software data changes; wherein, the first in-vehicle software data is used to indicate the newly added or modified software code data between the changed third in-vehicle software data and the previous second in-vehicle software data; the first in-vehicle software data includes at least one software interface function and the software components related to the software interface function;

[0033] A test data acquisition module, which obtains the in-vehicle unit test data and the in-vehicle system test data according to the software interface function and the software components;

[0034] A test data sending module, configured to send the automation test script, the in-vehicle unit test data, the in-vehicle system test data, and the third in-vehicle software data to the in-vehicle device, so that the in-vehicle device updates the in-vehicle software according to the third in-vehicle software according to the automation test script, and tests the updated in-vehicle software according to the in-vehicle unit test data and the in-vehicle system test data to obtain the test results.

[0035] According to a fourth aspect of the embodiments of the present application, an electronic device is provided, including a processor and a memory; the memory stores a computer program, and the computer program is adapted to be loaded and executed by the processor to perform the vehicle-mounted device automation test method as described above.

[0036] According to a fifth aspect of the embodiments of the present application, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the vehicle-mounted device automation test method as described above is implemented.

[0037] The embodiments of the present application do not require manual writing of test data and do not require manual execution of test operations, which can reduce test costs and improve test efficiency; automated comprehensive testing can be performed according to newly added or modified software code data, which can avoid the risk of missing test points in manual testing.

[0038] It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit the present application.

[0039] For better understanding and implementation, the present invention will be described in detail below with reference to the accompanying drawings. Description of the Drawings

[0040] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the following drawings are only some embodiments of the present application, and those of ordinary skill in the art can also obtain other drawings based on these drawings without creative efforts.

[0041] Figure 1 It is a schematic diagram of the application scenario of the vehicle-mounted device automation test shown in the embodiments of the present application;

[0042] Figure 2 It is a flowchart of the vehicle-mounted device automation test method shown in the first embodiment of the present application;

[0043] Figure 3 It is a flowchart of the method for obtaining test data shown in an embodiment of the present application;

[0044] Figure 4 It is a flowchart of the vehicle-mounted device automation test method shown in the second embodiment of the present application;

[0045] Figure 5 It is a schematic block diagram of the vehicle-mounted device automation test device shown in the third embodiment of the present application;

[0046] Figure 6 It is a schematic block diagram of the structure of the electronic device shown in the fourth embodiment of the present application. Detailed Embodiments

[0047] To make the objectives, technical solutions, and advantages of this application clearer, the following will further describe the embodiments of this application in detail with reference to the accompanying drawings. Among them, when the following description involves the accompanying drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements.

[0048] It should be clear that the embodiments described in the following embodiments do not represent all embodiments consistent with this application. On the contrary, they are merely examples of devices and methods consistent with some aspects of this application as detailed in the appended claims. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative efforts belong to the scope of protection of this application.

[0049] The terms used in this application are only for the purpose of describing specific embodiments and are not intended to limit this application. The singular forms "a" and "the" used in this application are also intended to include the plural forms unless the context clearly indicates otherwise. In addition, in the description of this application, unless otherwise specified, "a plurality" means two or more. It should also be understood that the term "and / or" used herein refers to and includes any or all possible combinations of one or more of the associated listed items. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone; the character " / " generally represents an "or" relationship between the associated objects before and after.

[0050] It should be understood that although the terms first, second, third, etc. may be used in this application to describe various information, such information should not be limited to these terms. Moreover, these terms are only used to distinguish similar objects and do not have to be used to describe a specific order or sequence, nor can they be understood as indicating or implying relative importance. For those of ordinary skill in the art, the specific meanings of the above terms in this application can be understood according to specific circumstances. Depending on the context, the words "if" / "when" used in this application can be interpreted as "when...", "when...", or "in response to a determination".

[0051] Currently, with the development of intelligent vehicles, the in-vehicle infotainment system, also known as the intelligent cockpit system, car machine system, or car machine (hereinafter referred to as the car machine), as an important part of the interaction between users and vehicles, integrates functions such as in-vehicle navigation, Bluetooth, Wi-Fi (wireless network), radio, audio and video, and intelligent voice prompts.

[0052] To continuously meet user needs, car machine software often undergoes continuous iteration; for each update of the car machine software version, test engineers need to consume a large amount of time and labor costs for testing, which is time-consuming, laborious, and inefficient.

[0053] In an embodiment of the present application, at least one software interface function newly added or modified between the changed third in-vehicle software data and the previous second in-vehicle software data, as well as software components related to the software interface function, are used to automatically obtain in-vehicle unit test data and in-vehicle system test data. As a result, the in-vehicle unit updates the in-vehicle software according to the third in-vehicle software data based on the automated test script, and tests the updated in-vehicle software according to the in-vehicle unit test data and the in-vehicle system test data to obtain test results. This eliminates the need for manual writing of test data and manual execution of test operations, reduces test costs, improves test efficiency, and avoids the risk of missing test points in manual testing.

[0054] Please refer to Figure 1 , which is a schematic diagram of the application scenario of the in-vehicle automation testing method provided by an embodiment of the present application. The application scenario of the in-vehicle automation testing method provided by an embodiment of the present application includes a test server 10, a test data generation server 20, an in-vehicle unit 30, and an in-vehicle software database 40.

[0055] The test server 10 is respectively connected to the test data generation server 20, the in-vehicle unit 30, and the in-vehicle software database 40. The in-vehicle software database 40 stores in-vehicle software data. When the user A uploads the new version of the third in-vehicle software data, causing a change in the in-vehicle software database 40, the in-vehicle software database 40 sends a change notification to the test server 10. The test server 10 determines the first in-vehicle software data from the in-vehicle software database 40 and sends the first in-vehicle software data to the test data generation server 20, where the first in-vehicle software data is used to indicate the software code data newly added or modified between the changed third in-vehicle software data and the previous second in-vehicle software data in the in-vehicle software database 40. The test data generation server 20 sends the in-vehicle unit test data and the in-vehicle system test data generated according to the first in-vehicle software data to the test server 10, and the test server 10 then sends the in-vehicle unit test data and the in-vehicle system test data to the in-vehicle unit 30; the in-vehicle unit 30 conducts tests according to the in-vehicle unit test data and the in-vehicle system test data, obtains the test results, and sends the test results to the test server 10. The test server 10 then sends the test results to the user B via email, enabling the user B to conveniently obtain the test results of the new version of the third in-vehicle software data.

[0056] Next, the in-vehicle automation testing method provided by an embodiment of the present application will be introduced in detail in conjunction with the attached Figures 2 to 3 , and the in-vehicle automation testing method provided by an embodiment of the present application will be introduced in detail.

[0057] Please refer to Figure 2 , the in-vehicle automation testing method provided by an embodiment of the present application includes the following steps:

[0058] Step S101: When the in-vehicle software data changes, the test server obtains the first in-vehicle software data and sends the first in-vehicle software data to the test data generation server; wherein, the first in-vehicle software data is used to indicate the newly added or modified software code data between the changed third in-vehicle software data and the previous second in-vehicle software data; the first in-vehicle software data includes at least one software interface function and software components related to the software interface function.

[0059] The test server is responsible for the scheduling of in-vehicle testing and is used to implement data interaction between the test data generation server and the in-vehicle unit. Optionally, the test server can be Jenkins. Jenkins is an open-source automation server, a tool for continuous integration and continuous delivery, used to monitor continuously repeated tasks, aiming to provide an open and easy-to-use software platform for continuous integration of software projects and performing tasks such as compiling and packaging in-vehicle software.

[0060] In-vehicle software data refers to the code of various software installed on the in-vehicle unit and its related data. This data may include the source code of the software, compiled binary files, configuration files, and databases, etc. The in-vehicle software data can be stored on the test server or in an in-vehicle software database that interacts with the test server.

[0061] In the embodiment of the present application, the in-vehicle software data is stored in the in-vehicle software database, and each newly generated version of the in-vehicle software data after modification or addition is uploaded to the in-vehicle software database. Among them, the in-vehicle software database can be GitLab. GitLab is a repository management tool based on the open-source distributed version control system (Git), providing functions such as code hosting, version control, continuous integration, and continuous delivery.

[0062] In an optional embodiment, the test server can actively identify whether the in-vehicle software data has changed.

[0063] Specifically, the test server obtains the in-vehicle software data from the in-vehicle software database at preset time intervals and determines whether the third in-vehicle software data obtained at the current time has changed compared with the second in-vehicle software data obtained at the previous time interval.

[0064] In another optional embodiment, the test server can also be triggered passively to identify whether the in-vehicle software data has changed.

[0065] Specifically, when new in-vehicle software data is uploaded to the in-vehicle software database, it triggers the sending of information indicating that the in-vehicle software data has changed to the test server, thereby enabling the test server to determine that the in-vehicle software data has changed. For example, a trigger is bound between the test server and the in-vehicle code database. When new code is submitted for the in-vehicle software data, this trigger is activated. The test server can further obtain the second in-vehicle software data before the code submission and the third in-vehicle software data after the submission through the trigger, and determine whether the in-vehicle software data has changed.

[0066] It can be understood that for the third in-vehicle software data and the second in-vehicle software data, the test service area can determine whether the in-vehicle software data has changed by identifying different version numbers, or by directly comparing the third in-vehicle software data and the second in-vehicle software data.

[0067] The test server performs a one-to-one comparison at the code level between the second in-vehicle software data and the third in-vehicle software data to obtain the modified or added code; it parses the modified or added code to obtain the first in-vehicle software data.

[0068] A software interface function refers to a function used to implement communication and interaction between different software modules. The software interface function defines the protocols and specifications between modules, enabling different software components to effectively perform data transmission and information exchange. The software interface function in the embodiments of the present application can be an internal interface for internal communication between modules, or an external interface for interacting with external systems or users.

[0069] A software component refers to an independent module or unit that constitutes a software system. Software components can be developed, tested, deployed, and maintained independently. Software components have high cohesion and low coupling, and can interact with other components through interfaces. Component-based development can improve the maintainability, scalability, and reusability of software.

[0070] In the embodiments of the present application, the software components related to the software interface function include the first software component where the interface function is located and the second software component associated with the first software component. Among them, the second software component associated with the first software component includes the component directly defined in the software code as being associated with the first software component, and the component that interacts with the first software component extracted according to the software code logic.

[0071] Step S102: The test data generation server obtains in-vehicle unit test data and in-vehicle system test data according to the software interface function and the software components; it sends the in-vehicle unit test data and the in-vehicle system test data to the test server.

[0072] The test data generation server stores various test data. The test data generator traverses to obtain the corresponding in-vehicle unit test data and in-vehicle system test data according to software components and software interface functions. When the corresponding test data is not stored in the test data generation server, the test data generation server can also automatically generate the corresponding in-vehicle unit test data and in-vehicle system test data.

[0073] The in-vehicle unit test data is a series of test steps and operations for testing the in-vehicle unit or in-vehicle module. These test data are designed to verify the functions, performance, compatibility, security, etc. of the in-vehicle unit or in-vehicle module to ensure the stability and reliability of the in-vehicle unit.

[0074] The in-vehicle system test data is a set of test data for testing the overall functions and performance of the in-vehicle system. These test data are designed to verify whether the various functions of the in-vehicle system are normal, whether the performance is stable, and the compatibility with other systems, etc.

[0075] Step S103: The test server sends the automated test script, in-vehicle unit test data, in-vehicle system test data, and third in-vehicle software data to the in-vehicle unit.

[0076] The automated test script is used to indicate the process of the in-vehicle unit for automated testing. For example, the in-vehicle unit needs to perform software upgrade according to the third in-vehicle software data based on the automated test script, and then perform unit test according to the in-vehicle unit test data, and finally perform in-vehicle system test according to the in-vehicle test data.

[0077] It can be understood that a data communication link is established between the test server and the in-vehicle unit, which enables the test server to send the second in-vehicle software data and the in-vehicle test data to the in-vehicle unit.

[0078] Among them, the data communication link can be communication media of various connection types. For example, it can be a wired communication link, a wireless communication link, or an optical fiber cable, etc. In the embodiments of the present application, for the convenience of data transmission, data is transmitted between the test server and the in-vehicle unit through wifi.

[0079] Step S104: The in-vehicle unit updates the in-vehicle software according to the automated test script and the third in-vehicle software data, and tests the updated in-vehicle software according to the in-vehicle unit test data and the in-vehicle system test data to obtain the test results.

[0080] It can be understood that after the in-vehicle computer receives the automated test script, it executes the automated test script through the built-in or additionally installed automated test tool. On the one hand, it performs code testing on the newly added or modified software components according to the in-vehicle computer unit test data. On the other hand, according to the in-vehicle computer system test data, it simulates user operations and comprehensively tests the updated in-vehicle computer software.

[0081] In the embodiment of the present application, when the in-vehicle computer software data changes, the test server obtains the first in-vehicle computer software data and sends the first in-vehicle computer software data to the test data generation server; wherein, the first in-vehicle computer software data is used to indicate at least one software interface function and the software components related to the software interface function that are newly added or modified between the changed third in-vehicle computer software data and the unchanged second in-vehicle computer software data; the test data generation server obtains the in-vehicle computer unit test data and the in-vehicle computer system test data according to the software interface function and the software components; sends the in-vehicle computer unit test data and the in-vehicle computer system test data to the test server; the test server sends the automated test script, the in-vehicle computer unit test data, the in-vehicle computer system test data, and the third in-vehicle computer software data to the in-vehicle computer; the in-vehicle computer updates the in-vehicle computer software according to the automated test script and the third in-vehicle computer software data, and tests the updated in-vehicle computer software according to the in-vehicle computer unit test data and the in-vehicle computer system test data to obtain the test result, so that there is no need to manually write test data and no need to manually execute test operations, which can reduce the test cost and improve the test efficiency; performing automated comprehensive testing according to the newly added or modified software code data can avoid the risk of missing test points in manual testing.

[0082] Please refer to Figure 3 , in an optional embodiment, the software components include the first software component where the interface function is located and the second software component associated with the first software component; the step in step S102 where the test data generation server obtains the in-vehicle computer unit test data and the in-vehicle computer system test data according to the software interface function and the software components includes:

[0083] Step S1021: The test data generation server determines whether there is a first unit test case set corresponding to the first software component stored. If there is, it determines whether there is a test case corresponding to the software interface function stored in the first unit test case set. If there is, it obtains the stored first unit test case set; determines whether there is a second unit test case set corresponding to the second software component stored. If there is, it obtains the stored second unit test case set; obtains the in-vehicle computer unit test data according to the first unit test case set and the second unit test case set.

[0084] Optionally, the test data generation server compiles the first unit test case set and the second unit test case set into an executable in-vehicle unit test file, and uses the in-vehicle unit test file as the in-vehicle unit test data, so that the in-vehicle system can directly perform tests according to the executable in-vehicle unit test file without installing additional unit test tools, saving the installation cost.

[0085] Step S1022: The test data generation server determines whether there is a stored first system test case set corresponding to the first software component. If there is, it obtains the stored first system test case set; determines whether there is a stored second system test case set corresponding to the second software component. If there is, it obtains the stored second system test case set; and obtains the in-vehicle system test data according to the first system test case set and the second system test case set.

[0086] Optionally, the test data generation server uses an in-vehicle automation test tool to generate in-vehicle system test data without compilation, and the in-vehicle system can automatically identify and use it.

[0087] In the embodiment of the present application, by testing both the first software component where the interface function is located and the second software component associated with the first software component, comprehensive testing of the changed software data can be performed to avoid missing test points; the stored test cases can be directly obtained from the test data generation server, and the test case data can be obtained quickly, improving the test efficiency.

[0088] In an optional embodiment, step S1021 further includes step S10211: If the test data generation server determines that there is no stored first unit test case set corresponding to the first software component, it generates a first unit test case set identifier according to the name of the first software component; obtains the corresponding source code from the third in-vehicle software data according to the software interface function, and obtains the interface function data according to the source code; generates a first software interface test case according to the interface function data; and obtains the first unit test case set according to the first unit test case set identifier and the first software interface test case.

[0089] Among them, the test data set identifier is used to facilitate the management and identification of the test data of each software component. Each software component test data has a unique name to avoid confusion and duplication, and improve the test efficiency and quality.

[0090] It can be understood that when the test data generation server does not store the first unit test case set, it means that the entire first software component is newly added, and the corresponding software interface function is also newly added. Since a software component is composed of one or more interface functions, the corresponding first software interface test case can be generated according to the newly added software interface functions under the first software component, and thus the first unit test case set of the first software component can be obtained.

[0091] Among them, after the test data generation server generates the first unit test case set, it will also store the first unit test case set to facilitate subsequent automated testing, improve subsequent testing efficiency, and enrich and improve the test cases stored in the test data generation server.

[0092] In the embodiment of the present application, when the test data generation server does not store the first unit test case set, the first unit test case set is automatically generated according to the first software component and the software interface function, without the need for the user to write test cases, thereby reducing testing costs.

[0093] In an optional embodiment, the interface function data includes: a function name, a judgment condition, and an output parameter; the step in which the test data generation server generates a first software interface test case according to the interface function data in step S10211 includes: the test data generation server generates a first software interface test case identifier according to the function name; generates a stub function according to the judgment condition; generates an expected result comparison function according to the output function; generates a first software interface test case according to the first software interface test case identifier, the stub function, and the expected result comparison function.

[0094] The role of the test case identifier is to provide a unique identifier, facilitate search and tracking, associate test requirements, record test results with test cases, and help improve the efficiency and quality of the test. Stub function (Stub) or stub code is a module that simulates the module being tested. In the vehicle system test, some "stand-in" modules that simulate the functions of its lower-level modules are compiled for the module being tested to replace the interface of the module being tested and accept or pass the data of the module being tested. These "fake" modules dedicated to testing are called stub modules of the module being tested. The expected result comparison function can be used to verify whether the function of the module being tested is correctly implemented. When the module being tested is executed, the expected result comparison function compares the actual result with the expected result. If the two are consistent, the test is considered to have passed; otherwise, the test is considered to have failed.

[0095] Taking the modified software data as the vehicle multimedia service (MediaServive) as an example, the test data generation server generates the first unit test case set identifier according to the name of the software component: MediaServiceTest; generates the first software interface test case identifier according to the function name: MediaFullScreen_001; generates a stub function according to the judgment condition: Mock_CheckMediaPlayerStatus(true); generates an expected value result comparison function according to the output function: EXPECT_TRUE(MediaFullScreen()), and then the generated first unit test case set can be obtained as:

[0096]

[0097] In the embodiment of the present application, according to the software interface function, interface function data is obtained, and thus the first software interface test case is automatically generated according to the interface function data, without the need for users to write, which can reduce the test cost and improve the test efficiency.

[0098] In an optional embodiment, if the test data generation server determines that the first unit test case set is stored, but the test case corresponding to the software interface function is not stored, then according to the software interface function, the corresponding source code is obtained from the third in-vehicle software data, and the interface function data is obtained according to the source code; according to the interface function data, the first software interface test case is generated; the first software interface test case is added to the first unit test case set to update the first unit test case set.

[0099] Among them, the method for generating the first software interface test case according to the interface function data is exactly the same as the foregoing, and will not be elaborated here.

[0100] When the test data generation server in the embodiment of the present application stores the first unit test case set, but does not store the test case corresponding to the software interface function, by automatically generating the first software interface test case and adding it to the first unit test case set for testing, the first unit test case set can be enriched to achieve a comprehensive test of the first software component unit.

[0101] In an optional embodiment, if the test data generation server determines that the second unit test case set corresponding to the second software component is not stored, then according to the name of the second software component, a second unit test case set identifier is generated; all software interface functions under the second software component are obtained, and according to all software interface functions under the second software component, the second software interface test case is generated; according to the second unit test case set identifier and the second software interface test case, the second unit test case set is obtained.

[0102] Among them, the method for generating the second software interface test case according to the interface function data is exactly the same as the foregoing, and will not be elaborated here.

[0103] In the embodiment of the present application, by automatically generating the second unit test case set without coding, the test efficiency can be improved.

[0104] In an optional embodiment, if the test data generation server determines that the first system test case set corresponding to the first software component is not stored, it generates a first system test case set identifier and a first application startup function of the application where the first software component is located according to the name of the first software component; obtains the first position coordinates of the first software component on the in-vehicle screen and generates a first resource data comparison function after touching the first software component according to the resource library; and generates the first system test case set by using the in-vehicle automation test tool according to the first system test case set identifier, the first application startup function, the first position coordinates, and the first resource data comparison function.

[0105] A system test case identifier is a unique identifier used to identify a system test case. It is usually composed of a specific set of characters or numbers and is used to distinguish different system test cases. The role of the system test case identifier is to assist in the management and tracking of system test cases. By using a unique identifier, confusion and duplication can be avoided, ensuring that each test case can be accurately identified and managed. An application startup function is a function that is called when an application starts, used to initialize the application and prepare its running environment. This function is usually defined in the main function of the application and is called when the program starts.

[0106] The resource library stores all the screen page information and audio information of the in-vehicle system. The screen page information includes the position coordinates of each software component within the in-vehicle screen, the visual resource information displayed on the current in-vehicle screen page, the visual resource information after jumping after triggering the software component, etc.; the audio information includes the audio that should be played on the current in-vehicle screen page, the audio after jumping after triggering the software component, etc.

[0107] An in-vehicle automation test tool is a type of tool specifically used to test in-vehicle systems, which can simulate different interactions between various protocols, including interface testing, protocol testing, security testing, etc. These tools can automatically execute test cases, improving the efficiency and accuracy of testing.

[0108] The in-vehicle automation test tool in the embodiment of the present application encapsulates various instruction sets specific to the in-vehicle system to simulate user operations on the in-vehicle system, including simulating in-vehicle interface touch click instructions, simulating in-vehicle interface sliding instructions, simulating in-vehicle action pauses, and taking screenshots of the current in-vehicle screen and comparing the expected screen instructions, etc.

[0109] Taking the modified software data of the in-vehicle multimedia service (MediaServive) as an example, the test data generation server generates the first system test case identifier: SYS_MediaServiceTest_001 according to the name of the first software component; generates the application start function of the application where the first software component is located according to the name of the first software component: AppStart(Media); finds the first coordinate position Touch(x,y) of the first software component according to the resource library; generates the first resource data comparison function ImageSameAs(MediaFullScreen) according to the screen after touching the touch software component, and then the first system test case set can be obtained as follows:

[0110] #SYS_MediaServiceTest_001

[0111] AppStart(Media)

[0112] Touch(x,y)

[0113] ImageSameAs(MediaFullScreen)

[0114] In the embodiment of the present application, through the test data generation server, according to the first software component, using the in-vehicle automation test tool, the first system test case is automatically generated, so that the in-vehicle system can directly perform tests according to the first system test case without compilation, improving the test efficiency.

[0115] In an optional embodiment, if the test data generation server determines that the second system test case set corresponding to the second software component is not stored, it generates the second system test case set identifier and the second application start function of the application where the second software component is located according to the name of the second software component; obtains the second position coordinates of the second software component on the in-vehicle screen and generates the second resource data comparison function after touching the second software component according to the resource library; generates the second system test case set by using the in-vehicle automation test tool according to the second system test case set identifier, the second application start function, the second position coordinates and the second resource data comparison function.

[0116] It can be understood that the generation method of the second system test case set is the same as that of the first system test case set, and the present application will not elaborate further.

[0117] In an optional embodiment, the in-vehicle automation test method further includes the following steps: the test server performs a static scan on the third in-vehicle software data to obtain a static scan test result.

[0118] The test server can use a third-party tool to perform a static scan on the third in-vehicle software code and obtain the static scan test results. Among them, static scanning is a software testing technique used to detect potential security vulnerabilities and coding errors in the code. It analyzes the source code or the compiled binary file to perform static analysis on the code and discover possible problems.

[0119] Optionally, after the in-vehicle device obtains the test results, it will upload them to the test server, and the test server will then send the test results feedback by the in-vehicle device and the static scan test results to the email stored by the test user, so as to facilitate the test user to view the test results in a timely manner.

[0120] In the embodiment of the present application, the test server performs a static scan on the third in-vehicle software data to obtain the static scan test results, which can detect potential vulnerabilities and coding error problems in the code in a timely manner.

[0121] In an optional embodiment, the step in step S104 where the in-vehicle device updates the in-vehicle software according to the automated test script according to the third in-vehicle software data and tests the updated in-vehicle software according to the in-vehicle unit test data and the in-vehicle system test data to obtain the test results includes: the in-vehicle device updates the in-vehicle software according to the automated test script according to the third in-vehicle software data, performs software component testing on the updated in-vehicle software according to the in-vehicle unit test data, and obtains the unit test results; and tests the updated in-vehicle software according to the in-vehicle system test data to obtain the system test results.

[0122] In the embodiment of the present application, by performing software component testing on the updated in-vehicle software according to the in-vehicle unit test data to obtain the unit test results, and then testing the updated in-vehicle software according to the in-vehicle system test data to obtain the system test results, when an error occurs in the third in-vehicle software code, it is possible to first determine from the unit test results whether there is a problem with the component code itself, and then determine from the system test results whether there is a problem with the interaction of the component among the entire system, so as to quickly locate the problems that occur in the test.

[0123] Please refer to Figure 4 , which is the in-vehicle device automated test method provided by the second embodiment of the present application, and includes the following steps:

[0124] Step S201: When the in-vehicle software data changes, obtain the first in-vehicle software data; among them, the first in-vehicle software data is used to indicate the newly added or modified software code data between the changed third in-vehicle software data and the second in-vehicle software data before the change; the first in-vehicle software data includes at least one software interface function and the software components related to the software interface function;

[0125] Step S202: Obtain in-vehicle unit test data and in-vehicle system test data according to software interface functions and software components;

[0126] Step S203: Send the automated test script, in-vehicle unit test data, in-vehicle system test data, and third in-vehicle software data to the in-vehicle unit, so that the in-vehicle unit updates the in-vehicle software according to the third in-vehicle software based on the automated test script, and tests the updated in-vehicle software according to the in-vehicle unit test data and the in-vehicle system test data to obtain test results.

[0127] The in-vehicle unit automated test method provided in the second embodiment of the present application can be executed by a test server as the execution entity. At this time, the test server can obtain the in-vehicle unit test data by itself according to software components and software interface functions, or send the software components and software interface functions to a test data generation server to obtain the in-vehicle unit test data. The in-vehicle unit automated test method provided in the second embodiment of the present application can also be executed by a test data generation server as the execution entity. At this time, the test data generation server directly interacts with the in-vehicle unit, and the test data generation server directly sends the in-vehicle unit test data, system test data, automated test script, and third in-vehicle software data to the in-vehicle unit.

[0128] The in-vehicle unit automated test method provided in the second embodiment of the present application and the in-vehicle unit automated test method provided in the first embodiment belong to the same concept. The implementation process is shown in the method embodiment and will not be elaborated here.

[0129] Please refer to Figure 5 , which is a schematic structural diagram of an in-vehicle unit automated test device provided in the third embodiment of the present application. The device 300 includes:

[0130] A software data acquisition module 301, configured to acquire first in-vehicle software data when the in-vehicle software data changes; wherein, the first in-vehicle software data is used to indicate the newly added or modified software code data between the changed third in-vehicle software data and the previous second in-vehicle software data; the first in-vehicle software data includes at least one software interface function and software components related to the software interface function;

[0131] A test data acquisition module 302, configured to obtain in-vehicle unit test data and in-vehicle system test data according to software interface functions and software components;

[0132] A test data sending module 303, configured to send the automated test script, in-vehicle unit test data, in-vehicle system test data, and third in-vehicle software data to the in-vehicle unit, so that the in-vehicle unit updates the in-vehicle software according to the third in-vehicle software based on the automated test script, and tests the updated in-vehicle software according to the in-vehicle unit test data and the in-vehicle system test data to obtain test results.

[0133] It should be noted that when the in-vehicle infotainment (IVI) system automated test device provided in the third embodiment of the present application executes the IVI system automated test method, only the above division of each functional module is used for illustration. In actual applications, the above functions can be allocated to different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the IVI system automated test device provided in the third embodiment of the present application and the IVI system automated test method in the first embodiment of the present application belong to the same concept. The implementation process is described in detail in the method embodiment and will not be repeated here.

[0134] The embodiment of the IVI system automated test device in the third embodiment of the present application can be applied to a computer device, such as a test server or a test generation server. This device embodiment can be implemented by software, or by hardware, or by a combination of software and hardware. Taking software implementation as an example, as a logically meaningful device, it is formed by the processor in the file processing reading the corresponding computer program instructions in the memory and running. From the hardware level, the computer device where it is located can include a processor and a memory, and the processor and the memory are connected and communicated through a data bus or other well-known methods.

[0135] Please refer to Figure 6 , which is a schematic structural diagram of an electronic device provided in the fourth embodiment of the present application. As Figure 6 shown, the electronic device 400 can specifically be a computer, a mobile phone, a tablet computer, an interactive tablet, etc. The electronic device 400 can include: at least one processor 410, at least one memory 420, at least one display 430, at least one network interface 440, a user interface 450, and at least one communication bus 460.

[0136] Among them, the communication bus 460 is used to realize the connection and communication between these components.

[0137] Among them, the user interface 450 can include a camera; the user interface 450 can also include a standard wired interface and a wireless interface.

[0138] Among them, the network interface 440 can optionally include a standard wired interface and a wireless interface (such as a WI-FI interface).

[0139] Among them, the processor 410 may include one or more processing cores. The processor 410 connects various parts within the entire electronic device 400 through various interfaces and lines, and executes various functions of the electronic device 400 and processes data by running or executing instructions, programs, code sets, or instruction sets stored in the memory 420, and by calling the data stored in the memory 420. Optionally, the processor 410 may be implemented in at least one hardware form of digital signal processing (DSP), field-programmable gate array (FPGA), or programmable logic array (PLA). The processor 410 may integrate a combination of one or several of a central processing unit (CPU), a graphics processing unit (GPU), and a modem, etc. Among them, the CPU mainly processes the operating system, user interface, application programs, etc.; the GPU is responsible for rendering and drawing the content to be displayed in the display layer; the modem is used to process wireless communications. It can be understood that the above-mentioned modem may not be integrated into the processor 410 and may be implemented separately by a single chip.

[0140] Among them, the memory 420 may include random access memory (RAM) and may also include read-only memory. Optionally, the memory 420 includes a non-transitory computer-readable storage medium. The memory 420 can be used to store instructions, programs, code, code sets, or instruction sets. The memory 420 may include a program storage area and a data storage area. Among them, the program storage area may store instructions for implementing the operating system, instructions for at least one function (such as touch function, sound playback function, image playback function, etc.), instructions for implementing the above-mentioned various method embodiments, etc.; the data storage area may store the data involved in the above-mentioned various method embodiments. Optionally, the memory 420 may also be at least one storage device located far from the aforementioned processor 410. As Figure 6 shown, the memory 420, as a computer storage medium, may include an operating system, a network communication module, and a user.

[0141] In Figure 6In the electronic device 400 shown, the user interface 450 is mainly used to provide an interface for the user to input and obtain the data input by the user; and the processor 410 can be used to call the operation application program stored in the memory 420, for example: the in-vehicle automation test program; and execute the relevant operations of any in-vehicle automation test method in the above embodiments, and has the corresponding functions and beneficial effects.

[0142] The fourth embodiment of the present application also provides a computer-readable storage medium, on which a computer program is stored, and the instructions are suitable for being loaded and executed by the processor to perform the steps of the in-vehicle automation test method shown above. The specific execution process can refer to the specific description shown in the embodiment and will not be elaborated here. The device where the storage medium is located can be an electronic device such as a personal computer, a laptop computer, a smart phone, a tablet computer, etc.

[0143] For the device embodiment, since it basically corresponds to the method embodiment, the relevant parts can refer to the partial description of the method embodiment. The device embodiments described above are only illustrative. The components described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed to multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of the present application. Those of ordinary skill in the art can understand and implement it without creative work.

[0144] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0145] The present application is described with reference to the flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each flow and / or block in the flowchart and / or block diagram can be implemented by computer program instructions, and the combination of the flows and / or blocks in the flowchart and / or block diagram can also be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing devices generate for implementing in the process Figure 1 one process or multiple processes and / or blocks Figure 1means for selected functions in one or more blocks. These computer program instructions can also be stored in a computer-readable memory capable of guiding a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured article including an instruction means, and the instruction means implements in the process Figure 1 one process or more processes and / or blocks Figure 1 selected functions in one block or more blocks.

[0146] These computer program instructions can also be loaded onto a computer or other programmable data processing device, so that a series of operation steps are executed on the computer or other programmable device to generate a computer-implemented process, and thus the instructions executed on the computer or other programmable device provide for implementing in the process Figure 1 one process or more processes and / or blocks Figure 1 steps for selected functions in one block or more blocks.

[0147] In a typical configuration, a computing device includes one or more processors (CPUs), an input / output interface, a network interface, and memory.

[0148] The memory may include non-permanent memory in computer-readable media, in the form of random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.

[0149] Computer-readable media includes permanent and non-permanent, removable and non-removable media and can be implemented by any method or technology for information storage. The information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette tapes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission media that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media, such as modulated data signals and carrier waves.

[0150] It should also be noted that the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, such that a process, method, commodity or device comprising a series of elements not only includes those elements but also includes other elements not expressly listed, or further includes elements inherent to such process, method, commodity or device. Without further limitation, an element defined by the statement "comprising one..." does not exclude the presence of additional identical elements in the process, method, commodity or device comprising the element.

[0151] The above are only embodiments of the present application and are not intended to limit the present application. For those skilled in the art, various changes and modifications can be made to the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included within the scope of the claims of the present application.

Claims

1. A method for automated testing of a vehicle-mounted computer, characterized in that, The method includes the following steps: When the in-vehicle software data changes, the test server obtains the first in-vehicle software data and sends the first in-vehicle software data to the test data generation server; wherein, the first in-vehicle software data is used to indicate the newly added or modified software code data between the changed third in-vehicle software data and the previous second in-vehicle software data; the first in-vehicle software data includes at least one software interface function and software components related to the software interface function; The test data generation server obtains in-vehicle unit test data and in-vehicle system test data according to the software interface function and the software components; and sends the in-vehicle unit test data and the in-vehicle system test data to the test server; The test server sends the automated test script, the in-vehicle unit test data, the in-vehicle system test data, and the third in-vehicle software data to the in-vehicle unit; The in-vehicle unit updates the in-vehicle software according to the automated test script and the third in-vehicle software data, and tests the updated in-vehicle software according to the in-vehicle unit test data and the in-vehicle system test data to obtain a test result.

2. The in-vehicle automation test method according to claim 1, characterized in that: The software components include a first software component where the interface function is located and a second software component associated with the first software component; The step in which the test data generation server obtains the in-vehicle unit test data and the in-vehicle system test data according to the software interface function and the software components includes: The test data generation server determines whether there is a first unit test case set corresponding to the first software component stored. If there is, it determines whether there is a test case corresponding to the software interface function stored in the first unit test case set. If there is, it obtains the stored first unit test case set; determines whether there is a second unit test case set corresponding to the second software component stored. If there is, it obtains the stored second unit test case set; and obtains the in-vehicle unit test data according to the first unit test case set and the second unit test case set; The test data generation server determines whether there is a first system test case set corresponding to the first software component stored. If there is, it obtains the stored first system test case set; determines whether there is a second system test case set corresponding to the second software component stored. If there is, it obtains the stored second system test case set; and obtains the in-vehicle system test data according to the first system test case set and the second system test case set.

3. The in-vehicle automation test method according to claim 2, characterized in that: If the test data generation server determines that the first unit test case set corresponding to the first software component is not stored, it generates a first unit test case set identifier according to the name of the first software component; obtains the corresponding source code from the third in-vehicle software data according to the software interface function, and obtains interface function data from the source code; generates a first software interface test case according to the interface function data; and obtains a first unit test case set according to the first unit test case set identifier and the first software interface test case.

4. The in-vehicle automation test method according to claim 3, wherein: The interface function data includes: function name, judgment condition, and output parameter; the step of the test data generation server generating a first software interface test case according to the interface function data includes: The test data generation server generates a first software interface test case identifier according to the function name; generates a stub function according to the judgment condition; generates an expected result comparison function according to the output function; and generates a first software interface test case according to the first software interface test case identifier, the stub function, and the expected result comparison function.

5. The in-vehicle automation test method according to claim 3, wherein: If the test data generation server determines that the first unit test case set is stored but the test case corresponding to the software interface function is not stored, it obtains the corresponding source code from the third in-vehicle software data according to the software interface function, and obtains interface function data from the source code; generates a first software interface test case according to the interface function data; adds the first software interface test case to the first unit test case set, and updates the first unit test case set.

6. The in-vehicle automation test method according to claim 3, wherein: If the test data generation server determines that the first system test case set corresponding to the first software component is not stored, it generates a first system test case set identifier and a first application start function of the application where the first software component is located according to the name of the first software component; obtains a first position coordinate of the first software component on the in-vehicle screen and generates a first resource data comparison function after touching the first software component from the resource library; and generates a first system test case set by using an in-vehicle automation test tool according to the first system test case set identifier, the first application start function, the first position coordinate, and the first resource data comparison function.

7. The in-vehicle automation test method according to any one of claims 1 to 6, wherein: The step of the in-vehicle device updating the in-vehicle software according to the automation test script, testing the updated in-vehicle software according to the in-vehicle unit test data and the in-vehicle system test data, and obtaining a test result includes: The in-vehicle unit updates the in-vehicle unit software according to the automated test script and the third in-vehicle unit software data, and performs software component testing on the updated in-vehicle unit software according to the in-vehicle unit test data to obtain unit test results; and tests the updated in-vehicle unit software according to the in-vehicle unit system test data to obtain system test results.

8. The vehicle-mounted computer automated test method according to any one of claims 1 to 6, characterized in that It further includes the following steps: The test server performs a static scan on the third in-vehicle unit software data to obtain static scan test results.

9. A vehicle-mounted computer automated testing method, characterized in that, It includes the following steps: When the in-vehicle unit software data changes, obtain the first in-vehicle unit software data; wherein, the first in-vehicle unit software data is used to indicate the newly added or modified software code data between the changed third in-vehicle unit software data and the second in-vehicle unit software data before the change; the first in-vehicle unit software data includes at least one software interface function and the software components related to the software interface function; According to the software interface function and the software components, obtain in-vehicle unit test data and in-vehicle unit system test data; Send the automated test script, the in-vehicle unit test data, the in-vehicle unit system test data, and the third in-vehicle unit software data to the in-vehicle unit, so that the in-vehicle unit updates the in-vehicle unit software according to the automated test script and the third in-vehicle unit software, and tests the updated in-vehicle unit software according to the in-vehicle unit test data and the in-vehicle unit system test data to obtain test results.

10. An in-vehicle infotainment (IVI) system automated test device, characterized in that, It includes: A software data acquisition module, configured to obtain the first in-vehicle unit software data when the in-vehicle unit software data changes; wherein, the first in-vehicle unit software data is used to indicate the newly added or modified software code data between the changed third in-vehicle unit software data and the second in-vehicle unit software data before the change; the first in-vehicle unit software data includes at least one software interface function and the software components related to the software interface function; A test data acquisition module, configured to obtain in-vehicle unit test data and in-vehicle unit system test data according to the software interface function and the software components; A test data sending module, configured to send the automated test script, the in-vehicle unit test data, the in-vehicle unit system test data, and the third in-vehicle unit software data to the in-vehicle unit, so that the in-vehicle unit updates the in-vehicle unit software according to the automated test script and the third in-vehicle unit software, and tests the updated in-vehicle unit software according to the in-vehicle unit test data and the in-vehicle unit system test data to obtain test results.

11. An electronic device, comprising a processor and a memory; characterized in that, The memory stores a computer program, and the computer program is suitable for being loaded and executed by the processor to perform the in-vehicle unit automated test method according to any one of claims 1 to 9.

12. A computer-readable storage medium storing a computer program thereon, characterized in that, When the computer program is executed by the processor, it implements the in-vehicle unit automated test method according to any one of claims 1 to 9.

Images