A software version comparison method, system and electronic device

Abstract

This application provides a software version comparison method, system, and electronic device, relating to the field of automotive software testing technology. This application obtains a target software version information table and a software version information table under test, constructs corresponding composite keys for each, generates a mapping table based on the composite keys, and obtains the target software version number and the software version number under test corresponding to the target component based on the composite key of the target component. The two are then compared to obtain the software version comparison result. This enables automatic comparison of software versions of all vehicle components, reducing the workload of manual item-by-item verification, improving the efficiency and accuracy of version comparison, reducing the risk of missed or incorrect comparisons, and thus enhancing the reliability of vehicle software testing.

Description

Technical Field

[0001] This application relates to the field of automotive software testing technology, and in particular to a software version comparison method, system, and electronic device. Background Technology

[0002] Currently, common technical solutions for comparing vehicle software versions include manual item-by-item comparison, manual verification based on version information tables, and manual backfilling of test reports. These methods typically involve software test engineers confirming the version information of each component in the vehicle after the corresponding software version has been flashed. This verifies whether the part number, supplier code, serial number code, and software version number of each component in the tested vehicle match the corresponding information in the vehicle software version information table, thus determining whether subsequent vehicle software testing can proceed.

[0003] However, with the rapid development of new energy vehicles, the electronic and electrical architecture of vehicles is becoming increasingly complex, and the number of components in a vehicle is constantly increasing. Furthermore, different components often correspond to different suppliers, significantly increasing the workload of confirming vehicle software versions. Under these circumstances, existing methods for comparing vehicle software versions still mainly rely on manual processing, requiring manual verification of multiple information fields item by item. The overall process is cumbersome and inefficient. In particular, when a vehicle contains hundreds of components, relying solely on manual visual comparison is prone to omissions and errors, thus affecting the accuracy and reliability of vehicle software testing.

[0004] Therefore, based on the above problems, this application proposes a new software version comparison method. Summary of the Invention

[0005] In view of the above problems, embodiments of this application provide a software version comparison method, system, and electronic device to overcome or at least partially solve the above problems.

[0006] A first aspect of this application provides a software version comparison method, the method comprising: Obtain a software version information table, which includes: a target software version information table and a software version information table to be tested; Based on the software version information table, a composite key is constructed, which includes a first composite key constructed based on the target software version information table and a second composite key constructed based on the software version information table under test. A mapping table is generated based on the software version information table and the composite key, and the mapping table includes a first mapping table and a second mapping table; The target software version number of the target component is obtained from the first mapping table using the first composite key, and the test software version number of the target component is obtained from the second mapping table using the second composite key. The target component is any one of multiple components. The target software version number is compared with the version number of the software to be tested to obtain the software version comparison result of the target component.

[0007] Optionally, after obtaining the target software version information table and the software version information table under test, the method further includes: Traverse the first row of the target software version information table and obtain the column name of the target column in the first row of the target software version information table. The column name of the target column includes at least: component name, component number, supplier code, serial number code, and software version number. Traverse the first row of the software version information table under test and obtain the column name of the target column of the first row of the software version information table under test. The column name of the target column includes at least: component name, component number, supplier code, serial number code, and software version number. Initialize a first dictionary container and a second dictionary container, and store the column names of the target columns obtained from the target software version information table into the first dictionary container, and store the column names of the target columns obtained from the software version information table into the second dictionary container.

[0008] Optionally, constructing a composite key based on the software version information table includes: Obtain the values ​​of the cells corresponding to each target column from the target software version information table, and obtain the values ​​of the cells corresponding to each target column from the software version information table under test; From the values ​​of the cells corresponding to each target column obtained from the target software version information table, extract the values ​​corresponding to the component name, the supplier code, and the component number, and concatenate the values ​​corresponding to the component name, the supplier code, and the component number to obtain the first composite key; Extract the values ​​of the corresponding cells of each target column obtained from the software version information table under test, the values ​​corresponding to the component name, the supplier code, and the component number, and concatenate the values ​​corresponding to the component name, the supplier code, and the component number to obtain the second composite key.

[0009] Optionally, before obtaining the values ​​of the cells corresponding to each target column from the target software version information table and the values ​​of the cells corresponding to each target column from the software version information table under test, the method further includes: The column names of the target columns stored in the first dictionary container are matched with the column names of the target columns in the first row of the target software version information table, and the column numbers of the target columns in the first row of the target software version information table that match successfully are stored in the corresponding target columns in the first dictionary container. The column names of the target columns stored in the second dictionary container are matched with the column names of the target columns in the first row of the software version information table under test, and the column numbers of the target columns in the first row of the software version information table under test that match are stored in the corresponding target columns in the second dictionary container. The step of obtaining the values ​​of the corresponding cells for each target column from the target software version information table, and obtaining the values ​​of the corresponding cells for each target column from the software version information table under test, includes: According to the column name and column number of the target column stored in the first dictionary container, the value of the cell corresponding to each target column is obtained from the target software version information table; According to the column name and column number of the target column stored in the second dictionary container, the value of the cell corresponding to each target column is obtained from the software version information table under test.

[0010] Optionally, generating a mapping table based on the software version information table and the composite key includes: Obtain the values ​​of the cells corresponding to each target column from the target software version information table, and obtain the values ​​of the cells corresponding to each target column from the software version information table under test; The first composite key and the values ​​of the corresponding cells of each target column obtained from the target software version information table are stored in the first dictionary container to obtain the first mapping table. The first composite key is used as the key of the first dictionary container, and the values ​​of the corresponding cells of each target column obtained from the target software version information table are used as the values ​​of the first dictionary container. The second composite key and the values ​​of the corresponding cells of each target column obtained from the software version information table under test are stored in the second dictionary container to obtain the second mapping table. The second composite key is used as the key of the second dictionary container, and the values ​​of the corresponding cells of each target column obtained from the software version information table under test are used as the values ​​of the second dictionary container.

[0011] Optionally, obtaining the target software version number of the target component from the first mapping table using the first composite key, and obtaining the test software version number of the target component from the second mapping table using the second composite key, includes: Obtain the first composite key and the second composite key corresponding to the target component; Based on the first composite key, obtain the first target software version number and the second target software version number of the target component from the first mapping table; Based on the second composite key, the first and second software version numbers of the target component are obtained from the second mapping table.

[0012] Optionally, comparing the target software version number with the software version number under test to obtain the software version comparison result of the target component includes: Compare the version number of the first target software with the version number of the first software under test; If the comparison is successful, the version number of the first software under test is stored in the first successful comparison list; In the event of a failed comparison, the version number of the first software under test is stored in the first failed comparison list; Compare the version number of the second target software with the version number of the second software to be tested; If the comparison is successful, the version number of the second software to be tested will be stored in the second successful comparison list; In the event of a failed comparison, the version number of the second software to be tested is stored in the second failed comparison list.

[0013] Optionally, after obtaining the software version comparison results of the target component, the method further includes: Load the test report workbook and initialize the test report workbook to obtain the initialization worksheet of the test report workbook; In the initialization worksheet, create a first alignment success test report table corresponding to the first alignment success list, a first alignment failure test report table corresponding to the first alignment failure list, a second alignment success test report table corresponding to the second alignment success list, and a second alignment failure test report table corresponding to the second alignment failure list; Traverse the target comparison list, extract the names of the target components in the target comparison list by string slicing, and store the extracted names of the target components and the software version comparison results of the target components in the target comparison test report table; The target comparison list is any one of the first successful comparison list, the first failed comparison list, the second successful comparison list, and the second failed comparison list. The target comparison test report table is any one of the first successful comparison test report table corresponding to the first successful comparison list, the first failed comparison test report table corresponding to the first failed comparison list, the second successful comparison test report table corresponding to the second successful comparison list, and the second failed comparison test report table corresponding to the second failed comparison list.

[0014] A second aspect of this application provides a software version comparison system, the system comprising: The first acquisition module is used to acquire a software version information table, which includes: a target software version information table and a software version information table to be tested. A construction module is used to construct a composite key based on the software version information table. The composite key includes a first composite key constructed based on the target software version information table and a second composite key constructed based on the software version information table under test. A generation module is used to generate a mapping relationship table based on the software version information table and the composite key, wherein the mapping relationship table includes a first mapping relationship table and a second mapping relationship table; The second acquisition module is used to obtain the target software version number of the target component from the first mapping relationship table through the first composite key, and to obtain the test software version number of the target component from the second mapping relationship table through the second composite key, wherein the target component is any one of a plurality of components; The comparison module is used to compare the target software version number with the software version number under test to obtain the software version comparison result of the target component.

[0015] Optionally, the system further includes: The first acquisition submodule is used to traverse the first row of the target software version information table and obtain the column name of the target column of the first row of the target software version information table. The column name of the target column includes at least: component name, component number, supplier code, serial number code, and software version number. The second acquisition submodule is used to traverse the first row of the software version information table under test and obtain the column name of the target column of the first row of the software version information table under test. The column name of the target column includes at least: component name, component number, supplier code, serial number code, and software version number. An initialization and storage submodule is used to initialize a first dictionary container and a second dictionary container, store the column names of the target columns obtained from the target software version information table into the first dictionary container, and store the column names of the target columns obtained from the software version information table under test into the second dictionary container.

[0016] Optionally, the construction of a composite key based on the software version information table includes: The third acquisition submodule is used to acquire the values ​​of the cells corresponding to each target column from the target software version information table, and to acquire the values ​​of the cells corresponding to each target column from the software version information table under test. The first extraction submodule is used to extract the value corresponding to the component name, the value corresponding to the supplier code, and the value corresponding to the component number from the values ​​of the cells corresponding to each target column obtained from the target software version information table, and to concatenate the value corresponding to the component name, the value corresponding to the supplier code, and the value corresponding to the component number to obtain the first composite key; The second extraction submodule is used to extract the value corresponding to the component name, the value corresponding to the supplier code, and the value corresponding to the component number from the values ​​of the cells corresponding to each target column obtained from the software version information table under test, and to concatenate the value corresponding to the component name, the value corresponding to the supplier code, and the value corresponding to the component number to obtain the second composite key.

[0017] Optionally, the system further includes: The first matching submodule is used to match the column name of the target column stored in the first dictionary container with the column name of the target column in the first row of the target software version information table, and store the column number of the target column in the first row of the target software version information table that has been matched successfully into the corresponding target column in the first dictionary container. The second matching submodule is used to match the column name of the target column stored in the second dictionary container with the column name of the target column in the first row of the software version information table under test, and store the column number of the target column in the first row of the software version information table under test that is successfully matched into the corresponding target column in the second dictionary container. The third acquisition submodule, which involves obtaining the values ​​of the corresponding cells for each target column from the target software version information table and from the software version information table under test, includes: The first acquisition subunit is used to acquire the value of the cell corresponding to each target column from the target software version information table according to the column name and column number of the target column stored in the first dictionary container; The second acquisition subunit is used to acquire the value of the cell corresponding to each target column from the software version information table under test according to the column name and column number of the target column stored in the second dictionary container.

[0018] Optionally, the step of generating a mapping relationship table based on the software version information table and the composite key, the generation module includes: The fourth acquisition submodule is used to acquire the values ​​of the cells corresponding to each target column from the target software version information table, and to acquire the values ​​of the cells corresponding to each target column from the software version information table under test. The first storage submodule is used to store the first composite key and the values ​​of the corresponding cells of each target column obtained from the target software version information table into the first dictionary container to obtain the first mapping table. The first composite key is used as the key of the first dictionary container, and the values ​​of the corresponding cells of each target column obtained from the target software version information table are used as the values ​​of the first dictionary container. The second storage submodule is used to store the second composite key and the values ​​of the corresponding cells of each target column obtained from the software version information table under test into the second dictionary container to obtain the second mapping table. The second composite key is used as the key of the second dictionary container, and the values ​​of the corresponding cells of each target column obtained from the software version information table under test are used as the values ​​of the second dictionary container.

[0019] Optionally, the second acquisition module, which obtains the target software version number of the target component from the first mapping table using the first composite key and the test software version number of the target component from the second mapping table using the second composite key, includes: The fifth acquisition submodule is used to acquire the first composite key and the second composite key corresponding to the target component; The sixth acquisition submodule is used to obtain the first target software version number and the second target software version number of the target component from the first mapping relationship table according to the first composite key; The seventh acquisition submodule is used to obtain the first and second software version numbers of the target component from the second mapping table based on the second composite key.

[0020] Optionally, the comparison module, which compares the target software version number with the software version number under test to obtain the software version comparison result of the target component, includes: The first comparison submodule is used to compare the version number of the first target software with the version number of the first software under test. The third storage submodule is used to store the version number of the first software under test into the first successful comparison list if the comparison is successful. The fourth storage submodule is used to store the version number of the first software under test to the first comparison failure list in the event of a comparison failure. The second comparison submodule is used to compare the version number of the second target software with the version number of the second software to be tested; The fifth storage submodule is used to store the second software version number to be tested into the second successful comparison list if the comparison is successful. The sixth storage submodule is used to store the second software version number to be tested into the second comparison failure list in the event of a comparison failure.

[0021] Optionally, the system further includes: The loading and initialization submodule is used to load the test report workbook and initialize the test report workbook to obtain the initialization worksheet of the test report workbook. A submodule is created to create a first alignment success test report table, a first alignment failure test report table, a second alignment success test report table, and a second alignment failure test report table corresponding to the first alignment success list and the second alignment failure list, respectively, in the initialization worksheet. The seventh storage submodule is used to traverse the target comparison list, extract the names of the target components in the target comparison list by string slicing, and store the extracted names of the target components and the software version comparison results of the target components in the target comparison test report table; The target comparison list is any one of the first successful comparison list, the first failed comparison list, the second successful comparison list, and the second failed comparison list. The target comparison test report table is any one of the first successful comparison test report table corresponding to the first successful comparison list, the first failed comparison test report table corresponding to the first failed comparison list, the second successful comparison test report table corresponding to the second successful comparison list, and the second failed comparison test report table corresponding to the second failed comparison list.

[0022] A third aspect of this application provides an electronic device, including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the software version comparison method as described in the first aspect of this application.

[0023] The beneficial effects of this application are: This application provides a software version comparison method, the method comprising: obtaining a software version information table, the software version information table including a target software version information table and a software version information table under test; constructing a composite key based on the software version information table, the composite key including a first composite key constructed based on the target software version information table and a second composite key constructed based on the software version information table under test; generating a mapping relationship table according to the software version information table and the composite key, the mapping relationship table including a first mapping relationship table and a second mapping relationship table; obtaining the target software version number of a target component from the first mapping relationship table using the first composite key, and obtaining the software version number under test of the target component from the second mapping relationship table using the second composite key, wherein the target component is any one of multiple components; comparing the target software version number with the software version number under test to obtain a software version comparison result of the target component.

[0024] This application obtains a target software version information table and a test software version information table, constructs corresponding composite keys for each, generates a mapping table based on the composite keys, and obtains the target software version number and test software version number corresponding to the target component based on the composite key of the target component. The two are then compared to obtain the software version comparison result. This enables automatic comparison of software versions for all vehicle components, reducing the workload of manual item-by-item verification, improving the efficiency and accuracy of version comparison, reducing the risk of missed or incorrect comparisons, and thus enhancing the reliability of vehicle software testing. Attached Figure Description

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

[0026] Figure 1 This is a flowchart illustrating the steps of a software version comparison method provided in an embodiment of this application; Figure 2 This is a flowchart illustrating the steps of a target column storage method provided in an embodiment of this application; Figure 3 This is a flowchart of a software version comparison provided in an embodiment of this application; Figure 4 This is a schematic diagram of a software version comparison system provided in an embodiment of this application; Figure 5 This is a schematic diagram of an electronic device provided in an embodiment of this application. Detailed Implementation

[0027] Exemplary embodiments of this application will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of this application are shown in the drawings, it should be understood that this application may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided to enable a more thorough understanding of this application and to fully convey the scope of this application to those skilled in the art.

[0028] In a first aspect, this application provides a software version comparison method, such as... Figure 1 As shown, the method includes: S101, Obtain the software version information table, which includes: the target software version information table and the software version information table to be tested.

[0029] In this step, the software version information table is first obtained. This table includes a target software version information table and a test software version information table. The target software version information table provides standard data for version comparison, while the test software version information table provides the version data after the vehicle has been actually flashed. In this application, for the software version information table, the corresponding Excel workbook can be loaded first, and a worksheet object can be instantiated. Then, the location of key columns can be found in the header row. Key columns include at least the software version number, part number, supplier code, serial number code, and part name. After locating each key column, the corresponding data values ​​for each column are read row by row from the data area, thus completing the collection of key version data from the two version information tables.

[0030] S102, based on the software version information table, construct a composite key, the composite key including a first composite key constructed based on the target software version information table, and a second composite key constructed based on the software version information table to be tested.

[0031] In this step, the values ​​of key columns are extracted from both the target software version information table and the software under test version information table. These key columns can be component names, supplier codes, and component numbers, and are concatenated in a predetermined order to form a composite key. In some cases, the combination rule for constructing the composite key is: component name^supplier code^component number, where "^" serves as the field separator. In this step, a first composite key is constructed based on the target software version information table, and a second composite key is constructed based on the software under test version information table.

[0032] S103, Generate a mapping relationship table based on the software version information table and the composite key, the mapping relationship table including a first mapping relationship table and a second mapping relationship table.

[0033] In this step, corresponding mapping tables are established for the target software version information table and the software under test version information table, respectively. In some cases, a nested dictionary approach can be used for storage: a composite key is used as the index, and a data set containing fields such as software version number, component number, supplier code, serial number code, and component name is used as the value. In this step, the first mapping table is used to store the version information of each component in the target software version information table, and the second mapping table is used to store the version information of each component in the software under test version information table.

[0034] S104, obtain the target software version number of the target component from the first mapping table through the first composite key, and obtain the test software version number of the target component from the second mapping table through the second composite key, wherein the target component is any one of multiple components.

[0035] In this step, for any target component among multiple components, first determine the first composite key corresponding to the target component in the target software version information table, and then use the first composite key to obtain the target software version number from the first mapping relationship table; at the same time, determine the second composite key corresponding to the target component in the software version information table under test, and then use the second composite key to obtain the software version number under test from the second mapping relationship table.

[0036] S105, compare the target software version number with the software version number to be tested to obtain the software version comparison result of the target component.

[0037] The target software version number is compared with the version number of the software under test. If the two version numbers are the same, the software version comparison of the target component is considered successful. If the two version numbers are different, the software version comparison of the target component is considered unsuccessful.

[0038] This application obtains a target software version information table and a test software version information table, constructs corresponding composite keys for each, generates a mapping table based on the composite keys, and obtains the target software version number and test software version number corresponding to the target component based on the composite key of the target component. The two are then compared to obtain the software version comparison result. This enables automatic comparison of software versions for all vehicle components, reducing the workload of manual item-by-item verification, improving the efficiency and accuracy of version comparison, reducing the risk of missed or incorrect comparisons, and thus enhancing the reliability of vehicle software testing.

[0039] In one embodiment, a method such as... is also provided. Figure 2 The diagram illustrates a target column storage method, which includes: S201, traverse the first row of the target software version information table and obtain the column name of the target column in the first row of the target software version information table. The column name of the target column includes at least: component name, component number, supplier code, serial number code, and software version number.

[0040] In this step, the first row of the target software version information table stores the field names corresponding to each column. Therefore, this step uses the first row as the header row for traversal. During traversal, the column names of each column can be read sequentially according to cell order, and it can be determined whether the current column name belongs to the preset target column. The field range of the preset target column name includes at least the component name, component number, supplier code, serial number code, and software version number.

[0041] S202, traverse the first row of the software version information table under test, and obtain the column name of the target column of the first row of the software version information table under test. The column name of the target column includes at least: component name, component number, supplier code, serial number code, and software version number.

[0042] In this step, following the same method as step S201, the first row of the software version information table under test is traversed. During the traversal, the column name corresponding to each column is read in the order of the cells, and it is determined whether the current column name belongs to the preset target column.

[0043] S203, initialize the first dictionary container and the second dictionary container, and store the column names of the target columns obtained from the target software version information table into the first dictionary container, and store the column names of the target columns obtained from the software version information table into the second dictionary container.

[0044] In this step, separate data containers can be created for the target software version information table and the software version information table under test, respectively, to store the header identification results. The first dictionary container is used to store the column names of the target columns in the target software version information table and their corresponding relationships, and the second dictionary container is used to store the column names of the target columns in the software version information table under test and their corresponding relationships.

[0045] In one embodiment, constructing a composite key based on the software version information table includes: Obtain the values ​​of the cells corresponding to each target column from the target software version information table, and obtain the values ​​of the cells corresponding to each target column from the software version information table under test; From the values ​​of the cells corresponding to each target column obtained from the target software version information table, extract the values ​​corresponding to the component name, the supplier code, and the component number, and concatenate the values ​​corresponding to the component name, the supplier code, and the component number to obtain the first composite key; Extract the values ​​of the corresponding cells of each target column obtained from the software version information table under test, the values ​​corresponding to the component name, the supplier code, and the component number, and concatenate the values ​​corresponding to the component name, the supplier code, and the component number to obtain the second composite key.

[0046] In this embodiment, to accurately locate the version data corresponding to the same component from the target software version information table and the software version information table under test, a composite key can be constructed based on multiple key fields. Specifically, after completing the header identification and determining the column positions corresponding to the component name, component number, supplier code, serial number code, and software version number, the data rows in the two version information tables can be traversed, and the values ​​of the cells corresponding to each target column can be read according to the determined column positions. During the reading process, at least the component name, supplier code, and component number corresponding to each row can be extracted from the target software version information table, and the same method can be used to extract at least the component name, supplier code, and component number corresponding to each row from the software version information table under test.

[0047] Furthermore, after reading the values ​​of the cells corresponding to each target column, the values ​​corresponding to the component name, supplier code, and component number can be selected from the target software version information table and concatenated in a preset order to obtain the first composite key. Simultaneously, the values ​​corresponding to the component name, supplier code, and component number can be selected from the software version information table under test and concatenated in the same order to obtain the second composite key. In some cases, the values ​​of the cells corresponding to each target column can be connected using the separator "^", for example: component name^supplier code^component number.

[0048] In one embodiment, before obtaining the values ​​of the cells corresponding to each target column from the target software version information table and the values ​​of the cells corresponding to each target column from the software version information table under test, the method further includes: The column names of the target columns stored in the first dictionary container are matched with the column names of the target columns in the first row of the target software version information table, and the column numbers of the target columns in the first row of the target software version information table that match successfully are stored in the corresponding target columns in the first dictionary container. The column names of the target columns stored in the second dictionary container are matched with the column names of the target columns in the first row of the software version information table under test, and the column numbers of the target columns in the first row of the software version information table under test that match are stored in the corresponding target columns in the second dictionary container. The step of obtaining the values ​​of the corresponding cells for each target column from the target software version information table, and obtaining the values ​​of the corresponding cells for each target column from the software version information table under test, includes: According to the column name and column number of the target column stored in the first dictionary container, the value of the cell corresponding to each target column is obtained from the target software version information table; According to the column name and column number of the target column stored in the second dictionary container, the value of the cell corresponding to each target column is obtained from the software version information table under test.

[0049] In this embodiment, before reading the values ​​of the cells corresponding to each target column from the target software version information table and the software version information table under test, the correspondence between the target column name and the actual column number can be determined first.

[0050] The column names of each target column pre-stored in the first dictionary container are matched one by one with the column names of each target column in the first row of the target software version information table. If a match is successful, the column number of the corresponding target column in the target software version information table is recorded under the corresponding target column item in the first dictionary container. Similarly, the column names of each target column pre-stored in the second dictionary container are matched one by one with the column names of each target column in the first row of the software version information table under test. If a match is successful, the column number of the corresponding target column in the software version information table under test is recorded under the corresponding target column item in the second dictionary container.

[0051] After matching column names and column numbers, the first dictionary container stores the field names and column positions corresponding to each target column in the target software version information table, and the second dictionary container stores the field names and column positions corresponding to each target column in the software under test version information table. Based on this correspondence, when reading data subsequently, the values ​​of the cells corresponding to each target column in the target software version information table can be retrieved according to the column names and column numbers stored in the first dictionary container; alternatively, the values ​​of the cells corresponding to each target column in the software under test version information table can be retrieved according to the column names and column numbers stored in the second dictionary container.

[0052] This embodiment improves the accuracy of target field location in different versions of information tables and reduces data extraction errors caused by different column orders by first establishing the correspondence between the target column name and column number and then extracting the cell value according to the correspondence.

[0053] In one embodiment, generating a mapping table based on the software version information table and the composite key includes: Obtain the values ​​of the cells corresponding to each target column from the target software version information table, and obtain the values ​​of the cells corresponding to each target column from the software version information table under test; The first composite key and the values ​​of the corresponding cells of each target column obtained from the target software version information table are stored in the first dictionary container to obtain the first mapping table. The first composite key is used as the key of the first dictionary container, and the values ​​of the corresponding cells of each target column obtained from the target software version information table are used as the values ​​of the first dictionary container. The second composite key and the values ​​of the corresponding cells of each target column obtained from the software version information table under test are stored in the second dictionary container to obtain the second mapping table. The second composite key is used as the key of the second dictionary container, and the values ​​of the corresponding cells of each target column obtained from the software version information table under test are used as the values ​​of the second dictionary container.

[0054] In this embodiment, after constructing the first composite key and the second composite key based on the target software version information table and the software version information table to be tested, a mapping relationship table can be further generated based on the software version information table and the composite key.

[0055] Specifically, after obtaining the values ​​of the cells corresponding to each target column in the target software version information table, the first composite key can be associated with the values ​​of the cells corresponding to each target column in that row of data and stored in the first dictionary container, thus obtaining the first mapping table. Here, the first composite key serves as the key of the first dictionary container, and the values ​​of the cells corresponding to each target column in the target software version information table serve as the values ​​of the first dictionary container. The first mapping table records the correspondence between "first composite key - target column data". Similarly, after obtaining the values ​​of the cells corresponding to each target column in the software version information table under test, the second composite key can be associated with the values ​​of the cells corresponding to each target column in that row of data and stored in the second dictionary container, thus obtaining the second mapping table. Here, the second composite key serves as the key of the second dictionary container, and the values ​​of the cells corresponding to each target column in the software version information table under test serve as the values ​​of the second dictionary container. In other words, the second mapping table records the correspondence between "second composite key - target column data".

[0056] Using the above method, the row data in the target software version information table and the software version information table under test can be converted into a key-value mapping structure indexed by a composite key, thus forming a first mapping table and a second mapping table. Therefore, during subsequent software version comparison, it is no longer necessary to manually search or repeatedly traverse the two version information tables row by row. Instead, the version information corresponding to the target component can be quickly located directly based on the composite key, and the software version number can be extracted for automatic comparison. This not only facilitates accurate matching of the same component in the two version information tables but also improves data retrieval efficiency.

[0057] In one embodiment, obtaining the target software version number of the target component from the first mapping table using the first composite key, and obtaining the test software version number of the target component from the second mapping table using the second composite key, includes: Obtain the first composite key and the second composite key corresponding to the target component; Based on the first composite key, obtain the first target software version number and the second target software version number of the target component from the first mapping table; Based on the second composite key, the first and second software version numbers of the target component are obtained from the second mapping table.

[0058] In this embodiment, after obtaining the first composite key and the second composite key corresponding to the target component, the version information corresponding to the target component can be extracted based on the first mapping table and the second mapping table, respectively. Specifically, both the first mapping table and the second mapping table adopt a storage method using the composite key as the key and the field values ​​corresponding to each target column as the values. Therefore, after determining the first composite key corresponding to the target component, the first composite key can be directly used as an index to find the set of fields corresponding to the target component in the first mapping table; similarly, after determining the second composite key corresponding to the target component, the second composite key can also be directly used as an index to find the set of fields corresponding to the target component in the second mapping table.

[0059] Furthermore, the first target software version number and the second target software version number of the target component can be obtained from the first mapping table according to the first composite key, or the first test software version number and the second test software version number of the target component can be obtained from the second mapping table according to the second composite key. In this application, the first target software version number and the first test software version number are the 0216 software version number of the target component, and the second target software version number and the second test software version number are the f189 serial number code of the target component.

[0060] This embodiment is based on the fact that the records of the target component in the two version information tables can be accurately matched first by using a composite key, and then the specific version field can be extracted from the corresponding record. This avoids the manual process of searching for software version numbers and serial numbers one by one, and improves the extraction efficiency and matching accuracy of target component version data.

[0061] In one embodiment, comparing the target software version number with the software version number under test to obtain the software version comparison result of the target component includes: Compare the version number of the first target software with the version number of the first software under test; If the comparison is successful, the version number of the first software under test is stored in the first successful comparison list; In the event of a failed comparison, the version number of the first software under test is stored in the first failed comparison list; Compare the version number of the second target software with the version number of the second software to be tested; If the comparison is successful, the version number of the second software to be tested will be stored in the second successful comparison list; In the event of a failed comparison, the version number of the second software to be tested is stored in the second failed comparison list.

[0062] In this embodiment, after obtaining the first target software version number, the first software version number under test, the second target software version number, and the second software version number under test corresponding to the target component, the two sets of version information can be compared to determine the software version comparison result of the target component. Specifically, the first target software version number and the first software version number under test are first compared for consistency; when they are the same, it indicates that the first type of version information comparison is successful, and the first software version number under test can be stored in the first successful comparison list; when they are different, it indicates that the first type of version information comparison fails, and the first software version number under test can be stored in the first failed comparison list.

[0063] After completing the comparison of the first type of version information, the second target software version number can be compared with the second software version number under test. When they are the same, it indicates that the second type of version information comparison is successful, and the second software version number under test can be stored in the second successful comparison list. When they are different, it indicates that the second type of version information comparison fails, and the second software version number under test can be stored in the second failed comparison list.

[0064] The above method allows for the recording of comparison results for different types of version information, categorized and stored as successful and unsuccessful comparisons. This not only enables rapid statistical analysis of the comparison status of various version information for target components but also facilitates the separate output of successful and unsuccessful comparison results for generating version confirmation results or backfilling test reports, thereby improving the efficiency and ease of use of software version comparison results.

[0065] In one embodiment, after obtaining the software version comparison result of the target component, the method further includes: Load the test report workbook and initialize the test report workbook to obtain the initialization worksheet of the test report workbook; In the initialization worksheet, create a first alignment success test report table corresponding to the first alignment success list, a first alignment failure test report table corresponding to the first alignment failure list, a second alignment success test report table corresponding to the second alignment success list, and a second alignment failure test report table corresponding to the second alignment failure list; Traverse the target comparison list, extract the names of the target components in the target comparison list by string slicing, and store the extracted names of the target components and the software version comparison results of the target components in the target comparison test report table; The target comparison list is any one of the first successful comparison list, the first failed comparison list, the second successful comparison list, and the second failed comparison list. The target comparison test report table is any one of the first successful comparison test report table corresponding to the first successful comparison list, the first failed comparison test report table corresponding to the first failed comparison list, the second successful comparison test report table corresponding to the second successful comparison list, and the second failed comparison test report table corresponding to the second failed comparison list.

[0066] In this embodiment, after obtaining the software version comparison results of the target component, the comparison results can also be filled back into the test report.

[0067] Specifically, first load the test report workbook and instantiate the corresponding worksheet object to obtain the initialization worksheet for backfilling.

[0068] After initializing the worksheets, corresponding result record areas can be created in the initialized worksheets based on the first successful comparison list, the first failed comparison list, the second successful comparison list, and the second failed comparison list, thereby forming the first successful comparison test report table, the first failed comparison test report table, the second successful comparison test report table, and the second failed comparison test report table. In this embodiment, the test report table can be understood as the corresponding area or table item in the test report used to record different comparison results. Its function is to classify and record version comparison information of different types and results, facilitating subsequent querying and summarization.

[0069] Furthermore, before backfilling the test report, the target comparison list can be traversed first, and the names of the target components can be extracted by string slicing. In some cases, when processing the elements in the success list and the failure list, the names of the target components can be extracted by "split('^')[0]" and a new list containing only the component names can be generated; at the same time, deduplication judgment can be added. If the corresponding controller name already exists in the new list, it will not be added again, thereby improving the regularity of the backfilling results. In this embodiment, the target comparison list is any one of the first comparison success list, the first comparison failure list, the second comparison success list, and the second comparison failure list.

[0070] In this embodiment, after obtaining the name of the target component, the extracted target component name and the corresponding software version comparison result can be written into the corresponding target comparison test report table. Specifically, the target column used to identify component names in the test report can be traversed, and the names in the target column can be matched with the extracted target component names. If the match is successful, the corresponding software version information and its comparison result can be written into a specified position in the test report. Specifically, the extracted target component name and the target component software version comparison result can be stored in the target comparison test report table, which can be any one of the following: the first successful comparison test report table corresponding to the first successful comparison list, the first failed comparison test report table corresponding to the first failed comparison list, the second successful comparison test report table corresponding to the second successful comparison list, and the second failed comparison test report table corresponding to the second failed comparison list.

[0071] This embodiment automatically backfills the test report after obtaining the software version comparison results, which can reduce the workload of manually compiling and filling in the test report. At the same time, by extracting the target component name by string slicing the controller identifier in the comparison list, it can better adapt to the name field in the test report, thereby improving the accuracy and efficiency of test report backfilling.

[0072] In one embodiment, this application provides as follows: Figure 3 The flowchart shown below illustrates the software version comparison process: Obtain the target software version information table and the software under test version information table respectively; identify the target columns corresponding to the component name, component number, supplier code, serial number code, and software version number in the two software version information tables; construct a first composite key and a second composite key based on the component name, supplier code, and component number, and generate the corresponding mapping relationship table; if it is determined that the first composite key and the second composite key correspond to the same target component, obtain the target software version information and the software under test version information respectively and compare them; based on the comparison results, generate a comparison success or comparison failure result, and fill the corresponding result back into the test report.

[0073] Based on the same inventive concept, a second aspect of the embodiments of this application provides a software version comparison system, such as... Figure 4 As shown, the system includes: The first acquisition module 301 is used to acquire a software version information table, which includes a target software version information table and a software version information table to be tested. The construction module 302 is used to construct a composite key based on the software version information table. The composite key includes a first composite key constructed based on the target software version information table and a second composite key constructed based on the software version information table under test. The generation module 303 is used to generate a mapping relationship table based on the software version information table and the composite key, wherein the mapping relationship table includes a first mapping relationship table and a second mapping relationship table; The second acquisition module 304 is used to obtain the target software version number of the target component from the first mapping relationship table through the first composite key, and to obtain the test software version number of the target component from the second mapping relationship table through the second composite key, wherein the target component is any one of a plurality of components; The comparison module 305 is used to compare the target software version number with the software version number under test to obtain the software version comparison result of the target component.

[0074] Optionally, the system further includes: The first acquisition submodule is used to traverse the first row of the target software version information table and obtain the column name of the target column of the first row of the target software version information table. The column name of the target column includes at least: component name, component number, supplier code, serial number code, and software version number. The second acquisition submodule is used to traverse the first row of the software version information table under test and obtain the column name of the target column of the first row of the software version information table under test. The column name of the target column includes at least: component name, component number, supplier code, serial number code, and software version number. An initialization and storage submodule is used to initialize a first dictionary container and a second dictionary container, store the column names of the target columns obtained from the target software version information table into the first dictionary container, and store the column names of the target columns obtained from the software version information table under test into the second dictionary container.

[0075] Optionally, the construction module 302, which constructs a composite key based on the software version information table, includes: The third acquisition submodule is used to acquire the values ​​of the cells corresponding to each target column from the target software version information table, and to acquire the values ​​of the cells corresponding to each target column from the software version information table under test. The first extraction submodule is used to extract the value corresponding to the component name, the value corresponding to the supplier code, and the value corresponding to the component number from the values ​​of the cells corresponding to each target column obtained from the target software version information table, and to concatenate the value corresponding to the component name, the value corresponding to the supplier code, and the value corresponding to the component number to obtain the first composite key; The second extraction submodule is used to extract the value corresponding to the component name, the value corresponding to the supplier code, and the value corresponding to the component number from the values ​​of the cells corresponding to each target column obtained from the software version information table under test, and to concatenate the value corresponding to the component name, the value corresponding to the supplier code, and the value corresponding to the component number to obtain the second composite key.

[0076] Optionally, the system further includes: The first matching submodule is used to match the column name of the target column stored in the first dictionary container with the column name of the target column in the first row of the target software version information table, and store the column number of the target column in the first row of the target software version information table that has been matched successfully into the corresponding target column in the first dictionary container. The second matching submodule is used to match the column name of the target column stored in the second dictionary container with the column name of the target column in the first row of the software version information table under test, and store the column number of the target column in the first row of the software version information table under test that is successfully matched into the corresponding target column in the second dictionary container. The third acquisition submodule, which involves obtaining the values ​​of the corresponding cells for each target column from the target software version information table and from the software version information table under test, includes: The first acquisition subunit is used to acquire the value of the cell corresponding to each target column from the target software version information table according to the column name and column number of the target column stored in the first dictionary container; The second acquisition subunit is used to acquire the value of the cell corresponding to each target column from the software version information table under test according to the column name and column number of the target column stored in the second dictionary container.

[0077] Optionally, the step of generating a mapping relationship table based on the software version information table and the composite key, the generation module 303, includes: The fourth acquisition submodule is used to acquire the values ​​of the cells corresponding to each target column from the target software version information table, and to acquire the values ​​of the cells corresponding to each target column from the software version information table under test. The first storage submodule is used to store the first composite key and the values ​​of the corresponding cells of each target column obtained from the target software version information table into the first dictionary container to obtain the first mapping table. The first composite key is used as the key of the first dictionary container, and the values ​​of the corresponding cells of each target column obtained from the target software version information table are used as the values ​​of the first dictionary container. The second storage submodule is used to store the second composite key and the values ​​of the corresponding cells of each target column obtained from the software version information table under test into the second dictionary container to obtain the second mapping table. The second composite key is used as the key of the second dictionary container, and the values ​​of the corresponding cells of each target column obtained from the software version information table under test are used as the values ​​of the second dictionary container.

[0078] Optionally, the second acquisition module 304, which obtains the target software version number of the target component from the first mapping table using the first composite key and the test software version number of the target component from the second mapping table using the second composite key, includes: The fifth acquisition submodule is used to acquire the first composite key and the second composite key corresponding to the target component; The sixth acquisition submodule is used to obtain the first target software version number and the second target software version number of the target component from the first mapping relationship table according to the first composite key; The seventh acquisition submodule is used to obtain the first and second software version numbers of the target component from the second mapping table based on the second composite key.

[0079] Optionally, the comparison module, which compares the target software version number with the software version number under test to obtain the software version comparison result of the target component, includes: The first comparison submodule is used to compare the version number of the first target software with the version number of the first software under test. The third storage submodule is used to store the version number of the first software under test into the first successful comparison list if the comparison is successful. The fourth storage submodule is used to store the version number of the first software under test to the first comparison failure list in the event of a comparison failure. The second comparison submodule is used to compare the version number of the second target software with the version number of the second software to be tested; The fifth storage submodule is used to store the second software version number to be tested into the second successful comparison list if the comparison is successful. The sixth storage submodule is used to store the second software version number to be tested into the second comparison failure list in the event of a comparison failure.

[0080] Optionally, the system further includes: The loading and initialization submodule is used to load the test report workbook and initialize the test report workbook to obtain the initialization worksheet of the test report workbook. A submodule is created to create a first alignment success test report table, a first alignment failure test report table, a second alignment success test report table, and a second alignment failure test report table corresponding to the first alignment success list and the second alignment failure list, respectively, in the initialization worksheet. The seventh storage submodule is used to traverse the target comparison list, extract the names of the target components in the target comparison list by string slicing, and store the extracted names of the target components and the software version comparison results of the target components in the target comparison test report table; The target comparison list is any one of the first successful comparison list, the first failed comparison list, the second successful comparison list, and the second failed comparison list. The target comparison test report table is any one of the first successful comparison test report table corresponding to the first successful comparison list, the first failed comparison test report table corresponding to the first failed comparison list, the second successful comparison test report table corresponding to the second successful comparison list, and the second failed comparison test report table corresponding to the second failed comparison list.

[0081] Based on the same inventive concept, a third aspect of the embodiments of this application provides a method as follows: Figure 5 The electronic device 100 shown includes a processor 120, a memory 110, and a program or instructions stored in the memory 110 and executable on the processor 120. When the program or instructions are executed by the processor 120, they implement the steps of the software version comparison method as described in the first aspect of this application.

[0082] Each embodiment in this specification focuses on the differences from other embodiments. For the same or similar parts between the embodiments, please refer to each other.

[0083] Those skilled in the art will understand that embodiments of this application can be provided as methods, apparatus, or computer program products. Therefore, embodiments of this application can take the form of entirely hardware embodiments, entirely software embodiments, or embodiments combining software and hardware aspects. Furthermore, embodiments of this application can take the form of computer program products 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.

[0084] This application describes embodiments with reference to flowchart illustrations and / or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing terminal device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal device, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0085] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing terminal device to operate in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0086] These computer program instructions can also be loaded onto a computer or other programmable data processing terminal equipment, causing a series of operational steps to be performed on the computer or other programmable terminal equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable terminal equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0087] Although preferred embodiments of the present application have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of the embodiments of the present application.

[0088] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or terminal device that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or terminal device. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or terminal device that includes said element.

[0089] The above provides a detailed description of the software version comparison method, system, and electronic device. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A software version comparison method, characterized in that, The method includes: Obtain a software version information table, which includes: a target software version information table and a software version information table to be tested; Based on the software version information table, a composite key is constructed, which includes a first composite key constructed based on the target software version information table and a second composite key constructed based on the software version information table under test. A mapping table is generated based on the software version information table and the composite key, and the mapping table includes a first mapping table and a second mapping table; The target software version number of the target component is obtained from the first mapping table using the first composite key, and the test software version number of the target component is obtained from the second mapping table using the second composite key. The target component is any one of multiple components. The target software version number is compared with the version number of the software to be tested to obtain the software version comparison result of the target component.

2. The software version comparison method according to claim 1, characterized in that, After obtaining the target software version information table and the software version information table under test, the method further includes: Traverse the first row of the target software version information table and obtain the column name of the target column in the first row of the target software version information table. The column name of the target column includes at least: component name, component number, supplier code, serial number code, and software version number. Traverse the first row of the software version information table under test and obtain the column name of the target column of the first row of the software version information table under test. The column name of the target column includes at least: component name, component number, supplier code, serial number code, and software version number. Initialize a first dictionary container and a second dictionary container, and store the column names of the target columns obtained from the target software version information table into the first dictionary container, and store the column names of the target columns obtained from the software version information table into the second dictionary container.

3. The software version comparison method according to claim 2, characterized in that, The construction of the composite key based on the software version information table includes: Obtain the values ​​of the cells corresponding to each target column from the target software version information table, and obtain the values ​​of the cells corresponding to each target column from the software version information table under test; From the values ​​of the cells corresponding to each target column obtained from the target software version information table, extract the values ​​corresponding to the component name, the supplier code, and the component number, and concatenate the values ​​corresponding to the component name, the supplier code, and the component number to obtain the first composite key; Extract the values ​​of the corresponding cells of each target column obtained from the software version information table under test, the values ​​corresponding to the component name, the supplier code, and the component number, and concatenate the values ​​corresponding to the component name, the supplier code, and the component number to obtain the second composite key.

4. The software version comparison method according to claim 3, characterized in that, Before obtaining the values ​​of the corresponding cells for each target column from the target software version information table and the values ​​of the corresponding cells for each target column from the software version information table under test, the method further includes: The column names of the target columns stored in the first dictionary container are matched with the column names of the target columns in the first row of the target software version information table, and the column numbers of the target columns in the first row of the target software version information table that match successfully are stored in the corresponding target columns in the first dictionary container. The column names of the target columns stored in the second dictionary container are matched with the column names of the target columns in the first row of the software version information table under test, and the column numbers of the target columns in the first row of the software version information table under test that match are stored in the corresponding target columns in the second dictionary container. The step of obtaining the values ​​of the corresponding cells for each target column from the target software version information table, and obtaining the values ​​of the corresponding cells for each target column from the software version information table under test, includes: According to the column name and column number of the target column stored in the first dictionary container, the value of the cell corresponding to each target column is obtained from the target software version information table; According to the column name and column number of the target column stored in the second dictionary container, the value of the cell corresponding to each target column is obtained from the software version information table under test.

5. The software version comparison method according to claim 2, characterized in that, The step of generating a mapping table based on the software version information table and the composite key includes: Obtain the values ​​of the cells corresponding to each target column from the target software version information table, and obtain the values ​​of the cells corresponding to each target column from the software version information table under test; The first composite key and the values ​​of the corresponding cells of each target column obtained from the target software version information table are stored in the first dictionary container to obtain the first mapping table. The first composite key is used as the key of the first dictionary container, and the values ​​of the corresponding cells of each target column obtained from the target software version information table are used as the values ​​of the first dictionary container. The second composite key and the values ​​of the corresponding cells of each target column obtained from the software version information table under test are stored in the second dictionary container to obtain the second mapping table. The second composite key is used as the key of the second dictionary container, and the values ​​of the corresponding cells of each target column obtained from the software version information table under test are used as the values ​​of the second dictionary container.

6. The software version comparison method according to claim 1, characterized in that, The step of obtaining the target software version number of the target component from the first mapping table using the first composite key, and obtaining the test software version number of the target component from the second mapping table using the second composite key, includes: Obtain the first composite key and the second composite key corresponding to the target component; Based on the first composite key, obtain the first target software version number and the second target software version number of the target component from the first mapping table; Based on the second composite key, the first and second software version numbers of the target component are obtained from the second mapping table.

7. The software version comparison method according to claim 6, characterized in that, The step of comparing the target software version number with the software version number under test to obtain the software version comparison result of the target component includes: Compare the version number of the first target software with the version number of the first software under test; If the comparison is successful, the version number of the first software under test is stored in the first successful comparison list; In the event of a failed comparison, the version number of the first software under test is stored in the first failed comparison list; Compare the version number of the second target software with the version number of the second software to be tested; If the comparison is successful, the version number of the second software to be tested will be stored in the second successful comparison list; In the event of a failed comparison, the version number of the second software to be tested is stored in the second failed comparison list.

8. The software version comparison method according to claim 7, characterized in that, After obtaining the software version comparison results of the target component, the method further includes: Load the test report workbook and initialize the test report workbook to obtain the initialization worksheet of the test report workbook; In the initialization worksheet, create a first alignment success test report table corresponding to the first alignment success list, a first alignment failure test report table corresponding to the first alignment failure list, a second alignment success test report table corresponding to the second alignment success list, and a second alignment failure test report table corresponding to the second alignment failure list; Traverse the target comparison list, extract the names of the target components in the target comparison list by string slicing, and store the extracted names of the target components and the software version comparison results of the target components in the target comparison test report table; The target comparison list is any one of the first successful comparison list, the first failed comparison list, the second successful comparison list, and the second failed comparison list. The target comparison test report table is any one of the first successful comparison test report table corresponding to the first successful comparison list, the first failed comparison test report table corresponding to the first failed comparison list, the second successful comparison test report table corresponding to the second successful comparison list, and the second failed comparison test report table corresponding to the second failed comparison list.

9. A software version comparison system, characterized in that, The system includes: The first acquisition module is used to acquire a software version information table, which includes: a target software version information table and a software version information table to be tested. A construction module is used to construct a composite key based on the software version information table. The composite key includes a first composite key constructed based on the target software version information table and a second composite key constructed based on the software version information table under test. A generation module is used to generate a mapping relationship table based on the software version information table and the composite key, wherein the mapping relationship table includes a first mapping relationship table and a second mapping relationship table; The second acquisition module is used to obtain the target software version number of the target component from the first mapping relationship table through the first composite key, and to obtain the test software version number of the target component from the second mapping relationship table through the second composite key, wherein the target component is any one of a plurality of components; The comparison module is used to compare the target software version number with the software version number under test to obtain the software version comparison result of the target component.

10. An electronic device, characterized in that, It includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the software version comparison method as described in any one of claims 1-8.

Images