Testing methods for software call information, electronic devices and vehicles

Abstract

This disclosure relates to the field of data processing technology, providing a method for testing software call information, an electronic device, and a vehicle. The method includes: establishing a first preset mapping relationship between vehicle execution functions and software components, and a second preset mapping relationship between software components and interface signals; during the integration of the software under test, acquiring the call information of the software under test, and testing the call information based on the first and second preset mapping relationships to obtain test results. In this way, the software under test is tested during the integration process, eliminating the need to test it again after integration, thus avoiding the problem of excessively long development time for the software under test when it malfunctions.

Description

Technical Field

[0001] This disclosure relates to the field of data processing technology, and in particular to a test method for software calling information, an electronic device, and a vehicle. Background Technology

[0002] As vehicle functions become increasingly complex, the amount of software code grows rapidly, making software testing essential during development. However, after software integration, testing reveals anomalies. Testers report these anomalies to developers for fixing, and the software is then integrated again until testing passes. This process of multiple integrations and tests leads to excessively long software development times.

[0003] Therefore, how to avoid excessive software development time due to multiple software integrations and tests has become an urgent technical problem to be solved. Summary of the Invention

[0004] In view of this, the purpose of this disclosure is to provide a testing method, electronic device and vehicle for software call information, so as to solve the problem that the software development time is too long due to multiple software integrations and software tests in the prior art.

[0005] To achieve the above objectives, the first aspect of this disclosure provides a method for testing software call information, the method comprising:

[0006] Establish a first preset mapping relationship between vehicle execution functions and software components, and a second preset mapping relationship between software components and interface signals;

[0007] During the integration process of the software under test, the calling information of the software under test is obtained, and the calling information is tested based on the first preset mapping relationship and the second preset mapping relationship to obtain test results.

[0008] Based on the same inventive concept, a second aspect of this disclosure proposes an electronic device including a memory, a processor, and a computer program stored in the memory and executable by the processor, wherein the processor implements the method described above when executing the computer program.

[0009] Based on the same inventive concept, a third aspect of this disclosure proposes a vehicle that includes the electronic equipment described in the second aspect.

[0010] As described above, this disclosure provides a method for testing software call information, an electronic device, and a vehicle. It establishes a first preset mapping relationship between vehicle execution functions and software components, and a second preset mapping relationship between software components and interface signals. During the integration of the software under test, the call information of the software under test is acquired, and the call information is tested based on the first and second preset mapping relationships to obtain test results. This allows testing of the software under test during integration, eliminating the need to test it again after integration, thus avoiding the problem of excessively long development times when the software under test malfunctions. Furthermore, the first and second preset mapping relationships store correct call information, making the test results more accurate when testing the call information of the software under test based on these relationships. Attached Figure Description

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

[0012] Figure 1 This is a flowchart of a method for testing software call information according to an embodiment of the present disclosure;

[0013] Figure 2 This is a schematic diagram of the structure of a testing device for software call information according to an embodiment of the present disclosure;

[0014] Figure 3 This is a schematic diagram of the structure of an electronic device according to an embodiment of the present disclosure. Detailed Implementation

[0015] To make the objectives, technical solutions, and advantages of this disclosure clearer, the following detailed description is provided in conjunction with specific embodiments and the accompanying drawings.

[0016] It should be noted that, unless otherwise defined, the technical or scientific terms used in the embodiments of this disclosure should have the ordinary meaning understood by one of ordinary skill in the art to which this disclosure pertains. The terms "first," "second," and similar terms used in the embodiments of this disclosure do not indicate any order, quantity, or importance, but are merely used to distinguish different components. Terms such as "comprising" or "including" mean that the element or object preceding the word encompasses the elements or objects listed following the word and their equivalents, without excluding other elements or objects. Terms such as "connected" or "linked" are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. Terms such as "upper," "lower," "left," and "right" are used only to indicate relative positional relationships; when the absolute position of the described object changes, the relative positional relationship may also change accordingly.

[0017] Based on the background description, as vehicle functions become increasingly complex, the amount of software code is growing rapidly. The Vehicle Control Unit (VCU), as the core of the vehicle's electronic system, also has a massive amount of software code. In the software development process, identifying problems early can accelerate software release, significantly improve work efficiency, and reduce software failure rates and maintenance costs.

[0018] The large amount of code increases the failure rate of VCU software, with communication failures being a common one. One cause of communication failures is incorrect signal mapping at the interfaces between software modules. In the current software development process, interface signal mapping errors are discovered during integration testing. After an anomaly is found, testers report it to software developers for problem analysis, fix the software, and then re-integrate it. This process is repeated until the tests pass. Given the current size of the VCU software codebase, software integration is time-consuming, taking approximately two hours per integration. If the software fixes do not completely resolve the problem or introduce new issues, it will inevitably lead to multiple integrations and tests, multiplying the software development time.

[0019] As mentioned above, how to avoid excessive software development time due to multiple software integrations and tests has become an important research issue.

[0020] Based on the above description, such as Figure 1 As shown in this embodiment, the method for testing software call information includes:

[0021] Step 101: Establish a first preset mapping relationship between vehicle execution functions and software components, and a second preset mapping relationship between software components and interface signals.

[0022] In practice, vehicle execution functions refer to the application functions that a vehicle can perform. For example, vehicle execution functions include at least one of the following: thermal management functions, driver assistance functions, entertainment functions, and safety functions.

[0023] Software components are an important concept in software development, analogous to chips in hardware. They have certain standards, such as input / output formats, the number and types of parameters, etc. A software component is the deployment unit of software; it is the smallest entity / unit that can independently complete the deployment of the entire software system. Specifically, it manifests as a set of binary files or source code files in a compiled and runnable language.

[0024] Interface signals are detailed specifications of electrical characteristics, logic levels, timing parameters, etc., used to identify and synchronize signals when transmitting data between different devices or systems.

[0025] Specifically, when the vehicle performs a thermal management function, the corresponding software components include electronic water pump control, four-way valve control, and battery heating / cooling control. The first preset mapping relationship is the correspondence between the thermal management function and the electronic water pump control, four-way valve control, and battery heating / cooling control. When the software component is electronic water pump control, the corresponding interface signals include opening degree request signal, actual opening degree feedback signal, target speed signal, and actual speed feedback signal. The second preset mapping relationship is the correspondence between electronic water pump control and the opening degree request signal, actual opening degree feedback signal, target speed signal, and actual speed feedback signal.

[0026] The storage format of the first preset mapping relationship and the second preset mapping relationship includes at least one of the following: binary tree, hash table, and table.

[0027] Step 102: During the integration process of the software under test, the calling information of the software under test is obtained, and the calling information is tested based on the first preset mapping relationship and the second preset mapping relationship to obtain the test results.

[0028] In practice, the software under test is the software that needs to be integrated and tested during the software development process.

[0029] During the integration process of the software under test, the calling information of the software under test is obtained. The calling information includes: the first mapping relationship between the vehicle execution function of the software under test and the software components, and the second mapping relationship between the software components of the software under test and the interface signals.

[0030] The first mapping relationship to be tested is compared with the first preset mapping relationship. When the first mapping relationship to be tested and the first preset mapping relationship are consistent, the first mapping relationship to be tested in the software under test is determined to have passed the test. When the first mapping relationship to be tested and the first preset mapping relationship are inconsistent, the first mapping relationship to be tested in the software under test is determined to be abnormal.

[0031] The second mapping relationship to be tested is compared with the second preset mapping relationship. If the second mapping relationship to be tested matches the second preset mapping relationship, the second mapping relationship to be tested in the software under test is deemed to have passed the test. If the second mapping relationship to be tested does not match the second preset mapping relationship, the second mapping relationship to be tested in the software under test is deemed to have an error (abnormality).

[0032] Through the above embodiments, a first preset mapping relationship between vehicle execution functions and software components, and a second preset mapping relationship between software components and interface signals are established. During the integration of the software under test, the calling information of the software under test is obtained, and the calling information is tested based on the first and second preset mapping relationships to obtain test results. In this way, the software under test is tested during the integration process, eliminating the need to test it again after integration. This avoids the problem of excessively long development time for the software under test when it malfunctions. Furthermore, the first and second preset mapping relationships store correct calling information, and testing the calling information of the software under test based on these relationships results in more accurate test results.

[0033] In some embodiments, step 101 includes:

[0034] Step 1011: Obtain the vehicle execution function identifier, software component identifier, and interface signal identifier.

[0035] Step 1012: Based on the vehicle execution function identifier and the software component identifier, establish a first preset mapping relationship between the vehicle execution function and the software component.

[0036] Step 1013: Based on the software component identifier and the interface signal identifier, establish a second preset mapping relationship between the software component and the interface signal.

[0037] In practice, the vehicle's execution function identifier, software component identifier, and interface signal identifier are acquired. Based on the vehicle's execution function identifier and software component identifier, a first preset mapping relationship between the vehicle's execution function and the software component is established. Based on the software component identifier and interface signal identifier, a second preset mapping relationship between the software component and the interface signal is established.

[0038] For example, when the vehicle is performing a thermal management function, the acquired vehicle function identifier is the thermal management function identifier, and the acquired software component identifiers are the electronic water pump control identifier, the four-way valve control identifier, and the battery heating / cooling control identifier. Based on the thermal management function identifier, the electronic water pump control identifier, the four-way valve control identifier, and the battery heating / cooling control identifier, a first preset mapping relationship is established between the thermal management function and the electronic water pump control, the four-way valve control, and the battery heating / cooling control.

[0039] When the software component is an electronic water pump control, the acquired software component identifier is the electronic water pump control identifier, and the acquired interface signal identifiers are the opening gear request signal identifier, the actual opening feedback signal identifier, the target speed signal identifier, and the actual speed feedback signal identifier. Based on the electronic water pump control identifier, the opening gear request signal identifier, the actual opening feedback signal identifier, the target speed signal identifier, and the actual speed feedback signal identifier, a second preset mapping relationship is established between the electronic water pump control and the opening gear request signal, the actual opening feedback signal, the target speed signal, and the actual speed feedback signal.

[0040] By acquiring the vehicle's execution function identifier, software component identifier, and interface signal identifier through the above scheme, an identity can be established for each vehicle execution function, software component, and interface signal. This ensures accurate referencing and identification during the establishment of the first and second preset mapping relationships, thereby enabling the rapid and accurate establishment of both relationships.

[0041] In some embodiments, step 102 includes:

[0042] Step 1021: Create a preset script based on the first preset mapping relationship and the second preset mapping relationship, and embed the preset script into the software integration tool.

[0043] Step 1022: During the integration process of the software under test, the preset script is used to collect the call information of the software under test, and the software integration tool is used to test the call information to obtain test results.

[0044] In practice, a preset script is created based on the first and second preset mapping relationships. The function of the preset script is to automatically collect the call information of interface signals during the integration of the software under test and mark them one by one.

[0045] The preset script is embedded into the software integration tool (which combines the underlying software and the application layer software into one software version) to enable self-diagnosis of the call information of interface signals during the integration process of the software under test.

[0046] The above scheme involves creating a preset script based on a first and a second preset mapping relationship. This preset script stores both the first and second preset mapping relationships, enabling accurate collection of the call information from the software under test. The preset script is then embedded into a software integration tool, which in turn stores the first and second preset mapping relationships. This allows the software integration tool to accurately test the call information of the software under test during the integration process.

[0047] In some embodiments, step 1022 includes:

[0048] Step 10221: During the integration process of the software under test, the call information of the software under test is collected using the preset script.

[0049] Step 10222: Analyze and process the call information to obtain the first mapping relationship between the vehicle execution function and software components of the software under test, and the second mapping relationship between the software components and interface signals of the software under test.

[0050] Step 10223: Determine the target mapping relationship to be tested from the first mapping relationship to be tested and the second mapping relationship to be tested, and use the software integration tool to test the target mapping relationship to be tested to obtain the test result.

[0051] In practice, during the integration of the software under test, a preset script is used to collect the calling information of the software under test. This calling information includes: a first mapping relationship between the vehicle execution functions of the software under test and its software components, and a second mapping relationship between the software components of the software under test and their interface signals.

[0052] The call information of the software under test is analyzed and processed to obtain the first and second mapping relationships to be tested. The first and second mapping relationships to be tested are then tested to obtain the test results.

[0053] In some scenarios, to ensure accurate testing of the calling information of the software under test while saving testing time, it is sufficient to test only the second mapping relationship to be tested. In other scenarios, to ensure accurate testing of the calling information of the software under test, it is necessary to test both the first and second mapping relationships to be tested.

[0054] Based on the above reasons, a target mapping relationship is determined from the first and second mapping relationships to be tested, and the target mapping relationship is tested using a software integration tool to obtain test results. Specifically, the target preset mapping relationship is called from the first and second preset mapping relationships using the software integration tool. The target mapping relationship to be tested and the target preset mapping relationship are compared. When the target mapping relationship to be tested and the target preset mapping relationship are consistent, the calling information test of the software under test is deemed to have passed. When the target mapping relationship to be tested and the target preset mapping relationship are inconsistent, the calling information of the software under test is deemed to contain errors.

[0055] By analyzing and processing the call information of the software under test using the above method, the first and second mapping relationships to be tested can be accurately obtained. The target mapping relationship to be tested is then determined from the first and second mapping relationships, and software integration tools are used to test the target mapping relationship to obtain the test results. This approach ensures accurate testing of the call information of the software under test while saving testing time.

[0056] In some embodiments, step 10223 includes:

[0057] Step 102231: Determine whether the software under test is being tested for the first time.

[0058] Step 102232: In response to determining that the software under test is being tested for the first time, the first mapping relationship under test and the second mapping relationship under test are used as target mapping relationships under test.

[0059] Step 102233: In response to determining that the software under test is not being tested for the first time, the target mapping relationship is determined from the first mapping relationship and the second mapping relationship by judging whether the software architecture of the software under test has changed.

[0060] In practice, in order to accurately determine whether the first mapping relationship to be tested needs to be tested in the current scenario, to determine whether the software under test is being tested for the first time, and based on the determination results, to determine the target mapping relationship to be tested from the first mapping relationship to be tested and the second mapping relationship to be tested, and to use software integration tools to test the target mapping relationship to be tested to obtain the test results.

[0061] When the software under test is being tested for the first time, to ensure the accuracy of the test results, the first and second mapping relationships to be tested are used as target mapping relationships to be tested. In this way, when the software under test is being tested for the first time, both the first and second mapping relationships to be tested can be performed, thus enabling a comprehensive test of the software's calling information and ensuring the accuracy of the test results.

[0062] When the software under test is not being tested for the first time, it means that the first mapping relationship to be tested has already passed the test. To save testing time, the second mapping relationship to be tested is used as the target mapping relationship to be tested. In this way, when the software under test is not being tested for the first time, only the second mapping relationship to be tested can be tested, thereby saving testing time while ensuring the accuracy of the test results.

[0063] In some scenarios, in order to more accurately determine whether the first mapping relationship to be tested needs to be tested in the current scenario, when the software under test is not being tested for the first time, it is determined whether the software architecture of the software under test has changed, and based on the determination result, the target mapping relationship to be tested is determined from the first mapping relationship to be tested and the second mapping relationship to be tested.

[0064] The above scheme, by determining whether the software under test (TBT) is being tested for the first time, can accurately identify the target TBT mapping relationship to be tested from the first and second TBT mapping relationships. When the TBT is being tested for the first time, using both the first and second TBT mapping relationships as the target TBT mapping relationships allows for testing of both, thus enabling comprehensive testing of the TBT's call information and ensuring the accuracy of the test results. When the TBT is not being tested for the first time, using the second TBT mapping relationship as the target TBT mapping relationship allows for testing only the second TBT mapping relationship, thereby saving testing time while ensuring the accuracy of the test results.

[0065] In some embodiments, step 102233 includes:

[0066] Step 1022331: Determine whether the software architecture of the software under test has changed.

[0067] Step 1022332: In response to determining that the software architecture of the software under test has changed, the first mapping relationship and the second mapping relationship are used as the target mapping relationship to be tested.

[0068] Step 1022333: In response to determining that the software architecture of the software under test has not changed, the second mapping relationship is used as the target mapping relationship to be tested.

[0069] In practice, in order to more accurately determine whether the first mapping relationship to be tested needs to be tested in the current scenario, when the software under test is not being tested for the first time, it is determined whether the software architecture of the software under test has changed. Based on the determination result, the target mapping relationship to be tested is determined from the first mapping relationship to be tested and the second mapping relationship to be tested. The target mapping relationship to be tested is then tested using software integration tools to obtain the test results.

[0070] When the software architecture of the software under test changes, to ensure the accuracy of the test results, the first and second mapping relationships under test are used as target mapping relationships under test. This way, when the software architecture changes, both the first and second mapping relationships under test can be tested, enabling comprehensive testing of the software under test's call information and ensuring the accuracy of the test results.

[0071] When the software under test (SUB) is not being tested for the first time and its software architecture has not changed, it means that the first mapping relationship under test has passed the test and the software architecture has not changed. To save testing time, the second mapping relationship under test is used as the target mapping relationship. In this way, when the software under test is not being tested for the first time and its software architecture has not changed, only the second mapping relationship under test can be tested, thereby saving testing time while ensuring the accuracy of the test results.

[0072] The above scheme, by determining whether the software architecture of the software under test has changed, can accurately identify the target mapping relationship to be tested from the first and second mapping relationships. When the software architecture of the software under test has changed, using both the first and second mapping relationships as the target mapping relationships allows for testing of both, thus enabling comprehensive testing of the software under test's call information and ensuring the accuracy of the test results. When the software architecture of the software under test has not changed, using the second mapping relationship as the target mapping relationship allows for testing only the second mapping relationship, thereby saving testing time while ensuring the accuracy of the test results.

[0073] In some embodiments, step 1022 includes:

[0074] Step 1022A: Use the preset script embedded in the software integration tool to mark the call information.

[0075] Step 1022B: In response to determining that there is a missing or incorrect marker, the test result is determined to be erroneous, and the software under test is repaired.

[0076] In practice, a preset script embedded in the software integration tool is used to retrieve the first and second preset mapping relationships. Based on the first and second preset mapping relationships, the mapping relationship to be tested in the call information is tested. When the mapping relationship to be tested matches the first and second preset mapping relationships, the call information is marked.

[0077] If a marker is missing or incorrect, it indicates an error in the call information. When the call information of the software under test is incorrect, the integration of the software under test is paused, and an error message is displayed in a pop-up window to assist developers in fixing the software under test.

[0078] The above solution can accurately detect errors in the calling information of the software under test when there are missing or incorrect markings, so that the software under test can be repaired in a timely manner.

[0079] In some embodiments, step 1022B includes:

[0080] Step 1022Ba: If the test result indicates an error, stop integrating the software under test.

[0081] Step 1022Bb: Repair the calling information of the software under test, and determine whether the calling information of the software under test has been repaired.

[0082] Step 1022Bc: In response to determining that the call information of the software under test has been repaired, continue to integrate the software under test, and test the software under test during the integration process.

[0083] In practice, if there is an error in the calling information of the software under test, the integration of the software under test is stopped by triggering the integration pause of the software under test.

[0084] Error messages are displayed via pop-up windows to identify the location of the error in the software under test. The updated mapping relationship corresponding to the error location is obtained from the first and second preset mapping relationships. The error location in the software under test is directly replaced with the updated mapping relationship, thereby repairing the call information of the software under test.

[0085] Determine if the call information of the software under test has been repaired. Once the call information of the software under test has been repaired, continue integrating the software under test, and test the software under test during the integration process until the integration of the software under test is complete.

[0086] The above solution allows for the convenient repair of errors in the call information of the software under test (SDT) by halting the integration process. By directly replacing the erroneous locations in the SDT with updated mappings, the call information can be repaired quickly and accurately. After the call information is repaired, integration can resume. This allows testing to be performed during the integration process, requiring only one integration operation and saving development time.

[0087] Through the above embodiments, a first preset mapping relationship between vehicle execution functions and software components, and a second preset mapping relationship between software components and interface signals are established. During the integration of the software under test, the calling information of the software under test is obtained, and the calling information is tested based on the first and second preset mapping relationships to obtain test results. In this way, the software under test is tested during the integration process, eliminating the need to test it again after integration. This avoids the problem of excessively long development time for the software under test when it malfunctions. Furthermore, the first and second preset mapping relationships store correct calling information, and testing the calling information of the software under test based on these relationships results in more accurate test results.

[0088] It should be noted that the embodiments of this disclosure can also be further described in the following ways:

[0089] Step 1: Establish identity identifiers for each function and software component to ensure accurate referencing and identification.

[0090] Step 2: Establish the first preset mapping relationship between each function and software component, and the second preset mapping relationship between the software component and the interface signal (Excel table); for example, the thermal management function includes electronic water pump control, four-way valve control, battery heating / cooling control, etc., so the thermal management function and the aforementioned three control components are established as the first preset mapping relationship; for example, the interface signals between the electronic water pump control and the VCU include opening position request signal, actual opening feedback signal, target speed signal, and actual speed feedback signal, so the electronic water pump control software component and these four interface signals are established as the second preset mapping relationship.

[0091] Step 3: Based on the first and second preset mapping relationships from Steps 1 and 2, create a preset script (i.e., an automated script, whose function is to automatically collect the call information of interface signals during the integration of the software under test and mark them one by one. The preset script is written by engineers) and embed it into the software integration tool (which combines the underlying and application layer software into one software version). This enables self-diagnosis of the call information of interface signals during the integration of the software under test (the first test mapping relationship will be checked when the software under test is integrated for the first time and the architecture of the software under test changes; otherwise, only the second test mapping relationship will be checked. During the integration of the software under test, after a matching relationship is established between the interface of one component in the underlying software and the interface of another component in the application layer software, the preset script will compare the matching result with the first and second preset mapping relationships in the Excel table in Step 2 and mark them according to the comparison result). Specifically, based on the integration strategy of the software under test, a preset script (software program) triggers the marking of call information. If there are missing or incorrect markings, the integration is paused and an error message is displayed to assist developers in fixing the software under test. (For places with incorrect interface mapping, the preset script reuses the first and second preset mapping relationships in the Excel sheet into the software under test, replacing the original problematic content.) After the repair is completed, the integration continues from the pause step.

[0092] Through the above embodiments, interface errors can be detected at any time during the integration of the software under test, which is convenient, quick, time-saving, and improves efficiency. Interface matching relationships are automatically invoked during the integration process, requiring no manual intervention. The frequency of interface matching checks can be adjusted according to each software version by modifying the settings in the preset script. It can automatically perform consistency checks on interface matching relationships and the first and second preset mapping relationships, and automatically mark any discrepancies. It can assist developers in software repair; for incorrect interface mappings, the preset script reuses the first and second preset mapping relationships from the Excel spreadsheet in the software under test, replacing the original problematic content.

[0093] It should be noted that the method of this disclosure embodiment can be executed by a single device, such as a computer or server. The method of this embodiment can also be applied to a distributed scenario, where multiple devices cooperate to complete the task. In such a distributed scenario, one of these devices may execute only one or more steps of the method of this disclosure embodiment, and the multiple devices will interact with each other to complete the method described.

[0094] It should be noted that the above description describes some embodiments of this disclosure. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in a different order than that shown in the above embodiments and still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require a specific or sequential order to achieve the desired result. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0095] Based on the same inventive concept, corresponding to any of the above embodiments, this disclosure also provides a testing device for software call information.

[0096] refer to Figure 2 The testing device for the software call information includes:

[0097] The mapping relationship establishment module 201 is configured to establish a first preset mapping relationship between vehicle execution functions and software components, and a second preset mapping relationship between software components and interface signals;

[0098] The call information testing module 202 is configured to obtain the call information of the software under test during the integration process, and to test the call information based on the first preset mapping relationship and the second preset mapping relationship to obtain test results.

[0099] In some embodiments, the mapping relationship establishment module 201 includes:

[0100] The acquisition unit is configured to acquire vehicle execution function identifiers, software component identifiers, and interface signal identifiers;

[0101] The first establishing unit is configured to establish a first preset mapping relationship between the vehicle execution function and the software component based on the vehicle execution function identifier and the software component identifier;

[0102] The second establishment unit is configured to establish a second preset mapping relationship between the software component and the interface signal based on the software component identifier and the interface signal identifier.

[0103] In some embodiments, the call information testing module 202 includes:

[0104] The embedding unit is configured to create a preset script based on the first preset mapping relationship and the second preset mapping relationship, and embed the preset script into the software integration tool;

[0105] The test unit is configured to collect the call information of the software under test using the preset script during the integration process, and to test the call information using the software integration tool to obtain test results.

[0106] In some embodiments, the test unit includes:

[0107] The call information collection subunit is configured to collect the call information of the software under test using the preset script during the integration process of the software under test.

[0108] The analysis and processing subunit is configured to analyze and process the call information to obtain a first mapping relationship between the vehicle execution function and the software components of the software under test, and a second mapping relationship between the software components and the interface signals of the software under test.

[0109] The test subunit is configured to determine a target mapping relationship from the first mapping relationship to be tested and the second mapping relationship to be tested, and to test the target mapping relationship to be tested using the software integration tool to obtain test results.

[0110] In some embodiments, the test subunit is specifically configured as follows:

[0111] Determine whether the software under test is being tested for the first time;

[0112] In response to determining that the software under test is being tested for the first time, the first mapping relationship to be tested and the second mapping relationship to be tested are used as the target mapping relationship to be tested;

[0113] In response to determining that the software under test is not being tested for the first time, a target mapping relationship is determined from the first mapping relationship and the second mapping relationship by judging whether the software architecture of the software under test has changed.

[0114] In some embodiments, the test subunit is specifically configured as follows:

[0115] Determine whether the software architecture of the software under test has changed;

[0116] In response to the determination that the software architecture of the software under test has changed, the first mapping relationship and the second mapping relationship are used as the target mapping relationship to be tested;

[0117] In response to the determination that the software architecture of the software under test has not changed, the second mapping relationship is used as the target mapping relationship to be tested.

[0118] In some embodiments, the test unit includes:

[0119] The tagging subunit is configured to tag the call information using a preset script embedded in the software integration tool;

[0120] The repair subunit is configured to, in response to determining that there is a missing or incorrect marker, determine that the test result contains an error and repair the software under test.

[0121] In some embodiments, the repair subunit is specifically configured as follows:

[0122] If the test result indicates an error, the integration of the software under test is stopped.

[0123] Repair the calling information of the software under test, and determine whether the calling information of the software under test has been repaired.

[0124] In response to the determination that the call information of the software under test has been repaired, the integration of the software under test continues, and the software under test is tested during the integration process.

[0125] For ease of description, the above apparatus is described in terms of its functions, divided into various modules. Of course, in implementing this disclosure, the functions of each module can be implemented in one or more software and / or hardware.

[0126] The apparatus described above is used to implement the testing method for the corresponding software call information in any of the foregoing embodiments, and has the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0127] Based on the same inventive concept, corresponding to the methods of any of the above embodiments, this disclosure also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the software call information testing method described in any of the above embodiments.

[0128] Figure 3 This embodiment illustrates a more specific hardware structure of an electronic device, which may include a processor 1010, a memory 1020, an input / output interface 1030, a communication interface 1040, and a bus 1050. The processor 1010, memory 1020, input / output interface 1030, and communication interface 1040 are interconnected internally via the bus 1050.

[0129] The processor 1010 can be implemented using a general-purpose CPU (Central Processing Unit), microprocessor, application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this specification.

[0130] The memory 1020 can be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage device, dynamic storage device, etc. The memory 1020 can store the operating system and other applications. When the technical solutions provided in the embodiments of this specification are implemented by software or firmware, the relevant program code is stored in the memory 1020 and is called and executed by the processor 1010.

[0131] The input / output interface 1030 is used to connect input / output modules to realize information input and output. Input / output modules can be configured as components within the device (not shown in the figure) or externally connected to the device to provide corresponding functions. Input devices may include keyboards, mice, touchscreens, microphones, various sensors, etc., while output devices may include displays, speakers, vibrators, indicator lights, etc.

[0132] The communication interface 1040 is used to connect a communication module (not shown in the figure) to enable communication between this device and other devices. The communication module can communicate via wired means (such as USB (Universal Serial Bus), network cable, etc.) or wireless means (such as mobile network, WIFI (Wireless Fidelity), Bluetooth, etc.).

[0133] Bus 1050 includes a pathway for transmitting information between various components of the device, such as processor 1010, memory 1020, input / output interface 1030, and communication interface 1040.

[0134] It should be noted that although the above-described device only shows the processor 1010, memory 1020, input / output interface 1030, communication interface 1040, and bus 1050, in specific implementations, the device may also include other components necessary for normal operation. Furthermore, those skilled in the art will understand that the above-described device may only include the components necessary for implementing the embodiments of this specification, and not necessarily all the components shown in the figures.

[0135] The electronic device described above is used to implement the testing method for the corresponding software call information in any of the foregoing embodiments, and has the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0136] Based on the same inventive concept, corresponding to the methods of any of the above embodiments, this disclosure also provides a non-transitory computer-readable storage medium that stores computer instructions for causing the computer to execute the software call information testing method as described in any of the above embodiments.

[0137] The computer-readable medium of this embodiment includes permanent and non-permanent, removable and non-removable media, and information storage can be implemented by any method or technology. 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, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transfer medium that can be used to store information accessible by a computing device.

[0138] The computer instructions stored in the storage medium of the above embodiments are used to cause the computer to execute the software call information testing method as described in any of the above embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0139] Based on the same inventive concept, corresponding to the methods of any of the above embodiments, this application also provides a vehicle, including a testing device, electronic device, or storage medium for software call information in the above embodiments, wherein the vehicle device implements the testing method for software call information described in any of the above embodiments.

[0140] The vehicle described in the above embodiments is used to implement the software call information testing method described in any of the foregoing embodiments, and has the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0141] Based on the same inventive concept, corresponding to the methods of any of the above embodiments, this application also provides a computer program product, including computer program instructions. When the computer program instructions are run on a computer, the computer executes the software call information testing method as described in any of the above embodiments, and has the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0142] It is understood that before using the technical solutions of the various embodiments in this disclosure, users will be informed of the type, scope of use, and usage scenarios of the personal information involved in an appropriate manner, and user authorization will be obtained.

[0143] For example, upon receiving a user's active request, a prompt message is sent to the user to explicitly inform them that the requested operation will require the acquisition and use of the user's personal information. This allows the user to independently choose, based on the prompt message, whether to provide personal information to the software or hardware such as electronic devices, applications, servers, or storage media performing the operations of this disclosed technical solution.

[0144] As an optional but not limited implementation, in response to a user's active request, sending a prompt message to the user can be done via a pop-up window, where the prompt message can be presented in text format. Furthermore, the pop-up window can also include a selection control allowing the user to choose "agree" or "disagree" to provide personal information to the electronic device.

[0145] It is understood that the above notification and user authorization process are merely illustrative and do not constitute a limitation on the implementation of this disclosure. Other methods that comply with relevant laws and regulations may also be applied to the implementation of this disclosure.

[0146] Those skilled in the art should understand that the discussion of any of the above embodiments is merely exemplary and is not intended to imply that the scope of this disclosure is limited to these examples; within the framework of this disclosure, the technical features of the above embodiments or different embodiments can also be combined, the steps can be implemented in any order, and there are many other variations of different aspects of the embodiments of this disclosure as described above, which are not provided in detail for the sake of brevity.

[0147] Additionally, to simplify the description and discussion, and to avoid obscuring the embodiments of this disclosure, the provided drawings may or may not show well-known power / ground connections to integrated circuit (IC) chips and other components. Furthermore, the apparatus may be shown in block diagram form to avoid obscuring the embodiments of this disclosure, and this also takes into account the fact that the details of implementation of these block diagram apparatuses are highly dependent on the platform on which the embodiments of this disclosure will be implemented (i.e., these details should be fully understood by those skilled in the art). While specific details (e.g., circuitry) have been set forth to describe exemplary embodiments of this disclosure, it will be apparent to those skilled in the art that the embodiments of this disclosure may be implemented without these specific details or with variations thereof. Therefore, these descriptions should be considered illustrative rather than restrictive.

[0148] Although this disclosure has been described in conjunction with specific embodiments thereof, many substitutions, modifications, and variations of these embodiments will be apparent to those skilled in the art from the foregoing description. For example, other memory architectures (e.g., dynamic RAM (DRAM)) may be used with the embodiments discussed.

[0149] This disclosure is intended to cover all such substitutions, modifications, and variations that fall within the broad scope of this disclosure. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this disclosure should be included within the protection scope of this disclosure.

Claims

1. A test method of software call information, characterized by, The method comprises: establishing a first preset mapping relationship between vehicle execution functions and software components, and a second preset mapping relationship between software components and interface signals; during integration of the software under test, obtaining calling information of the software under test, and testing the calling information based on the first preset mapping relationship and the second preset mapping relationship to obtain a test result; The method comprises: creating a preset script according to the first preset mapping relationship and the second preset mapping relationship, and embedding the preset script into a software integration tool; during integration of the software under test, collecting calling information of the software under test using the preset script, and testing the calling information using the software integration tool to obtain a test result; The method comprises: during integration of the software under test, collecting calling information of the software under test using the preset script; analyzing and processing the calling information to obtain a first test mapping relationship between vehicle execution functions and software components of the software under test, and a second test mapping relationship between software components and interface signals of the software under test; determining a target test mapping relationship from the first test mapping relationship and the second test mapping relationship, and testing the target test mapping relationship using the software integration tool to obtain a test result.

2. The method of claim 1, wherein, The method comprises: obtaining vehicle execution function identifiers, software component identifiers, and interface signal identifiers; based on the vehicle execution function identifiers and the software component identifiers, establishing a first preset mapping relationship between vehicle execution functions and software components; based on the software component identifiers and the interface signal identifiers, establishing a second preset mapping relationship between software components and interface signals.

3. The method of claim 1, wherein, The method comprises: determining whether the software under test is tested for the first time; in response to determining that the software under test is tested for the first time, taking the first test mapping relationship and the second test mapping relationship as a target test mapping relationship; in response to determining that the software under test is not tested for the first time, determining a target test mapping relationship from the first test mapping relationship and the second test mapping relationship by judging whether the software architecture of the software under test has changed.

4. The method of claim 3, wherein, The method comprises: judging whether the software architecture of the software under test has changed; in response to determining that the software architecture of the to-be-tested software changes, taking the first to-be-tested mapping relationship and the second to-be-tested mapping relationship as target to-be-tested mapping relationships; in response to determining that the software architecture of the to-be-tested software does not change, taking the second to-be-tested mapping relationship as a target to-be-tested mapping relationship.

5. The method of claim 1, wherein, The testing of the calling information by the software integration tool comprises: labeling the calling information by using a preset script embedded in the software integration tool; in response to determining that there is missing labeling or labeling error, determining that the test result has error, and repairing the to-be-tested software.

6. The method of claim 5, wherein, The determination that the test result has error and the repairing of the to-be-tested software comprise: determining that the test result has error, and stopping the integration of the to-be-tested software; repairing the calling information of the to-be-tested software, and determining whether the calling information of the to-be-tested software is repaired completely; in response to determining that the calling information of the to-be-tested software is repaired completely, continuing the integration of the to-be-tested software, and testing the to-be-tested software during the integration of the to-be-tested software.

7. An electronic device, comprising: An electronic device comprising a memory, a processor, and a computer program stored in the memory and running on the processor, wherein the processor implements the method of any one of claims 1 to 6 when executing the program.

8. A vehicle characterized by comprising: An electronic device comprising the electronic device of claim 7.

Images