An open source declaration comparison test method, device and computer readable storage medium

Abstract

The application discloses a kind of open source declaration comparison test method, equipment and computer readable storage medium, wherein the method comprises: obtaining the open source declaration of equipment, and creating corresponding open source list according to open source declaration;Comparison of open source declaration and software item, version item and license item in open source list;Determine the software matching state, version matching state and license matching state of software item, version item and license item respectively;Through preset comparison table, output test result containing software item, version item, license item and matching state;The application improves the working efficiency of open source declaration consistency test, avoids manual comparison by manual, enhances comparison accuracy, also saves manpower and material resources cost.

Description

Technical Field

[0001] This invention relates to the field of software testing technology, and in particular to an open-source declaration comparison testing method, device, and computer-readable storage medium. Background Technology

[0002] In existing technologies, the open-source declaration consistency testing scheme for devices such as routers is as follows: First, the components, component version numbers, component license names, and license contents in the open-source declarations of routers and other devices on the WebUI (a graphical user interface framework) are manually searched and obtained; then, the archived list of open-source and third-party components of the product is obtained, and the differences between the components are manually compared; finally, the consistency between the components actually used in the router product, the above open-source declarations, and the above list of open-source and third-party components, as well as the completeness of the license contents, are determined.

[0003] It is easy to see that the above testing plan has the following main shortcomings: First, because there are many components in the open source declaration, it is easy to miss them when manually searching the above declarations or lists; Secondly, manual comparison is labor-intensive, time-consuming, and inefficient, resulting in a waste of human and material resources.

[0004] Therefore, how to optimize the open-source declaration consistency testing of devices such as routers, reduce workload, avoid manual comparison, and save human and material costs has become an urgent technical problem to be solved. Summary of the Invention

[0005] In order to overcome the shortcomings of the prior art, the present invention aims to provide an open source declaration comparison test method, device and computer-readable storage medium to solve the problems that there are many components in the current open source declarations, and it is easy to make omissions when manually searching the above declarations or lists. In addition, the manual comparison is labor-intensive, time-consuming and inefficient, resulting in a waste of human and material resources.

[0006] This invention proposes an open-source declaration comparison testing method, which includes: Obtain the device's open-source declaration and create a corresponding open-source list based on the declaration; Compare the open source declaration with the software, version, and license entries in the open source list; Determine the software matching status, version matching status, and license matching status for the software item, version item, and license item respectively; The test results, which include software items, version items, license items, and matching status, are output through a preset comparison table.

[0007] Optionally, obtain the device's open-source declaration and create a corresponding open-source list based on the declaration, specifically including: Download the open-source declaration from the device's graphical user interface framework; Obtain a list of open-source and third-party components for the corresponding devices.

[0008] Optionally, obtaining the device's open-source declaration and creating a corresponding open-source list based on the declaration also includes: Identify the software items in the open-source declaration; Extract the corresponding content from the product's open source and third-party component lists based on the software items in the open source declaration, and create an open source list based on the content.

[0009] Optionally, obtain the device's open-source declaration and create a corresponding open-source list based on the declaration, further including: Create a table file containing software items, version items, and license items; Extract all software information, version information, and license information from the open source declaration, and fill in the software, version, and license items respectively to create an output table for the open source declaration.

[0010] Optionally, the open-source declaration is compared with the software, version, and license entries in the open-source list, specifically including: In the output table, compare the software item with the software name in the open source list; If the software information in all software items is the same as the software name, or the proportion of the same information is greater than the preset value, then add three columns to the output table and fill in the software items, version items, and license items from the open source list, respectively.

[0011] Optionally, comparing the open-source declaration with the software, version, and license entries in the open-source list also includes: Add three more columns to the output table, which will be used as software matching status items, version matching status items, and license matching items, respectively. The software matching status, version matching status, and license matching status are recorded using the software matching status item, version matching status item, and license matching status item, respectively.

[0012] Optionally, the software matching status, version matching status, and license matching status of the software item, version item, and license item can be determined separately, specifically including: Determine one or more of the following comparison results for the software item, version item, and license item: same, different, or missing comparison; Fill in one or more comparison results into the software matching status item, version matching status item, and license matching item respectively.

[0013] Optionally, a pre-defined comparison table can be used to output test results that include software items, version items, license items, and matching status, specifically including: Preset the correspondence between each comparison result and color and / or font; In the software, version, and license sections of the open-source declaration, select appropriate colors and / or fonts to label one or more of the software, version, and license information according to their corresponding relationships.

[0014] The present invention also proposes an open source declaration comparison test device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the computer program is executed by the processor, it implements the steps of the open source declaration comparison test method as described in any of the preceding claims.

[0015] The present invention also proposes a computer-readable storage medium storing an open-source declaration comparison test program, wherein when the open-source declaration comparison test program is executed by a processor, the steps of the open-source declaration comparison test method as described in any of the preceding claims are implemented.

[0016] The present invention provides an open source declaration comparison test method, device, and computer-readable storage medium. It obtains the open source declaration of the device and creates a corresponding open source list based on the declaration. The open source declaration is compared with the software items, version items, and license items in the open source list. The software matching status, version matching status, and license matching status of the software items, version items, and license items are determined respectively. Test results containing the software items, version items, license items, and matching status are output through a preset comparison table. This invention improves the efficiency of open source declaration consistency testing, avoids manual comparison, enhances comparison accuracy, and saves manpower and material costs. Attached Figure Description

[0017] The present invention will be further described below with reference to the accompanying drawings and embodiments. In the accompanying drawings: Figure 1 This is a flowchart of the first embodiment of the open-source declaration comparison test method of the present invention; Figure 2 This is a flowchart of the second embodiment of the open-source declaration comparison test method of the present invention; Figure 3 This is a flowchart of the third embodiment of the open-source declaration comparison test method of the present invention; Figure 4 This is a flowchart of the fourth embodiment of the open-source declaration comparison test method of the present invention; Figure 5 This is a flowchart of the fifth embodiment of the open-source declaration comparison test method of the present invention; Figure 6 This is a flowchart of the sixth embodiment of the open-source declaration comparison test method of the present invention; Figure 7 This is a flowchart of the seventh embodiment of the open-source declaration comparison test method of the present invention; Figure 8 This is a flowchart of the eighth embodiment of the open-source declaration comparison test method of the present invention; Figure 9 This is a schematic diagram of the test directory for the open-source declaration comparison test method of this invention; Figure 10 This is a schematic diagram of the first table of the open-source declaration comparison test method of this invention; Figure 11 This is a schematic diagram of the second table of the open-source declaration comparison test method of this invention; Figure 12 This is a schematic diagram of the third table in the open-source declaration comparison test method of this invention. Detailed Implementation

[0018] It should be understood that the specific embodiments described herein are for illustrative purposes only and are not intended to limit the scope of the invention.

[0019] In the following description, the use of suffixes such as "module," "part," or "unit" to denote elements is solely for the purpose of illustrative purposes and has no specific meaning in itself. Therefore, "module," "part," or "unit" may be used interchangeably.

[0020] Example 1 Figure 1 This is a flowchart of the first embodiment of the open-source declaration comparison testing method of the present invention. An open-source declaration comparison testing method, the method comprising: S1. Obtain the open source declaration of the device and create a corresponding open source list based on the open source declaration; S2. Compare the software, version, and license items in the open source declaration with those in the open source list; S3. Determine the software matching status, version matching status, and license matching status of the software item, version item, and license item respectively. S4. Output test results including software items, version items, license items, and matching status through a preset comparison table.

[0021] In this embodiment, Pandas (an analyzer for Python data) and OpenPyXL (a Python library for processing spreadsheet files) of Python (a high-level programming language) are used, along with nested functions in Excel (spreadsheets), to achieve consistency testing of router open-source components and accuracy testing of license content.

[0022] In this embodiment, the open-source declaration of the device is obtained, and a corresponding open-source list is created based on the open-source declaration. Specifically, firstly, a Python environment is installed on the test machine (e.g., a personal computer, mobile terminal, etc.), and the system environment variables, as well as the aforementioned Pandas and OpenPyXL, are configured. Then, the open-source declaration document (.txt format) is downloaded from the WebUI (a graphical user interface framework) of the device such as the router, and a preset Python script is run to extract all components, their corresponding component names, their corresponding license names, and their corresponding license contents from the document. Finally, an OPEN SOURCESOFTWARE.xlsx table file is created. The table file includes four columns: software, version, license, and license contents, which are used to record all the extracted components, their corresponding component names, their corresponding license names, and their corresponding license contents, respectively.

[0023] In this embodiment, the software, version, and license items in the open-source declaration and the open-source list are compared. Specifically, firstly, the list of open-source products and their three component providers is obtained. Similarly, this list is a table file. For example, three new columns are added to the table file to record all the components of the open-source products and their three component providers, their corresponding component names, and their corresponding license names. Then, the contents of OPEN SOURCE SOFTWARE.xlsx are compared with the contents of the list of open-source products and their three component providers. For example, the list items in the first three columns of OPEN SOURCE SOFTWARE.xlsx are compared with the list items in the newly added three columns.

[0024] In this embodiment, the software matching status, version matching status, and license matching status of the software item, version item, and license item are determined respectively. Specifically, the comparison results are directly output in the above table file, and the differences are highlighted in red, so that testers can obtain the test results conveniently and efficiently.

[0025] In this embodiment, a preset comparison table is used to output test results including software items, version items, license items, and matching status. Specifically, in order to preserve the original values ​​in the OPEN SOURCE SOFTWARE.txt downloaded by the router and other devices from the WebUI, the above comparison results are processed using preset Excel nested functions to determine each matching status in the comparison results.

[0026] The beneficial effects of this embodiment are as follows: by obtaining the open source declaration of the device and creating a corresponding open source list based on the open source declaration; comparing the open source declaration with the software items, version items, and license items in the open source list; determining the software matching status, version matching status, and license matching status of the software items, version items, and license items respectively; and outputting test results containing the software items, version items, license items, and matching status through a preset comparison table; thereby improving the efficiency of open source declaration consistency testing, avoiding manual comparison, enhancing comparison accuracy, and saving manpower and material costs.

[0027] Example 2 Figure 2 This is a flowchart of the second embodiment of the open source declaration comparison and testing method of the present invention. Based on the above embodiment, the open source declaration of the device is obtained, and a corresponding open source list is created according to the open source declaration, specifically including: S11. Download the open-source declaration from the device's graphical user interface framework; S12. Obtain the list of open-source and third-party components corresponding to the device.

[0028] Please refer to Figure 9 In this embodiment, a test script is created and stored in a preset directory; furthermore, an open-source declaration is downloaded, set to .txt format, and placed in the same directory as the test script; In this embodiment, an archived list of open-source and third-party components for the product is obtained and placed in the same directory as the test script. This list is in .xlsx format.

[0029] In this embodiment, the comparison results generated by the subsequent running of the test script will also be automatically saved to this directory.

[0030] The beneficial effect of this embodiment is that by grouping test scripts, open source declarations, product open source, and third-party component lists into the same directory, test scripts can centrally process open source declarations, product open source, and third-party component lists, which reduces the likelihood of errors and improves processing efficiency.

[0031] Example 3

[0032] Figure 3 This is a flowchart of the third embodiment of the open source declaration comparison and testing method of the present invention. Based on the above embodiment, the open source declaration of the device is obtained, and a corresponding open source list is created according to the open source declaration. The method also includes: S13. Identify the software items in the open-source declaration; S14. Extract the corresponding content from the product's open source and third-party component lists based on the software items in the open source declaration, and create an open source list based on the content.

[0033] In this embodiment, one approach is to directly use the archived list of open-source products and third-party components as the open-source list for this embodiment, thereby saving the preprocessing steps; in this list, the software involved has more field types than the software field types in the above-mentioned open-source declaration, thereby avoiding comparison omissions.

[0034] In this embodiment, another approach is to first determine the software items in the open-source declaration, then extract the corresponding content from the product's open-source and third-party component lists based on the software items in the open-source declaration, and create an open-source list based on the content. This ensures that the types of software involved in this list are the same as the types of software in the aforementioned open-source declaration, saving subsequent comparison processes and making the output results more concise.

[0035] Example 4 Figure 4 This is a flowchart of the fourth embodiment of the open source declaration comparison and testing method of the present invention. Based on the above embodiment, the open source declaration of the device is obtained, and a corresponding open source list is created according to the open source declaration, further including: S15. Create a table file containing software items, version items, and license items; S16. Extract all software information, version information, and license information from the open source declaration, and fill in the software item, version item, and license item respectively as the output table of the open source declaration.

[0036] In this embodiment, the component name, version number, license name, and license content are extracted from OPEN_SOURCE_SOFTWARE_NOTICE.txt. The first and second columns are the software and version items, respectively, used to record the component name and version number. The third column is the license item, used to record the license name. If a component has multiple licenses, they are separated by spaces, but all are recorded in the third column. Furthermore, this embodiment creates a fourth column based on the above three columns, which is the license content item, used to record the specific license content.

[0037] The beneficial effect of this embodiment is that by extracting all software information, version information, and license information from the open source declaration and filling them into software items, version items, and license items respectively, as an output table of the open source declaration, it is convenient to compare and mark the row contents of each pair of columns when running the test script, so that testers can intuitively obtain the test results.

[0038] Example 5 Figure 5This is a flowchart of the fifth embodiment of the open source declaration comparison and testing method of the present invention. Based on the above embodiment, the open source declaration is compared with the software items, version items, and license items in the open source list, specifically including: S21. In the output table, compare the software item with the software name in the open source list; S22. If the software information in all software items is the same as the software name, or the proportion of the same information is greater than the preset value, then add three columns to the output table and fill in the software items, version items and license items from the open source list respectively.

[0039] In this embodiment, the software, version, and license in OPEN SOURCE SOFTWARE.xlsx are compared with the software, version, and license in the product open source and third-party component list.xlsx, and the differences are compared and output based on the software item column in OPEN SOURCESOFTWARE.xlsx.

[0040] In this embodiment, in OPEN SOURCE SOFTWARE.xlsx, the software item, version item, and license item are labeled A, B, and C respectively from left to right. Similarly, to the right of column C, the software, version, and license from Product Open Source and Third-Party Component List.xlsx are recorded from left to right and labeled D, E, and F respectively. In this embodiment, if the software field in column A of OPEN SOURCE SOFTWARE.xlsx is the same as the software field in Product Open Source and Third-Party Component List.xlsx, or if the number of identical fields exceeds a first preset percentage (e.g., 70%), then the corresponding software, version, and license from Product Open Source and Third-Party Component List.xlsx are entered into columns D, E, and F in the same row. Based on this, a comparison is subsequently performed between columns B and E, and between columns C and F, with any discrepancies highlighted in red.

[0041] In this embodiment, the license content items are recorded to the right of column C, denoted as column D. In this embodiment, if the software field in column A of OPENSOURCE SOFTWARE.xlsx has a greater than second preset ratio (e.g., 30%) than the same field in the software field of Product Open Source and Third-Party Component List.xlsx, but is less than or equal to the first preset ratio, then the corresponding software, version, and license from Product Open Source and Third-Party Component List.xlsx are filled into columns E, F, and G of the same row, respectively. Based on this, the comparison between columns B and F, and between columns C and G are performed subsequently, and the fields with differences are highlighted in red. The matching status is output to the right of column G, denoted as column H.

[0042] In this embodiment, if the software field in column A of OPEN SOURCE SOFTWARE.xlsx is different from the software field in Product Open Source and Third-Party Component List.xlsx, then columns E, F, and G in the same row are left blank, and the corresponding software, version, and license from Product Open Source and Third-Party Component List.xlsx are not filled in. The strings in columns A, B, and C are highlighted in red, and then the software field comparison is performed on the next row. This process is repeated row by row.

[0043] In this embodiment, if there are n rows of software in column A of OPEN SOURCE SOFTWARE.xlsx, then the software and corresponding versions and licenses that are not matched in the open source and third-party component list.xlsx will be filled in columns E, F, and G of row n+1; furthermore, the strings in columns E, F, and G will be highlighted in red, and the matching status will be output in column H.

[0044] The beneficial effect of this embodiment is that the comparison results of the differences output by the above table make the test content and test results clear and concise, and the comprehensiveness and completeness of the test are higher.

[0045] Example 6 Figure 6 This is a flowchart of the sixth embodiment of the open source declaration comparison and testing method of the present invention. Based on the above embodiment, the comparison of the open source declaration with the software items, version items, and license items in the open source list also includes: S23. Add three more columns to the output table, as software matching status item, version matching status item and license matching item respectively; S24. Record the software matching status, version matching status, and license matching status respectively through the software matching status item, version matching status item, and license matching item.

[0046] Please refer to Figure 10 In this embodiment, the above column H is split into three columns, which are respectively used as software matching status items, version matching status items and license matching items, and record the various matching statuses of each row in detail; or, a new column is added to the right of the above column H as a description of the matching status, denoted as column I, which briefly records the differences and missing information in the software matching status, version matching status and license matching status.

[0047] Please refer to Figure 11 Based on the above embodiments, one approach is to directly record the software matching status, version matching status, and license matching status in column H; while another approach based on this embodiment is to add three more columns as software matching status items, version matching status items, and license matching items, respectively used to record the software matching status, version matching status, and license matching status.

[0048] Please refer to Figure 12 In this embodiment, another approach is to record mismatch information in the software matching status, version matching status, and license matching status in column H, thereby simplifying the display content of this column and making it easier for testers to intuitively grasp the test results. Furthermore, three additional columns are added to the right of column H as software matching status items, version matching status items, and license matching items, respectively used to record detailed information on the software matching status, version matching status, and license matching status, thereby enabling testers to fully grasp the test results.

[0049] Example 7 Figure 7 This is a flowchart of the seventh embodiment of the open-source declaration comparison test method of the present invention. Based on the above embodiment, the software matching status, version matching status, and license matching status of the software item, version item, and license item are determined respectively, specifically including: S31. Determine one or more comparison results among the software item, version item, and license item, including identical comparison, different comparison, and missing comparison; S32. Fill one or more comparison results into the software matching status item, version matching status item, and license matching item respectively.

[0050] In this embodiment, three additional columns are added to the right of column H above, which serve as software matching status items, version matching status items, and license matching items, respectively. The results of one or more of the above comparisons are then filled into the software matching status items, version matching status items, and license matching items accordingly.

[0051] Please continue to refer to this. Figure 12 In this embodiment, the software matching status item, version matching status item, and license matching status item are used to record detailed information about the software matching status, version matching status, and license matching status, respectively, so that testers can have a comprehensive understanding of the test results.

[0052] Example 8 Figure 8 This is a flowchart of the eighth embodiment of the open-source declaration comparison test method of the present invention. Based on the above embodiment, the test results, including software items, version items, license items, and matching status, are output through a preset comparison table, specifically including: S41. Preset the correspondence between each comparison result and color and / or font; S42. In the software, version, and license items of the open source declaration, select the corresponding color and / or font to mark one or more of the software information, version information, and license information according to the corresponding relationship.

[0053] In this embodiment, the above correspondence allows each comparison result to be represented more intuitively. For example, different characters in the software item are marked in red, and different characters in the license item are marked in bold. This makes it easier for testers to quickly extract the required information contained in the test results according to the current test requirements.

[0054] Example 9 Based on the above embodiments, the present invention also proposes an open source declaration comparison test device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the computer program is executed by the processor, it implements the steps of the open source declaration comparison test method as described in any of the above embodiments.

[0055] It should be noted that the above-described device embodiments and method embodiments belong to the same concept. The specific implementation process can be found in the method embodiments, and the technical features in the method embodiments are also applicable to the device embodiments, which will not be repeated here.

[0056] Example 10 Based on the above embodiments, the present invention also proposes a computer-readable storage medium storing an open-source declaration comparison test program, wherein when the open-source declaration comparison test program is executed by a processor, the steps of the open-source declaration comparison test method as described in any of the above claims are implemented.

[0057] It should be noted that the above-described medium embodiments and method embodiments belong to the same concept. The specific implementation process can be found in the method embodiments, and the technical features in the method embodiments are also applicable to the medium embodiments, which will not be repeated here.

[0058] The open source declaration comparison test method, device, and computer-readable storage medium of this invention obtain the open source declaration of the device and create a corresponding open source list based on the open source declaration; compare the open source declaration with the software items, version items, and license items in the open source list; determine the software matching status, version matching status, and license matching status of the software items, version items, and license items respectively; and output the test results containing the software items, version items, license items, and matching status through a preset comparison table. This improves the efficiency of open source declaration consistency testing, avoids manual comparison, enhances comparison accuracy, and saves manpower and material costs.

[0059] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus 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 apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0060] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0061] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of the present invention.

[0062] The embodiments of the present invention have been described above with reference to the accompanying drawings. However, the present invention is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of the present invention without departing from the spirit and scope of the claims. All of these forms are within the protection scope of the present invention.

Claims

1. An open-source declaration comparison testing method, characterized in that, The method includes: Obtain the device's open-source declaration and create a corresponding open-source list based on the declaration; Compare the open source declaration with the software items, version items, and license items in the open source list; Determine the software matching status, version matching status, and license matching status of the software item, the version item, and the license item, respectively; The test results, which include the software item, the version item, the license item, and the matching status, are output through a preset comparison table.

2. The open-source declaration comparison test method according to claim 1, characterized in that, The process of obtaining the device's open-source declaration and creating a corresponding open-source list based on the declaration specifically includes: Download the open-source declaration from the device's graphical user interface framework; Obtain the list of open-source and third-party components corresponding to the device.

3. The open-source declaration comparison test method according to claim 2, characterized in that, The step of obtaining the open-source declaration of the device and creating a corresponding open-source list based on the open-source declaration also includes: Identify the software items in the aforementioned open-source declaration; Based on the software items in the open-source declaration, extract the corresponding content from the product's open-source and third-party component list, and create the open-source list based on the content.

4. The open-source declaration comparison test method according to claim 1, characterized in that, The step of obtaining the open-source declaration of the device and creating a corresponding open-source list based on the open-source declaration further includes: Create a table file containing the software item, the version item, and the license item; Extract all software information, version information, and license information from the open source declaration, and fill them into the software item, version item, and license item respectively, as the output table of the open source declaration.

5. The open-source declaration comparison test method according to claim 4, characterized in that, The comparison of the open-source declaration with the software items, version items, and license items in the open-source list specifically includes: In the output table, the software item is compared with the software name in the open source list; If the software information in all the software items is the same as the software name, or the proportion of the same information is greater than a preset value, then three new columns are added to the output table, and the software items, version items, and license items from the open source list are filled in respectively.

6. The open-source declaration comparison test method according to claim 5, characterized in that, The comparison of the open-source declaration with the software items, version items, and license items in the open-source list also includes: Three new columns are added to the output table, serving as software matching status, version matching status, and license matching status, respectively. The software matching status, version matching status, and license matching status are recorded using the software matching status item, the version matching status item, and the license matching status item, respectively.

7. The open-source declaration comparison test method according to claim 6, characterized in that, The step of determining the software matching status, version matching status, and license matching status of the software item, the version item, and the license item respectively specifically includes: Determine one or more comparison results among the software item, the version item, and the license item, including identical comparisons, different comparisons, and missing comparisons; One or more of the comparison results are respectively filled into the software matching status item, the version matching status item, and the license matching item.

8. The open-source declaration comparison test method according to claim 7, characterized in that, The step of outputting test results, including the software item, the version item, the license item, and the matching status, through a preset comparison table specifically includes: The correspondence between each comparison result and color and / or font is preset; In the software, version, and license items of the open-source declaration, select appropriate colors and / or fonts to label one or more of the software information, version information, and license information according to the correspondence.

9. An open-source declaration comparison testing device, characterized in that, The device includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the steps of the open-source declaration comparison test method as described in any one of claims 1 to 8.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores an application open source declaration comparison test program, which, when executed by a processor, implements the steps of the open source declaration comparison test method as described in any one of claims 1 to 8.

Images