Software test demand analysis method and equipment based on XML configuration file

Abstract

A software test demand analysis method, apparatus and device based on an XML configuration file, and a storage medium, the method comprising: determining whether an XML file exists in a test process folder by traversing the test process folder; if it is determined that the XML file exists in the test process folder, obtaining storage path structure information of the XML file and element information of the XML file; writing an XML file analysis tool according to the element information of the XML file; according to the XML file analysis tool and the storage path structure information of the XML file, test requirement analysis is conducted on the XML file to extract data in the XML file, the extracted data are written into a preset Excel template according to a preset rule to generate an Excel file, and the problems that in the related technology, the XML file is too long, and the Excel file cannot be generated are solved. In the prior art, a tester needs to read file contents word by word and sentence by sentence, and the technical problems of difficulty in visually analyzing test requirements and identifying implicit test points exist.

Description

Technical Field

[0001] This application relates to the technical field of software testing, and particularly to a method, device, equipment and computer-readable storage medium for software test requirement analysis based on an XML configuration file. Background Art

[0002] With the continuous increase in the complexity and performance of aerospace equipment, the reliability of aerospace equipment software can not only improve combat effectiveness and reduce the full life cycle cost, but also be related to the success or failure of the entire equipment development. As an important means of software assurance, software testing runs through the entire life cycle of the aerospace equipment system, and software test requirement analysis is the key link of software testing. Only on the premise of determining software test requirements can test cases be designed comprehensively and effectively.

[0003] The main basis for traditional software test requirement analysis is the requirement document. However, in the actual development process of aerospace equipment software, the requirement document often cannot accurately, completely and specifically reflect user requirements and program characteristics. Therefore, it is insufficient to test software based on the requirement document. Testers must conduct further test requirement analysis on the basis of the limited content of the requirement document to fully explore the software requirements missing and unclear in the document.

[0004] In the situation of the continuous improvement of the complexity of aerospace equipment software, XML files with the characteristics of cross-platform sharing and exchange of test requirement data have become a common control flow description data file and are widely used in the field of aerospace equipment software. Although the XML file has a clear structure, it is relatively long and difficult to read. If the traditional manual review method is used, testers need to read the file content word by word. Even with a large amount of time and labor costs invested, there are still problems such as difficulty in intuitively analyzing test requirements and identifying implicit test points.

[0005] Therefore, how to use the characteristics of XML files to quickly and clearly analyze test requirements has become an urgent problem to be solved. Summary of the Invention

[0006] This application provides a method, device, equipment and computer-readable storage medium for software test requirement analysis based on an XML configuration file, which can solve the technical problems in the prior art that the XML file is relatively long and difficult to read, and when using the traditional manual review method, testers need to read the file content word by word, and there are still problems such as difficulty in intuitively analyzing test requirements and identifying implicit test points even with a large amount of time and labor costs invested.

[0007] In a first aspect, an embodiment of this application provides a method for software test requirement analysis based on an XML configuration file. The method for software test requirement analysis based on an XML configuration file includes:

[0008] Traverse the test process folder to determine whether there is an XML file in the test process folder;

[0009] If it is determined that there is the XML file in the test process folder, obtain the storage path structure information of the XML file and the element information of the XML file;

[0010] Write an XML file parsing tool according to the element information of the XML file;

[0011] Perform test requirement analysis on the XML file according to the XML file parsing tool and the storage path structure information of the XML file to extract the data in the XML file, and write the extracted data into a preset Excel template according to preset rules to generate an Excel file.

[0012] Combined with the first aspect, in one embodiment, the writing of the XML file parsing tool according to the element information of the XML file includes:

[0013] Invoke a preset Python language writing tool;

[0014] Write an XML file parsing tool based on the element information of the XML file through the preset Python language writing tool, wherein the element information of the XML file includes tags and attributes.

[0015] Combined with the first aspect, in one embodiment, the tags include ProcessCluster, ProcessItem, ProcessModule, and ProcessPoint.

[0016] Combined with the first aspect, in one embodiment, the attributes include actionCMD, check, and get.

[0017] Combined with the first aspect, in one embodiment, the performing of test requirement analysis on the XML file according to the XML file parsing tool and the storage path structure information of the XML file to extract the data in the XML file includes:

[0018] Traverse the test process folder through the storage path structure information of the XML file to determine the XML file to be parsed;

[0019] Perform test requirement analysis on the XML file through the XML file parsing tool to extract the data in the XML file, wherein the data is the corresponding data of the element information.

[0020] In combination with the first aspect, in one implementation, the step of writing the extracted data into a preset Excel template according to preset rules to generate an Excel file includes:

[0021] Group the obtained data, where the data is extracted from each of the XML files;

[0022] Write each group of the data into the preset Excel template in sequence to generate an Excel file.

[0023] In combination with the first aspect, in one implementation, the step of traversing the test process folder to determine whether there is an XML file in the test process folder includes:

[0024] Traverse the test process folder to determine whether there is an XML file under the test process folder;

[0025] If it is determined that there is no XML file under the test process folder, then traverse each subfolder in the test process folder to determine whether there is an XML file in each subfolder of the test process folder.

[0026] In a second aspect, an embodiment of the present application provides a software test requirement analysis device based on an XML configuration file. The software test requirement analysis device based on the XML configuration file includes:

[0027] A determination module, configured to traverse the test process folder to determine whether there is an XML file in the test process folder;

[0028] An acquisition module, configured to, if it is determined that there is the XML file in the test process folder, acquire the storage path structure information of the XML file and the element information of the XML file;

[0029] A writing module, configured to write an XML file parsing tool according to the element information of the XML file;

[0030] An extraction and writing module, configured to perform test requirement analysis on the XML file according to the XML file parsing tool and the storage path structure information of the XML file to extract the data in the XML file, and write the extracted data into a preset Excel template according to preset rules to generate an Excel file.

[0031] In a third aspect, an embodiment of the present application provides a software test requirement analysis device based on an XML configuration file. The software test requirement analysis device based on the XML configuration file includes a processor, a memory, and a software test requirement analysis program based on the XML configuration file stored on the memory and executable by the processor. When the software test requirement analysis program based on the XML configuration file is executed by the processor, the steps of the software test requirement analysis method based on the XML configuration file as described above are implemented.

[0032] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium with a software test requirement analysis program based on an XML configuration file stored thereon. When the software test requirement analysis program based on the XML configuration file is executed by a processor, the steps of the software test requirement analysis method based on the XML configuration file as described above are implemented.

[0033] The beneficial effects brought by the technical solutions provided by the embodiments of the present application include:

[0034] By traversing the test process folder, it is determined whether there is an XML file in the test process folder; if it is determined that there is an XML file in the test process folder, the storage path structure information of the XML file and the element information of the XML file are obtained; according to the element information of the XML file, an XML file parsing tool is written; according to the XML file parsing tool and the storage path structure information of the XML file, test requirement analysis is performed on the XML file to extract the data in the XML file, and the extracted data is written into a preset Excel template according to preset rules to generate an Excel file, which solves the technical problems in the related art that XML files are relatively long and difficult to read. Using traditional manual review methods, testers need to read the file content word by word. Even with a large amount of time and labor costs invested, there are still difficulties in intuitively analyzing test requirements and identifying implicit test points. It realizes the automatic extraction of test points of software in XML files, greatly reduces the time and labor expenses of manually reading XML files, avoids the risk of human review errors caused by the long data of XML files, and effectively improves the extraction efficiency of test requirements. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] Figure 1 It is a flowchart of the first embodiment of the software test requirement analysis method based on the XML configuration file of the present application;

[0036] Figure 2 It is a schematic diagram of the tree structure of the present application;

[0037] Figure 3Schematic diagram of functional modules of an embodiment of a software test requirement analysis device based on an XML configuration file according to the present application;

[0038] Figure 4 Schematic diagram of the hardware structure of a software test requirement analysis device based on an XML configuration file involved in the solution of an embodiment of the present application. Detailed implementation manners

[0039] In order to enable those skilled in the art to better understand the solution of the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

[0040] First, some technical terms in the present application are explained to facilitate the understanding of the present application by those skilled in the art.

[0041] To make the purpose, technical solution and advantages of the present application clearer, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings.

[0042] In a first aspect, an embodiment of the present application provides a software test requirement analysis method based on an XML configuration file.

[0043] In one embodiment, referring to Figure 1 , Figure 1 is a schematic flowchart of the first embodiment of the software test requirement analysis method based on an XML configuration file according to the present application. As Figure 1 shown, the software test requirement analysis method based on an XML configuration file includes:

[0044] Step S10: Traverse the test process folder to determine whether there is an XML file in the test process folder;

[0045] Exemplarily, traverse the test process folder to determine whether it contains an XML file. For example, the test process folder includes multiple files. Obtain the suffix name of each file and determine whether the suffix name of each file contains the XML field. If the suffix name of the file carries the XML field, it is determined that there is an XML file in the test process folder; if it is determined that the suffix name of the file does not carry the XML field, it is determined that there is no XML file in the test process folder.

[0046] Specifically, traversing the test process folder to determine whether there is an XML file in the test process folder includes: traversing the test process folder to determine whether there is an XML file under the test process folder; if it is determined that there is no XML file under the test process folder, then traverse each subfolder in the test process folder to determine whether there is an XML file in each of the subfolders of the test process folder.

[0047] Exemplarily, traverse the test process folder to determine whether it contains an XML file. For example, the test process folder includes multiple files. Obtain the suffix name of each file and determine whether the suffix name of each file has an XML field. If the suffix name of the file has an XML field, then determine that there is an XML file in the test process folder; if it is determined that the suffix name of the file does not have an XML field, then traverse each subfolder in the test process folder, obtain the suffix names of each subfile in each subfolder, and if it is determined that the suffix name of any subfile has an XML field, then determine that there is an XML file in the test process folder.

[0048] Step S20: If it is determined that there is the XML file in the test process folder, then obtain the storage path structure information of the XML file and the element information of the XML file;

[0049] Exemplarily, if it is determined that there is the XML file in the test process folder, then analyze the XML file to obtain the storage path format of the XML file. The purpose is to ensure that the parsing tool can read the correct target XML file according to the storage structure, avoid the situation that the parsing tool cannot read the general operation XML or needs to analyze the general operation XML separately, and also avoid reading XML files that should not be read. For example: when performing test requirement analysis on control process 1, the operations of control process 1 are written in control process 1.xml. If control process 1-3 contains the same operations, the same operations are written in general module 1.xml. The storage structure should be that the test process folder contains control process 1.xml and the "Module" folder, and general module 1.xml is in the "Module" folder. After the analysis is completed, when extracting test points through the xml file parsing tool, it will first analyze control process 1.xml. When extracting the general module of this file, it will then extract the general operations through general module 1.xml in the "Module" folder to ensure a comprehensive analysis of the test points in the control process and general operations at one time.

[0050] Obtain the element information of the XML file. The tags include ProcessCluster, ProcessItem, ProcessModule, and ProcessPoint. The attributes include actionCMD, check, and get.

[0051] Step S30: Write an XML file parsing tool according to the element information of the XML file;

[0052] Exemplarily, write an XML file parsing tool based on the obtained element information of the XML file. For example, use the Python language to write the tool, traverse the files in the folder and the tags and attributes in the tree structure as shown, extract the tags and attributes and write them into an Excel file to write the XML file parsing tool. Figure 2 As shown, extract and write the tags and attributes into an Excel file to write the XML file parsing tool.

[0053] Specifically, call the pre-set Python language writing tool; write an XML file parsing tool based on the element information of the XML file through the pre-set Python language writing tool, where the element information of the XML file includes tags and attributes.

[0054] Step S40: Perform test requirement analysis on the XML file according to the XML file parsing tool and the storage path structure information of the XML file, extract the data in the XML file, and write the extracted data into a pre-set Excel template according to pre-set rules to generate an Excel file.

[0055] Exemplarily, traverse the test process folder through the storage path structure information of the XML file to determine the XML files to be parsed; perform test requirement analysis on the XML files through the XML file parsing tool to extract the data in the XML files, where the data is the corresponding data of the element information. For example, the data corresponding to the tags and the data corresponding to the attributes. Group the obtained data, where the data is extracted from each XML file; write each group of data into the pre-set Excel template in turn to generate an Excel file.

[0056] Effectively make up for problems such as incorrect and incomplete description of software requirement documents leading to errors and omissions in test requirement analysis, help to fully explore the implicit requirements in aerospace equipment software, and effectively ensure the sufficiency of software test case design;

[0057] Using the Python language to write a file parsing tool can automatically extract the test points of the software in the XML file, greatly reducing the time and labor costs of manually reading the XML file, avoiding the risk of human review errors caused by the long XML file data, and effectively improving the extraction efficiency of test requirements;

[0058] The test points extracted after parsing are presented in the format of an Excel file, with clear levels and intuitive display, which helps testers quickly and clearly understand the process content and intuitively and comprehensively extract the test points.

[0059] The file parsing tool adopted is sensitive to XML file format errors. Since XML files have very strict format requirements, it is inevitable to make mistakes when writing manually, and the efficiency of manual troubleshooting is low and the time cost is high. In the process of parsing XML files in the present invention, if there are format exceptions, they can be quickly located, significantly reducing the workload of manual troubleshooting;

[0060] Using an automated method instead of manual work solves the problem of insufficient test requirement analysis caused by human errors. Combining XML files and software requirement documents for test case design reduces costs and increases efficiency, improves software test sufficiency, and effectively guarantees the quality of aerospace equipment software.

[0061] In this embodiment, by traversing the test process folder, it is determined whether there is an XML file in the test process folder; if it is determined that there is the XML file in the test process folder, the storage path structure information of the XML file and the element information of the XML file are obtained; according to the element information of the XML file, an XML file parsing tool is written; according to the XML file parsing tool and the storage path structure information of the XML file, test requirement analysis is performed on the XML file to extract the data in the XML file, and the extracted data is written into a preset Excel template according to preset rules to generate an Excel file, solving the technical problem in the related art that XML files are relatively long and difficult to read. Using the traditional manual review method, testers need to read the file content word by word. Even with a large amount of time and labor costs invested, there are still difficulties in intuitively analyzing test requirements and identifying implicit test points. It realizes the automated extraction of software test points in XML files, greatly reducing the time and labor expenses of manually reading XML files, avoiding the risk of human review errors caused by the long XML file data, and effectively improving the extraction efficiency of test requirements.

[0062] In a second aspect, an embodiment of the present application further provides a software test requirement analysis device based on an XML configuration file.

[0063] In one embodiment, referring to Figure 3 , Figure 3 is a schematic diagram of the functional modules of an embodiment of the software test requirement analysis device based on the XML configuration file of the present application. As Figure 3 shown, the software test requirement analysis device based on the XML configuration file includes:

[0064] A determination module 10 for traversing a test process folder to determine whether an XML file exists in the test process folder;

[0065] An acquisition module 20 for, if it is determined that the XML file exists in the test process folder, acquiring the storage path structure information of the XML file and the element information of the XML file;

[0066] A writing module 30 for writing an XML file parsing tool according to the element information of the XML file;

[0067] An extraction and writing module 40 for performing test requirement analysis on the XML file according to the XML file parsing tool and the storage path structure information of the XML file to extract the data in the XML file and writing the extracted data into a preset Excel template according to preset rules to generate an Excel file.

[0068] Further, in an embodiment, the writing module 30 is configured to:

[0069] Invoke a preset Python language writing tool;

[0070] Write an XML file parsing tool based on the element information of the XML file through the preset Python language writing tool, wherein the element information of the XML file includes tags and attributes.

[0071] Further, in an embodiment, the tags include ProcessCluster, ProcessItem, ProcessModule, and ProcessPoint.

[0072] Further, in an embodiment, the attributes include actionCMD, check, and get.

[0073] Further, in an embodiment, the extraction and writing module 40 is configured to:

[0074] Traverse the test process folder through the storage path structure information of the XML file to determine the XML file to be parsed;

[0075] Perform test requirement analysis on the XML file through the XML file parsing tool to extract the data in the XML file, wherein the data is the data corresponding to the element information.

[0076] Further, in an embodiment, the extraction and writing module 40 is configured to:

[0077] Group the obtained data, wherein the data includes that extracted from each of the XML files;

[0078] Write the data of each group into a preset Excel template in sequence to generate an Excel file.

[0079] Further, in one embodiment, the determination module 10 is used for:

[0080] Traverse the test process folder to determine whether there is an XML file under the test process folder;

[0081] If it is determined that there is no XML file under the test process folder, traverse each subfolder in the test process folder to determine whether there is an XML file in each of the subfolders of the test process folder.

[0082] Among them, the function implementation of each module in the software test requirement analysis device based on the XML configuration file corresponds to each step in the embodiment of the software test requirement analysis method based on the XML configuration file, and its function and implementation process will not be elaborated here one by one.

[0083] In a third aspect, an embodiment of the present application provides a software test requirement analysis device based on an XML configuration file. The software test requirement analysis device based on the XML configuration file can be a device with data processing functions such as a personal computer (PC), a laptop computer, a server, etc.

[0084] Refer to Figure 4 , Figure 4 is a schematic hardware structure diagram of the software test requirement analysis device based on the XML configuration file involved in the solution of the embodiment of the present application. In the embodiment of the present application, the software test requirement analysis device based on the XML configuration file may include a processor, a memory, a communication interface, and a communication bus.

[0085] Among them, the communication bus can be of any type and is used to interconnect the processor, the memory, and the communication interface.

[0086] The communication interface includes input / output (I / O) interfaces, physical interfaces, and logical interfaces, etc., which are used to implement the interfaces for interconnecting the components inside the software test requirement analysis device based on the XML configuration file, and the interfaces for interconnecting the software test requirement analysis device based on the XML configuration file with other devices (such as other computing devices or user devices). The physical interface can be an Ethernet interface, a fiber optic interface, an ATM interface, etc.; the user device can be a display screen (Display), a keyboard (Keyboard), etc.

[0087] The memory can be various types of storage media, such as random access memory (RAM), read-only memory (ROM), non-volatile RAM (NVRAM), flash memory, optical memory, hard disk, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), etc.

[0088] The processor can be a general-purpose processor, which can call the software test requirement analysis program based on the XML configuration file stored in the memory and execute the software test requirement analysis method based on the XML configuration file provided by the embodiments of the present application. For example, the general-purpose processor can be a central processing unit (CPU). Among them, the method executed when the software test requirement analysis program based on the XML configuration file is called can refer to the various embodiments of the software test requirement analysis method based on the XML configuration file of the present application, which will not be elaborated here.

[0089] Those skilled in the art can understand that Figure 4 the hardware structure shown in does not constitute a limitation to the present application, and may include more or fewer components than shown in the figure, or combine certain components, or have different component arrangements.

[0090] In a fourth aspect, the embodiments of the present application further provide a computer-readable storage medium.

[0091] The computer-readable storage medium of the present application stores a software test requirement analysis program based on an XML configuration file. When the software test requirement analysis program based on the XML configuration file is executed by a processor, the steps of the software test requirement analysis method based on the XML configuration file as described above are implemented.

[0092] Among them, the method implemented when the software test requirement analysis program based on the XML configuration file is executed can refer to the various embodiments of the software test requirement analysis method based on the XML configuration file of the present application, which will not be elaborated here.

[0093] It should be noted that the serial numbers of the embodiments of the present application above are only for description and do not represent the advantages or disadvantages of the embodiments.

[0094] In the description of the specification, claims and the above-mentioned drawings of the present application, the terms "comprising", "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally further include steps or units not listed, or may optionally further include other steps or units inherent to these processes, methods, products or devices. The descriptions such as "first", "second" and "third" are used to distinguish different objects, etc., and do not represent a sequence, nor do they limit that "first", "second" and "third" are of different types.

[0095] In the description of the embodiments of the present application, terms such as "exemplary", "for example" or "for instance" are used to represent examples, illustrations or explanations. Any embodiment or design solution described as "exemplary", "for example" or "for instance" in the embodiments of the present application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Rather, the use of terms such as "exemplary", "for example" or "for instance" is intended to present relevant concepts in a specific manner.

[0096] In the description of the embodiments of the present application, unless otherwise specified, " / " means "or". For example, A / B may represent A or B; "and / or" in the text is merely a description of the association relationship between associated objects, indicating that there can be three relationships. For example, A and / or B may represent: A exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiments of the present application, "a plurality of" means two or more than two.

[0097] In some processes described in the embodiments of the present application, there are a plurality of operations or steps that appear in a specific order. However, it should be understood that these operations or steps may not be executed in the order in which they appear in the embodiments of the present application or may be executed in parallel. The serial numbers of the operations are only used to distinguish different operations, and the serial numbers themselves do not represent any execution order. In addition, these processes may include more or fewer operations, and these operations or steps may be executed in order or in parallel, and these operations or steps may be combined.

[0098] Through the description of the above embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus a necessary general hardware platform. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation. Based on such an understanding, the technical solution of the present application, in essence, 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 as described above (such as ROM / RAM, magnetic disk, optical disc), and includes several instructions to enable a terminal device to execute the methods described in the various embodiments of the present application.

[0099] The above are only the preferred embodiments of the present application, and do not limit the patent scope of the present application accordingly. Any equivalent structure or equivalent process transformation made by using the content of the specification and drawings of the present application, or directly or indirectly applied in other related technical fields, shall be similarly included in the patent protection scope of the present application.

Claims

1. A software testing requirements analysis method based on XML configuration files, characterized in that: The software testing requirements analysis method based on XML configuration file includes: Traverse the test process folder to determine whether there is an XML file in the test process folder; If it is determined that the XML file exists in the test process folder, then obtaining the storage path structure information of the XML file and the element information of the XML file; Writing an XML file parsing tool according to the element information of the XML file; The XML file is subjected to a test requirement analysis based on the XML file parsing tool and the storage path structure information of the XML file to extract the data in the XML file, and the extracted data is written into a preset Excel template according to preset rules to generate an Excel file.

2. The software testing requirements analysis method based on XML configuration files as claimed in claim 1, characterized in that: The step of writing an XML file parsing tool according to the element information of the XML file comprises: Retrieve the preset Python language writing tool; An XML file parsing tool is written based on the element information of the XML file through the preset Python language writing tool, wherein the element information of the XML file includes tags and attributes.

3. The software testing requirements analysis method based on XML configuration files as claimed in claim 2, characterized in that: The tags include ProcessCluster, ProcessItem, ProcessModule, and ProcessPoint.

4. The software testing requirements analysis method based on XML configuration files as claimed in claim 2, characterized in that: The attributes include actionCMD, check, and get.

5. The software testing requirements analysis method based on XML configuration files as claimed in claim 1, characterized in that: The performing test requirement analysis on the XML file according to the XML file parsing tool and the storage path structure information of the XML file to extract data in the XML file includes: Traverse the test process folder through the storage path structure information of the XML file to determine the XML file that needs to be parsed; The XML file is subjected to a test requirement analysis by the XML file parsing tool to extract data in the XML file, wherein the data is data corresponding to the element information.

6. The software testing requirements analysis method based on XML configuration files as claimed in claim 1, characterized in that: Writing the extracted data into a preset Excel template according to preset rules to generate an Excel file includes: Grouping the acquired data, wherein the data includes data extracted from each of the XML files; Write each group of data into a preset Excel template in sequence to generate an Excel file.

7. The software testing requirements analysis method based on XML configuration files as claimed in claim 1, characterized in that: The traversing the test process folder to determine whether there is an XML file in the test process folder includes: Traverse the test process folder to determine whether there is an XML file in the test process folder; If it is determined that there is no XML file in the test process folder, each subfolder in the test process folder is traversed to determine whether there is an XML file in each subfolder of the test process folder.

8. A software testing requirements analysis device based on XML configuration files, characterized in that: The software testing requirements analysis device based on XML configuration file includes: A determination module is used to traverse the test process folder to determine whether there is an XML file in the test process folder; An acquisition module, configured to acquire storage path structure information of the XML file and element information of the XML file if it is determined that the XML file exists in the test process folder; A writing module, used for writing an XML file parsing tool according to the element information of the XML file; The extraction and writing module is used to perform test demand analysis on the XML file according to the XML file parsing tool and the storage path structure information of the XML file to extract the data in the XML file, and write the extracted data into a preset Excel template according to preset rules to generate an Excel file.

9. A software testing requirements analysis device based on XML configuration files, characterized in that: The software testing requirement analysis device based on XML configuration file includes a processor, a memory, and a software testing requirement analysis program based on XML configuration file stored in the memory and executable by the processor, wherein when the software testing requirement analysis program based on XML configuration file is executed by the processor, the steps of the software testing requirement analysis method based on XML configuration file as described in any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a software testing requirement analysis program based on an XML configuration file, wherein when the software testing requirement analysis program based on an XML configuration file is executed by a processor, the steps of the software testing requirement analysis method based on an XML configuration file as described in any one of claims 1 to 7 are implemented.

Images