A method and device for converting test case file data

Abstract

The present invention discloses a method and device for converting test case file data, and relates to the field of computer technology. A specific implementation of the method includes: obtaining file data of a test case in XMind format; the file data is composed of nodes, and the file data contains element identification information; parsing the file data to determine the node data of each node in the file data; the node data includes node content and / or element dimension; determining the parsed data of the sub-test case in the file data according to the node data, and integrating and storing the parsed data of the sub-test case in a relational data table to generate the relational file data of the test case. This implementation can parse the XMind file containing element identification information, and then determine the element information in the XMind format test case, and store the unstructured text type test case in a structured relational data table, so that it is easy to manage.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a method and device for converting test case file data. Background Art

[0002] XMind is a mind-mapping application that is often used by testers when writing test cases. However, when the test department manages a large number of test cases, it often uses structured database tables (such as MySQL) to manage them. Therefore, it is necessary to convert the XMind format files that describe the test cases to make them easier to manage. Currently, it supports referencing the API in the XMind core jar package (such as org.xmind.core) to parse XMind files.

[0003] In the process of implementing the present invention, the inventors found that there are at least the following problems in the prior art:

[0004] When testers use XMind to write test cases, they often only enter text information describing the test cases or the test case requirements at each node. Therefore, after parsing the XMind file, it is impossible to determine the element dimension information of the test case (such as title, premise, steps, expected results, level, etc.), resulting in the inability to store the parsed data in a structured relational data table, which is not conducive to the management of test cases. Summary of the invention

[0005] In view of this, an embodiment of the present invention provides a method and device for converting test case file data. By setting a correspondence table between element identifiers and element dimensions, and combining a parsing tool to parse an XMind file containing element identifier information, the element information in the XMind format test case can be determined, and the unstructured text type test case can be stored in a structured relational data table to make it easy to manage.

[0006] To achieve the above object, according to one aspect of an embodiment of the present invention, a method for converting test case file data is provided, comprising:

[0007] Obtaining file data of the test case in XMind format; wherein the file data is composed of nodes, and the file data contains element identification information;

[0008] Parsing the file data to determine node data of each node in the file data; wherein the node data includes: node content and / or element dimension;

[0009] The parsed data of the sub-test cases in the file data are determined according to the node data, and the parsed data of the sub-test cases are integrated and stored in a relational data table to generate relational file data of the test case.

[0010] Optionally, the element identifier is an icon provided in the XMind application;

[0011] The parsing of the file data includes:

[0012] Based on the correspondence table between element identifiers and element dimensions, the file data is parsed according to the element identifiers of the test case elements contained in the nodes in the file data in combination with a parsing tool for parsing XMind format data.

[0013] Optionally, the structure of the file data is a tree structure consisting of nodes;

[0014] The determining, according to the node data, the parsed data of the sub-test case in the file data comprises:

[0015] Performing a depth-first traversal of the tree structure from the root node to the leaf nodes, and taking each path from the root node to the leaf node as a sub-test case;

[0016] The node data of all nodes in the sub-test case are used as the parsed data of the sub-test case.

[0017] Optionally, the step of integrating and storing the parsed data of the sub-test cases into a relational data table includes:

[0018] splicing the node contents of the nodes with the same element dimension in the parsed data of the sub-test case to serve as the test case content corresponding to the element dimension;

[0019] Each element dimension of the sub-test case and the corresponding test case content are stored in a relational data table.

[0020] Optionally, when the node data of the node in the sub-test case does not include an element dimension, the element dimension of the parent node of the node is used as the element dimension of the node;

[0021] When the node data of the node in the sub-test case does not include node content, empty data is used as the node content of the node.

[0022] Optionally, the element dimensions include at least one of the following: project name, module name, use case title, use case premise, use case input, use case steps, use case expected results, and use case importance level.

[0023] According to another aspect of an embodiment of the present invention, there is provided a device for converting test case file data, comprising:

[0024] An acquisition module, used to acquire file data of a test case in an XMind format; wherein the file data is composed of nodes, and the file data contains element identification information;

[0025] A parsing module, used to parse the file data and determine the node data of each node in the file data; wherein the node data includes: node content and / or element dimension;

[0026] A storage module is used to determine the parsed data of the sub-test case in the file data according to the node data, and integrate and store the parsed data of the sub-test case into a relational data table to generate relational file data of the test case.

[0027] Optionally, the element identifier is an icon provided in the XMind application;

[0028] The parsing module parses the file data, including:

[0029] Based on the correspondence table between element identifiers and element dimensions, the file data is parsed according to the element identifiers of the test case elements contained in the nodes in the file data in combination with a parsing tool for parsing XMind format data.

[0030] Optionally, the structure of the file data is a tree structure consisting of nodes;

[0031] The parsing module determines the parsing data of the sub-test case in the file data according to the node data, including:

[0032] Performing a depth-first traversal of the tree structure from the root node to the leaf nodes, and taking each path from the root node to the leaf node as a sub-test case;

[0033] The node data of all nodes in the sub-test case are used as the parsed data of the sub-test case.

[0034] Optionally, the storage module integrates and stores the parsed data of the sub-test cases into a relational data table, including:

[0035] splicing the node contents of the nodes with the same element dimension in the parsed data of the sub-test case to serve as the test case content corresponding to the element dimension;

[0036] Each element dimension of the sub-test case and the corresponding test case content are stored in a relational data table.

[0037] Optionally, when the node data of the node in the sub-test case does not include an element dimension, the element dimension of the parent node of the node is used as the element dimension of the node;

[0038] When the node data of the node in the sub-test case does not include node content, empty data is used as the node content of the node.

[0039] Optionally, the element dimensions include at least one of the following: project name, module name, use case title, use case premise, use case input, use case steps, use case expected results, and use case importance level.

[0040] According to another aspect of an embodiment of the present invention, there is provided an electronic device for converting test case file data, comprising:

[0041] one or more processors;

[0042] a storage device for storing one or more programs,

[0043] When the one or more programs are executed by the one or more processors, the one or more processors implement the test case file data conversion method provided by the present invention.

[0044] According to another aspect of an embodiment of the present invention, a computer-readable medium is provided, on which a computer program is stored. When the program is executed by a processor, the method for converting test case file data provided by the present invention is implemented.

[0045] An embodiment of the above invention has the following advantages or beneficial effects: because the technical means of setting the correspondence between element identification and element dimension is adopted, and the XMind file containing element identification information is parsed and stored in a relational data table in combination with a parsing tool, the technical problem in the prior art that the element dimension information of the test case cannot be determined after parsing the XMind file and cannot be stored in a structured relational data table is overcome, thereby achieving the technical effect of being able to convert data of unstructured text type test cases so that they can be stored in a structured relational data table, which is beneficial to the management of test cases.

[0046] The further effects of the above-mentioned non-conventional optional manner will be described below in conjunction with the specific implementation manner. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] The accompanying drawings are used to better understand the present invention and do not constitute an improper limitation of the present invention.

[0048] Figure 1 is a schematic diagram of the main process of a method for converting test case file data according to a first embodiment of the present invention;

[0049] Figure 2 is a schematic diagram of icons provided in an XMind application used in a test case file data conversion method according to a second embodiment of the present invention;

[0050] Figure 3 is a schematic diagram of an XMind file to be converted in a method for converting test case file data according to a third embodiment of the present invention;

[0051] Figure 4 It is a schematic diagram of parsing the XMind file to be converted and integrating and storing it in a relational data table in a test case file data conversion method according to the third embodiment of the present invention;

[0052] Figure 5 is a schematic diagram of an XMind file to be converted in a method for converting test case file data according to a fourth embodiment of the present invention;

[0053] Figure 6 is a schematic diagram of main modules of a test case file data conversion device according to a fifth embodiment of the present invention;

[0054] Figure 7 is an exemplary system architecture diagram to which embodiments of the present invention may be applied;

[0055] Figure 8 It is a schematic diagram of the structure of a computer system of a terminal device or a server suitable for implementing an embodiment of the present invention. DETAILED DESCRIPTION

[0056] The following is a description of exemplary embodiments of the present invention in conjunction with the accompanying drawings, including various details of the embodiments of the present invention to facilitate understanding, which should be considered as merely exemplary. Therefore, it should be recognized by those of ordinary skill in the art that various changes and modifications may be made to the embodiments described herein without departing from the scope and spirit of the present invention. Similarly, for clarity and conciseness, the description of well-known functions and structures is omitted in the following description.

[0057] Figure 1 FIG. 1 is a schematic diagram of the main process of a method for converting test case file data according to a first embodiment of the present invention. Figure 1 As shown, including:

[0058] Step S101, obtaining file data of a test case in an XMind format; wherein the file data is composed of nodes, and the file data contains element identification information;

[0059] Step S102: parsing the file data to determine node data of each node in the file data; wherein the node data includes: node content and / or element dimension;

[0060] Step S103: determining the parsed data of the sub-test cases in the file data according to the node data, and integrating and storing the parsed data of the sub-test cases in a relational data table to generate relational file data of the test cases.

[0061] According to the method of the present invention, the XMind file containing element identification information can be parsed, and the element information in the XMind format test case can be determined, and the unstructured text type test case can be stored in a structured relational data table to make it easy to manage.

[0062] In some embodiments, the element identifier can be an icon provided in the XMind application; parsing the file data includes: based on a correspondence table between element identifiers and element dimensions, according to the element identifiers of the test case elements contained in the nodes in the file data, combining a parsing tool for parsing XMind format data to parse the file data.

[0063] Furthermore, the element dimensions may include at least one of the following: project name, module name, use case title, use case premise, use case input, use case steps, use case expected results, and use case importance level.

[0064] Figure 2 is a schematic diagram of icons provided in an XMind application used in a test case file data conversion method according to a second embodiment of the present invention, such as Figure 2 As shown, the icons provided in the XMind application can be used as the element identifiers.

[0065] You can set the correspondence table between element identifiers and element dimensions according to actual needs. For example, you can use Figure 2 The number icons 1, 2, 3, and 4 selected under "Task Priority" respectively identify the four element dimensions of the test case: title, premise, step, and expected result. You can also use Figure 2 The flags of different colors selected under "Flag" mark the high, medium and low levels of the use case.

[0066] When parsing XMind file data, you can reference the API in the XMind core jar package to parse, such as: combining the parsing tool org.xmind.core to parse the XMind file.

[0067] In some embodiments, the structure of the file data is a tree structure consisting of nodes;

[0068] The method of determining the parsing data of the sub-test case in the file data based on the node data includes: performing a depth-first traversal on the tree structure from the root node to the leaf nodes, and taking each path from the root node to the leaf node as a sub-test case; and taking the node data of all nodes in the sub-test case as the parsing data of the sub-test case.

[0069] In some embodiments, the integration and storage of the parsed data of the sub-test cases into a relational data table includes: concatenating the node contents of the nodes with the same element dimensions in the parsed data of the sub-test cases to serve as the test case contents corresponding to the element dimensions; and storing each element dimension of the sub-test cases and the corresponding test case contents into a relational data table.

[0070] In some embodiments, when the node data of a node in the sub-test case does not include an element dimension, the element dimension of the parent node of the node is used as the element dimension of the node; when the node data of a node in the sub-test case does not include node content, empty data is used as the node content of the node.

[0071] To facilitate understanding of the above embodiments, Figure 3 For example, Figure 3 is a schematic diagram of an XMind file to be converted in a method for converting test case file data according to a third embodiment of the present invention; Figure 4 It is a schematic diagram of parsing an XMind file to be converted and integrating and storing it in a relational data table in a test case file data conversion method according to the third embodiment of the present invention.

[0072] Figure 3 The test case shown in can be seen as having two sub-test cases, using Figure 2 The correspondence table between the element identifier and the element dimension set in Figure 3 The element dimensions of the two sub-test cases in and the corresponding test case contents are stored in the relational data table, such as Figure 4 shown.

[0073] In some practical applications, a recognizable text type identifier may also be used as the element identifier, such as: "[Prerequisite]" or "*Prerequisite*" may be set to correspond to the use case premise element dimension; Figure 5 As shown, Figure 5 It is a schematic diagram of an XMind file to be converted in a test case file data conversion method according to the fourth embodiment of the present invention.

[0074] Figure 6 is a schematic diagram of main modules of a test case file data conversion device according to a fifth embodiment of the present invention, such as Figure 5 As shown, the test case file data conversion device 500 includes:

[0075] The acquisition module 601 is used to acquire the file data of the test case in the XMind format; wherein the file data is composed of nodes, and the file data contains element identification information;

[0076] The parsing module 602 is used to parse the file data to determine the node data of each node in the file data; wherein the node data includes: node content and / or element dimension;

[0077] The storage module 603 is used to determine the parsed data of the sub-test cases in the file data according to the node data, and integrate and store the parsed data of the sub-test cases into a relational data table to generate relational file data of the test cases.

[0078] According to the device of the present invention, it is possible to parse the XMind file containing element identification information, thereby determining the element information in the XMind format test case, and store the unstructured text type test case in a structured relational data table to make it easy to manage.

[0079] In some embodiments, the element identifier is an icon provided in the XMind application;

[0080] The parsing module 602 parses the file data, including:

[0081] Based on the correspondence table between element identifiers and element dimensions, the file data is parsed according to the element identifiers of the test case elements contained in the nodes in the file data in combination with a parsing tool for parsing XMind format data.

[0082] You can set the correspondence table between element identifiers and element dimensions according to actual needs. For example, you can use the icons provided in the XMind application, such as Figure 2 The number icons 1, 2, 3, and 4 selected under "Task Priority" respectively identify the four element dimensions of the test case: title, premise, step, and expected result. You can also use Figure 2 The flags of different colors selected under "Flag" mark the high, medium and low levels of the use case.

[0083] In some practical applications, a recognizable text type identifier may also be used as the element identifier, such as setting "

Prerequisite

[0084] When parsing XMind file data, you can reference the API in the XMind core jar package to parse, such as: combining the parsing tool org.xmind.core to parse the XMind file.

[0085] In some embodiments, the structure of the file data is a tree structure consisting of nodes;

[0086] The parsing module 602 determines the parsing data of the sub-test case in the file data based on the node data, including: performing a depth-first traversal of the tree structure from the root node to the leaf node, and taking each path from the root node to the leaf node as a sub-test case; and taking the node data of all nodes in the sub-test case as the parsing data of the sub-test case.

[0087] In some embodiments, the storage module 603 integrates and stores the parsed data of the sub-test cases into a relational data table, including: concatenating the node contents of the nodes with the same element dimensions in the parsed data of the sub-test cases to serve as the test case contents corresponding to the element dimensions; and storing each element dimension of the sub-test case and the corresponding test case contents in the relational data table.

[0088] In some embodiments, when the node data of a node in the sub-test case does not include an element dimension, the element dimension of the parent node of the node is used as the element dimension of the node; when the node data of a node in the sub-test case does not include node content, empty data is used as the node content of the node.

[0089] In some embodiments, the element dimensions include at least one of the following: project name, module name, use case title, use case premise, use case input, use case steps, use case expected results, and use case importance level.

[0090] Figure 7 An exemplary system architecture 700 of a test case file data conversion device to which an embodiment of the present invention can be applied is shown.

[0091] like Figure 7 As shown, system architecture 700 may include terminal devices 701, 702, 703, network 704 and server 705. Network 704 is used to provide a medium for communication links between terminal devices 701, 702, 703 and server 705. Network 704 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0092] Users can use terminal devices 701, 702, 703 to interact with server 705 through network 704 to receive or send messages, etc. Various communication client applications, such as web browser applications, instant messaging tools, etc., can be installed on terminal devices 701, 702, 703.

[0093] The terminal devices 701 , 702 , and 703 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, and desktop computers.

[0094] Server 705 may be a server that provides various services, such as a background management server that provides support for websites browsed by users using terminal devices 701, 702, and 703. The background management server may analyze and process received data such as product information query requests, and feed back the processing results to the terminal device.

[0095] It should be noted that the test case file data conversion method provided in the embodiment of the present invention is generally executed by the server 705 , and accordingly, the test case file data conversion device is generally disposed in the server 705 .

[0096] It should be understood that Figure 7 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.

[0097] Reference below Figure 8 , which shows a schematic diagram of the structure of a computer system 800 of a terminal device suitable for implementing an embodiment of the present invention. Figure 8 The terminal device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0098] like Figure 8 As shown, the computer system 800 includes a central processing unit (CPU) 801, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 802 or a program loaded from a storage part 808 into a random access memory (RAM) 803. In the RAM 803, various programs and data required for the operation of the system 800 are also stored. The CPU 801, the ROM 802, and the RAM 803 are connected to each other via a bus 804. An input / output (I / O) interface 805 is also connected to the bus 804.

[0099] The following components are connected to the I / O interface 805: an input section 806 including a keyboard, a mouse, etc.; an output section 807 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 808 including a hard disk, etc.; and a communication section 809 including a network interface card such as a LAN card, a modem, etc. The communication section 809 performs communication processing via a network such as the Internet. A drive 810 is also connected to the I / O interface 805 as needed. A removable medium 811, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 810 as needed, so that a computer program read therefrom is installed into the storage section 808 as needed.

[0100] In particular, according to the embodiments disclosed in the present invention, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present invention include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 809, and / or installed from the removable medium 811. When the computer program is executed by the central processing unit (CPU) 801, the above-mentioned functions defined in the system of the present invention are executed.

[0101] It should be noted that the computer-readable medium shown in the present invention may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present invention, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In the present invention, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

[0102] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present invention. In this regard, each box in the flow chart or block diagram can represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0103] The modules involved in the embodiments of the present invention may be implemented by software or hardware. The modules described may also be set in a processor, for example, it may be described as: a processor includes an acquisition module, a parsing module, and a storage module. The names of these modules do not, in some cases, constitute limitations on the modules themselves.

[0104] As another aspect, the present invention also provides a computer-readable medium, which may be included in the device described in the above embodiment; or it may exist independently without being assembled into the device. The above computer-readable medium carries one or more programs, and when the above one or more programs are executed by a device, the device includes: step S101, obtaining the file data of the test case in XMind format; wherein the file data is composed of nodes, and the file data contains element identification information; step S102, parsing the file data to determine the node data of each node in the file data; wherein the node data includes: node content and / or element dimension; step S103, determining the parsed data of the sub-test case in the file data according to the node data, and integrating and storing the parsed data of the sub-test case into a relational data table to generate the relational file data of the test case.

[0105] According to the technical solution of the embodiment of the present invention, because the corresponding relationship between element identification and element dimension is set, and the XMind file containing element identification information is parsed and stored in a relational data table in combination with a parsing tool, the technical problem in the prior art that the element dimension information of the test case cannot be determined after parsing the XMind file and cannot be stored in a structured relational data table is overcome, thereby achieving the technical effect of being able to convert data of unstructured text type test cases so that they can be stored in a structured relational data table, which is beneficial to the management of test cases.

[0106] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may occur depending on design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A method for converting test case file data, characterized in that: include: Obtaining file data of the test case in XMind format; wherein the file data is composed of nodes, and the file data contains element identification information; the element identification is an icon provided in the XMind application; Parsing the file data to determine the node data of each node in the file data; wherein the node data includes: node content and / or element dimension; parsing the file data includes: based on a correspondence table between element identifiers and element dimensions, parsing the file data according to the element identifiers of the test case elements contained in the nodes in the file data in combination with a parsing tool for parsing XMind format data; The parsed data of the sub-test cases in the file data are determined according to the node data, and the parsed data of the sub-test cases are integrated and stored in a relational data table to generate relational file data of the test case.

2. The method according to claim 1, characterized in that The structure of the file data is a tree structure consisting of nodes; The determining, according to the node data, the parsed data of the sub-test case in the file data comprises: Performing a depth-first traversal of the tree structure from the root node to the leaf nodes, and taking each path from the root node to the leaf node as a sub-test case; The node data of all nodes in the sub-test case are used as the parsed data of the sub-test case.

3. The method according to claim 2, characterized in that The step of integrating and storing the parsed data of the sub-test cases into a relational data table includes: splicing the node contents of the nodes with the same element dimension in the parsed data of the sub-test case to serve as the test case content corresponding to the element dimension; Each element dimension of the sub-test case and the corresponding test case content are stored in a relational data table.

4. The method according to claim 3, characterized in that Also includes: When the node data of the node in the sub-test case does not include an element dimension, the element dimension of the parent node of the node is used as the element dimension of the node; When the node data of the node in the sub-test case does not include node content, empty data is used as the node content of the node.

5. The method according to claim 1, characterized in that The element dimensions include at least one of the following: project name, module name, use case title, use case premise, use case input, use case steps, use case expected results, and use case importance level.

6. A test case file data conversion device, characterized in that: include: An acquisition module, used to acquire file data of a test case in an XMind format; wherein the file data is composed of nodes, and the file data contains element identification information; A parsing module, used to parse the file data and determine the node data of each node in the file data; wherein the node data includes: node content and element dimension, or node content; A storage module is used to determine the parsed data of the sub-test case in the file data according to the node data, and integrate and store the parsed data of the sub-test case into a relational data table to generate relational file data of the test case.

7. An electronic device for converting test case file data, characterized in that: include: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 5.

8. A computer readable medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 1 to 5 is implemented.

Images