CN109740122B - Method and device for converting thinking guide graph use case file - Google Patents
Method and device for converting thinking guide graph use case file Download PDFInfo
- Publication number
- CN109740122B CN109740122B CN201811513165.3A CN201811513165A CN109740122B CN 109740122 B CN109740122 B CN 109740122B CN 201811513165 A CN201811513165 A CN 201811513165A CN 109740122 B CN109740122 B CN 109740122B
- Authority
- CN
- China
- Prior art keywords
- use case
- file
- case
- text
- node
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 47
- 238000012360 testing method Methods 0.000 claims abstract description 37
- 238000010586 diagram Methods 0.000 claims abstract description 16
- 230000015654 memory Effects 0.000 claims description 19
- 238000012545 processing Methods 0.000 claims description 16
- 238000006243 chemical reaction Methods 0.000 claims description 8
- 238000004590 computer program Methods 0.000 claims description 7
- 238000005516 engineering process Methods 0.000 abstract description 3
- 230000006870 function Effects 0.000 description 22
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000012423 maintenance Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000006399 behavior Effects 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 239000007787 solid Substances 0.000 description 2
- 238000006467 substitution reaction Methods 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000000802 evaporation-induced self-assembly Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000009191 jumping Effects 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000013515 script Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Classifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The application discloses a method and a device for converting a mind map case file, which relate to the computer technology and are used for converting the mind map case file into an excel test case convenient for team management. Comprising the following steps: acquiring a thinking guide diagram use case file; traversing the father node and the child nodes corresponding to the father node to obtain a plurality of text values, and storing the text values into a dynamic array Arraylist; acquiring a configuration file of a standard use case template file, wherein the configuration file comprises a plurality of use case names; analyzing Arraylist to obtain a plurality of text values corresponding to a plurality of use case names; and determining a standard table file according to the plurality of case names and the text values corresponding to the plurality of case names. The embodiment of the application is applied to converting the thinking guide diagram case file into the standard excel test case.
Description
Technical Field
The application relates to the technical field of computers, in particular to a method and a device for converting a thinking guide diagram case file.
Background
The test case refers to the description of a specific software product for testing tasks, and the test scheme, the method, the technology and the strategy are embodied. The test contents include test targets, test environments, input data, test steps, expected results, test scripts, and the like, and form a document. And the document format standard is the basis for achieving information resource efficacy and open document format. Although the document format is gradually opened, the office document industry still exists in a plurality of standards.
At present, most of the test cases are written through a mind map, and then an excel test case is manually written again after the test is finished to serve as a standard test case template so as to maintain the test cases. excel test cases are suitable for team maintenance and reading by others, but the writing process is poor in logic and long in time consumption. The writing process of the case files of the mind map has stronger logic and simpler writing, but the writing tools of the mind map are numerous, have no unified writing specification and are inconvenient for team maintenance.
Disclosure of Invention
The embodiment of the application provides a method and a device for converting a test case file, which are used for converting a mind map case file into an excel test case convenient for team management.
In order to achieve the above purpose, the embodiment of the present application adopts the following technical scheme:
in a first aspect, a method for converting a case file of a mind map is provided, the method comprising: the method comprises the steps of obtaining a mind map use case file, wherein the mind map use case file comprises a plurality of nodes, each node comprises a root node, a father node and at least one child node corresponding to the father node, each node stores a text value, and the text value stored by the root node is used for representing the task name of the mind map use case file; the text value stored by the father node is used for representing the task name and/or the module name for executing the task; the text value stored by the child node corresponding to the father node is used for representing the test operation executable by the task and/or the module and the expected operation result; traversing the father node and the plurality of child nodes corresponding to the father node to obtain the plurality of text values, and storing the plurality of text values into a dynamic array Arraylist, wherein the Arraylist comprises a plurality of text values; acquiring a configuration file of a standard use case template file, wherein the configuration file comprises a plurality of use case names; analyzing the Arraylist to obtain a plurality of text values corresponding to the plurality of use case names; and determining a standard table file according to the plurality of case names and the text values corresponding to the plurality of case names.
In a second aspect, a device for converting a case file of a mind act chart is provided, where the device includes an acquisition unit, a processing unit, and a determination unit.
The acquiring unit is configured to acquire the mind map use case file, where the mind map use case file includes a plurality of nodes, the plurality of nodes include a root node, a parent node, and at least one child node corresponding to the parent node, each node stores a text value, and the text value stored in the root node is used to represent a task name of the mind map use case file; the text value stored by the father node is used for representing the task name and/or the module name for executing the task; the text value stored by the child node corresponding to the parent node is used for representing the test operation executable by the task and/or the module and the expected operation result.
The processing unit is configured to traverse the parent node and the plurality of child nodes corresponding to the parent node to obtain the plurality of text values, and store the plurality of text values into a dynamic array Arraylist, where the Arraylist includes a plurality of text values.
The obtaining unit is further configured to obtain a configuration file of the standard use case template file, where the configuration file includes a plurality of use case names.
The processing unit is further configured to parse the Arraylist to obtain a plurality of text values corresponding to the plurality of use case names.
The determining unit is used for determining a standard table file according to the plurality of case names and text values corresponding to the plurality of case names.
In a third aspect, there is provided a computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by a computer, cause the computer to perform the method of converting a mind map use case file according to the first aspect.
In a fourth aspect, a computer program product is provided comprising instructions which, when run on a computer, cause the computer to perform the method of converting a mind map case file according to the first aspect.
In a fifth aspect, there is provided a device for converting a case document of a mind act, comprising: the computer comprises a processor and a memory, wherein the memory is used for storing programs, and the processor calls the programs stored in the memory to execute the conversion method of the mind map use case file according to the first aspect.
According to the method and the device for converting the thinking guide image case file, the configuration items of the fixed test case are extracted according to the configuration files in the standard case template file, the thinking guide image case file is analyzed according to the preset specification, and the analyzed result is generated into an excel file according to the configuration items of the standard case template and stored in the file, so that the thinking guide image case can be automatically converted into the excel file, and the time for manually writing the excel case again is shortened.
Drawings
FIG. 1 is a schematic diagram of a case file for a mind act according to an embodiment of the present application;
FIG. 2 is a schematic diagram showing a process of converting a scenario file of a mind map according to an embodiment of the present application;
FIG. 3 is a schematic diagram showing a second example file conversion process for a mind map according to an embodiment of the present application;
FIG. 4 is a schematic diagram III of a process for converting a case file of a mind map according to an embodiment of the present application;
FIG. 5 is a schematic diagram showing a process of converting a case file for a mind map according to an embodiment of the present application;
FIG. 6 is a schematic flow chart of a method for converting a case file of a mind map according to an embodiment of the present application;
FIG. 7 is a schematic diagram of the content of an example document for a mind act;
FIG. 8 is a second flow chart of the example file conversion of the mind map according to the embodiment of the present application;
FIG. 9 is a schematic diagram of an apparatus for converting a case file for a mind map according to an embodiment of the present application;
fig. 10 is a schematic diagram of a device for converting a case file for a mind map according to an embodiment of the present application.
Detailed Description
Some concepts related to the embodiments of the present application will be briefly described below.
(1) Use case
Use case, or use case, is a description of how the system reacts to external requests in software engineering or system engineering, and is a technology for obtaining demands through the use scenario of users. Each use case provides one or more scenarios that describe how the system interacts with the end user or other system, i.e., who can do what with the system, to achieve an explicit business goal. The use of technical terms in writing the use cases should be avoided and the language of the end user or the domain expert should be used. Use cases are typically co-authored by software developers and end users.
(2) The mind map file, which may also be referred to as a mind map use case, may be drawn by an xmind tool. Mind map is an idea that uses one central keyword or idea to induce visualized construction and classification; the relationship of each level of topics is represented by a hierarchy of mutual membership and correlation by a central keyword or idea connecting all the representative words, ideas, tasks or other associated items in a radial line.
(3) ArrayList is a class based on dynamic array implementation, and has excellent functions for random access and setting.
(4) Linkedlist is a class based on linked list implementation, and has excellent functions for new add and delete operations.
The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings in the embodiments of the present application.
In the description of the present application, "/" means "or" unless otherwise indicated, for example, A/B may mean A or B. "and/or" herein is merely an association relationship describing an association object, and means that three relationships may exist, for example, a and/or B may mean: a exists alone, A and B exist together, and B exists alone.
The technical scheme provided by the embodiment of the application can be applied to the field of electronic payment and the like.
The method for converting the thinking guide graph case file provided by the embodiment of the application comprises the following steps: the method comprises the steps of making a rule for writing the mind map use case file, writing the mind map use case file according to the rule, and converting the written mind map use case file into a standard table use case file.
The writing rule of the thinking guide graph case file can be as follows: for the use cases of the modules and the tasks to be configured, M=module names and T=task names are used in the father node; test names and operation expected results of the split cases, etc. are used in the child nodes.
Specifically, referring to fig. 1, a case file of a mind map written according to the above rule is provided in an embodiment of the present application, and in fig. 1, a root node includes two text segments: logging in and registering; the text segment of the parent node is: t=task-1021, m=login, or t=task-1022, m=registration; the text segment of the first child node includes: opening a login page, clicking a registration button on the login page, and jumping to the registration page; the text segment in the second sub-node corresponding to the "open login page" in the first sub-node includes:
1. looking at the page information, looking at whether the landing page interface presentation is normal= = presentation: the login and registration buttons are displayed under the normal input boxes of the user name and password input boxes.
2. Inputting the correct user name and password in a user name and password input box, clicking a login button, and checking whether the user login function is normal: normal login using the correct username password is possible= = =successful login jump to the home page normal.
3. Inputting wrong user names and passwords in a user name and password input box, clicking a login button, and checking whether the user login function is normal or not: user name and password errors are prompted by using wrong user name password login failure= = login failure.
The second sub-node corresponding to the 'click on the registration button to jump to the registration page on the registration page' in the first sub-node comprises:
1. viewing page presentation, viewing registration page presentation normal= = = presenting all information filling boxes correct.
2. The registration information is filled out completely and completely according with rules, a decision button is clicked, and whether the registration function is normal or not is checked: entering the correct registration information enables registration success= registration success.
3. Registration information fills out non-compliance rules, clicks the ok button, checks if the registration function is normal: input wrong registration information registration failure= registration failure, prompt failure information.
The module names of the use cases are login and registration, and the task names of the use cases are task-1021 and task-1022; the test names of the use cases include: checking whether the login page interface display is normal, using the correct user name password to log in normally, using the wrong user name password to log in failed, checking the page display, checking the registration page display to be normal, inputting the correct registration information to register successfully, and inputting the wrong registration information to register failed.
The expected results include: and (3) displaying: displaying a login button and a registration button below a normal input box of the user name and password input box; the login can successfully jump to the normal home page; the login fails, and the user name and the password are prompted to be wrong; displaying that all information filling frames are correct; the registration is successful; and prompting failure information when registration fails.
Optionally, the embodiment of the present application provides a specific process for converting a case file of a mind map displayed through a visual interface, where the process may include S1-S4:
s1, opening an initial page.
As shown in fig. 2, an initial page displayed on the display interface, where the page includes a selection file for selecting a converted mind map use case file, may further include: the module to which the use case belongs, the version to which the use case belongs, the label to which the use case belongs and the use case tracking user.
S2, clicking the selected file to select the thinking guide picture example file.
As shown in fig. 3, a page of the selected mind map use case file is displayed on the display.
S3, selecting the use case file.
As shown in fig. 4, is a selected page displayed on the display interface.
S4, selecting an excel file storage position.
Before converting the mind guide file into a standard form case file, the storage location of the obtained annotation form case file needs to be determined. As shown in FIG. 5, a page is displayed on the display that selects the standard form file storage location.
S5, converting the selected thinking guide diagram case file into a standard table case file.
Specifically, referring to fig. 6, a method for converting a case file of a mind map into a case file of a standard table according to an embodiment of the present application may include S101-S105:
s101, acquiring a thinking guide diagram case file.
The system comprises a thinking drawing case file, a computer system and a computer system, wherein the thinking drawing case file comprises a plurality of nodes, the nodes comprise a root node, a father node and at least one child node corresponding to the father node, each node stores a text value, and the text value stored by the root node is used for representing the task name of the thinking drawing case file; the text value stored by the father node is used for representing the task name and/or the module name for executing the task; the text values stored by the child nodes corresponding to the parent nodes are used to represent test operations and expected operation results that can be performed by the tasks and/or modules.
It should be noted that the mind map use case files can be recursively decompressed to the local folder by using the ZipEntry and ZipInputStream classes under the java. Utel. Zip package.
It should be noted that java. Uteil. Zip is a toolkit in java, and the toolkit includes a ZipEntry class and a ZipINPutStream class.
Exemplary, fig. 1 is a schematic diagram of a case file of a mind map, where a root node is login & registration, and a first parent node is: task identity t=task-1021, module identity m=login; the second father node is: task identity t=task-1022, module identity m=registration; the first child node corresponding to the first father node is a test operation of opening a login page and checking page information to check whether the login page interface display is normal, and an expected operation result corresponding to the test operation is a display: the login button is normally displayed below the normal input box of the user name and password input box, and other node descriptions are similar to those described above and are not listed here.
S102, traversing the father node and a plurality of child nodes corresponding to the father node to obtain a plurality of text values, and storing the text values into a dynamic array Arraylist.
Wherein the Arraylist includes a plurality of text values.
The mind map file includes a content file in an extensible markup language (Extensible Markup Language, xml) format, as shown in fig. 7, which is a content xml file in the mind map file of fig. 1, the content xml file including a series of letter codes and text values, wherein title represents a title, topic represents a body, topics type represents a body type, topics id represents a body identification, child represents a child node.
And traversing the corresponding child nodes from the parent node to obtain a plurality of groups of related text values, wherein each group of text values is a use case, and the plurality of use cases obtained by traversing can be stored in an Arraylist so as to facilitate inquiry.
Illustratively, traversing content. Xml of the mind map use case file as in FIG. 7 may result in the following use cases:
1. t=task-1021, m=login, open login page, view page information, see if login page interface presentation is normal= = presentation: the login and registration buttons are displayed under the normal input boxes of the user name and password input boxes.
2. T=task-1021, m=login, open login page, enter correct user name and password in user name and password input box, click login button, see if user login function is normal: normal login using the correct username password is possible= = =successful login jump to the home page normal.
3. T=task-1021, m=login, open login page, input wrong user name and password in user name and password input box, click login button, see if user login function is normal: user name and password errors are prompted by using wrong user name password login failure= = login failure.
4. T=task-1022, m=registered, clicking the registration button on the login page jumps to the registration page, and viewing the page display, viewing the registration page display normal= =displaying the full information filling box correctly.
5. T=task-1022, m=register, click the register button to jump to the register page on the login page, register information fills out completely and all in accordance with rules, click the confirm button, see if the register function is normal: entering the correct registration information enables registration success= registration success.
6. T=task-1022, m=register, click the register button to jump to the register page on the login page, register information fills out non-conforming rules, click the confirm button, see if the register function is normal: input wrong registration information registration failure= registration failure, prompt failure information.
Alternatively, referring to fig. 8, one implementation of storing the plurality of text values obtained in S102 to an arraisist may include S201-S202:
s201, storing a plurality of text values into a plurality of linked lists LinkedList.
Each LinkedList comprises a use case, and each use case comprises a text value in a parent node and text values in a plurality of child nodes corresponding to the parent node.
Determining the corresponding child nodes according to the names of the father nodes, traversing the corresponding child nodes from the father nodes, and storing the text values of all the child nodes under the same link to the LinkedList until the complete thinking case map file is traversed.
S202, storing a plurality of LinkedLists to Arrayleist.
Because Linkedlist is realized based on a linked list, the Linkedlist can be used for representing the relationship of the direct points of a plurality of nodes, is convenient for new addition and deletion operation, and is convenient for moving data, so that a plurality of Linkedlist obtained in S201 can be stored into Arraylist.
S103, acquiring a configuration file of the standard use case template file.
Wherein the configuration file includes a plurality of case names.
And extracting the fixed format in the standard use case template file to form a configuration file convenient to manage, wherein the configuration file can comprise a plurality of use case names.
Illustratively, the use case names in the configuration file may include: 1. a casename, test Name (Name); 2. caseType, use case type; 3. components, modules (Components); 4. first-stage function module; 5. second-level functional module; 6. a threecomponent, a tertiary functional module; 7. fixVersion, versions (Versions); 8. linkedjira no, tag (Labels); 9. casePriority, use case priority; 10. pubilgcase, public use case; 11. assignment, executives (assignment); 12. a description; 13. step, test step description; 14. expectResult, expected outcome; 15. testDate, test data.
Optionally, when a new use case exists, updating the configuration file of the standard use case template file to obtain a new standard use case template file, and storing the updated standard use case template file, wherein the configuration file comprises a name corresponding to the new use case.
By updating the configuration file in the template file of the maintenance standard case, the field value and the corresponding column number of each test case can be updated, and the name of the test case can be updated.
Optionally, the extracted common field may also be presented, as shown in table 1:
table 1, presentation page of public field
| Module to which use case belongs | Database for storing data |
| Version of use case | On-line for 4 months in 2018 |
| Label of use case | KHFW-4400 |
| Upper limit class | Routine on-line |
| Use case tracking user | Sym |
It should be noted that, in table 1, the first column is a common field name, and the second column is a field corresponding to the common field name.
When the value of the module to which the use case belongs is not configured in the use case, the value corresponding to the module to which the use case belongs in table 1 may be selected; when the value of the task to which the use case belongs is not configured in the use case, the value corresponding to the task to which the use case belongs in table 1 can be selected; the version to which the use case belongs, the use case sponsor, etc. may also be as the corresponding values in table 1.
S104, analyzing Arrayist to obtain a plurality of text values corresponding to a plurality of use case names.
Each LinkedList in the ArrayList is circularly traversed as a use case, each LinkedList is analyzed according to the provided rule to obtain text values corresponding to a plurality of use case names, and after analysis is completed, each corresponding text value is written into a newly built excel table until the completion of traversing.
S105, determining a standard table file according to the plurality of case names and text values corresponding to the plurality of case names.
An excel table file can be newly built through an XSSFWorkbook (XSSFWorkbook is a tool kit in Java) in Java, and a plurality of case names in a configuration file in a standard case template file format are imported into a first row or column of the newly built excel, and other rows or columns except the first row or column are text values corresponding to the case names.
Illustratively, a standard table file as shown in table 2 can be obtained from the mind map use case file shown in fig. 1 and the common fields shown in table 1:
table 2, standard form test cases
In table 2, the first behavior case name, the second to seventh behaviors, and text values corresponding to the case names.
According to the method for converting the case file of the mind map, the case names and the corresponding text values are generated into the excel file according to the standard case template configuration items and stored in the file according to the case names in the configuration file of the standard case template format, the time for manually writing the excel case again is reduced, the configuration file can be updated timely, and the standard table file is up to date.
The embodiment of the application can divide the function modules or the function units of the conversion device of the case file of the mind map according to the method example, for example, each function module or each function unit can be divided corresponding to each function, and two or more functions can be integrated in one processing module. The integrated modules may be implemented in hardware, or in software functional modules or functional units. The division of the modules or units in the embodiment of the present application is schematic, which is merely a logic function division, and other division manners may be implemented in practice.
Referring to fig. 9, an embodiment of the present application provides a device for converting a case file of a mind map, which may include an obtaining unit 810, a processing unit 820, and a determining unit 830:
an obtaining unit 810, configured to obtain a mind map use case file, where the mind map use case file includes a plurality of nodes, the plurality of nodes includes a root node, a parent node, and at least one child node corresponding to the parent node, each node stores a text value, and the text value stored by the root node is used to represent a task name of the mind map use case file; the text value stored by the father node is used for representing the task name and/or the module name for executing the task; the text values stored by the child nodes corresponding to the parent nodes are used to represent test operations and expected operation results that can be performed by the tasks and/or modules.
The processing unit 820 is configured to traverse the parent node and a plurality of child nodes corresponding to the parent node to obtain a plurality of text values, and store the plurality of text values into the dynamic array Arraylist.
The obtaining unit 810 is further configured to obtain a configuration file of the standard use case template file, where the configuration file includes a plurality of use case names.
The processing unit 820 is further configured to parse Arraylist to obtain a plurality of text values corresponding to a plurality of use case names.
The determining unit 830 is configured to determine a standard table file according to the plurality of case names and text values corresponding to the plurality of case names.
Optionally, the processing unit 820 is specifically configured to: storing a plurality of text values into a plurality of linked lists LinkedList, wherein each LinkedList comprises a use case, and each use case comprises a text value in a father node and a text value in a plurality of child nodes corresponding to the father node; multiple LinkedList are stored to Arraylist.
Optionally, the processing unit 820 is further configured to: when a new use case exists, updating the configuration file of the standard use case template file to obtain a new standard use case template file, and storing the updated standard use case template file, wherein the configuration file comprises a use case name corresponding to the new use case.
Fig. 10 shows still another possible structural schematic diagram of the conversion device of the case document for mind map related to the above embodiment. The device comprises: a processor 402. The processor 402 is configured to control and manage actions of the apparatus, e.g., perform the steps performed by the acquisition unit 810 described above, and/or to perform other processes of the techniques described herein. The terminal may further comprise a memory 401 and a bus 403, the memory 401 being used for storing program codes and data of the device.
Wherein the processor 402 may implement or execute the various exemplary logic blocks, elements, and circuits described in connection with the present disclosure. The processor may be a central processing unit, a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. Which may implement or perform the various exemplary logic blocks, units and circuits described in connection with this disclosure. The processor may also be a combination that performs the function of a computation, e.g., a combination comprising one or more microprocessors, a combination of a DSP and a microprocessor, etc.
Memory 401 may include volatile memory, such as random access memory; the memory may also include non-volatile memory, such as read-only memory, flash memory, hard disk or solid state disk; the memory may also comprise a combination of the above types of memories.
Bus 403 may be an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus or the like. The bus 403 may be classified into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in fig. 10, but not only one bus or one type of bus.
From the foregoing description of the embodiments, it will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of functional units is illustrated, and in practical application, the above-described functional allocation may be performed by different functional units, that is, the internal structure of the apparatus is divided into different functional units, so as to perform all or part of the functions described above. The specific working processes of the above-described systems, devices and units may refer to the corresponding processes in the foregoing method embodiments, which are not described herein.
Embodiments of the present application also provide a computer-readable storage medium having instructions stored therein that, when executed by a computer, perform the steps of the method flows as shown in fig. 6, 8.
Embodiments of the present application provide a computer program product comprising instructions which, when run on a computer, cause the computer to perform a method of converting a mind map use case file as described in fig. 6, 8.
The computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the computer-readable storage medium would include the following: electrical connections having one or more wires, portable computer diskette, hard disk. Random access Memory (Random Access Memory, RAM), read-Only Memory (ROM), erasable programmable Read-Only Memory (Erasable Programmable Read Only Memory, EPROM), registers, hard disk, optical fiber, portable compact disc Read-Only Memory (CD-ROM), an optical storage device, a magnetic storage device, or any other form of computer-readable storage medium suitable for use by a person or persons of skill in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an application specific integrated circuit (Application Specific Integrated Circuit, ASIC). In embodiments of the present application, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
Since the conversion device, the computer readable storage medium, and the computer program product of the mind map use case document in the embodiments of the present application can be applied to the above method, the technical effects obtained by the method can also refer to the above method embodiments, and the embodiments of the present application are not described herein again.
The foregoing is merely illustrative of specific embodiments of the present application, and the scope of the present application is not limited thereto, but any changes or substitutions within the technical scope of the present application should be covered by the scope of the present application.
In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, for example, multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be through some interface, indirect coupling or communication connection of devices or units, electrical, mechanical, or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.
In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using a software program, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present application are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line (Digital SubscriberLine, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device including one or more servers, data centers, etc. that can be integrated with the medium. The usable medium may be a magnetic medium (e.g., a floppy Disk, a hard Disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a Solid State Disk (SSD)), or the like.
The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (9)
1. The method for converting the thinking guide diagram case file is characterized by being applied to the field of electronic payment and comprising the following steps of:
the method comprises the steps of obtaining a mind map use case file, wherein the mind map use case file comprises a plurality of nodes, each node comprises a root node, a father node and at least one child node corresponding to the father node, each node stores a text value, and the text value stored by the root node is used for representing the task name of the mind map use case file; the text value stored by the father node is used for representing the task name and/or the module name for executing the task; the text value stored by the child node corresponding to the father node is used for representing the test operation executable by the task and/or the module and the expected operation result;
wherein, the thinking guide graph case file is obtained according to the writing rule; the writing rule comprises the following steps: for the use cases of the modules and the tasks to be configured, the parent node is represented by M=module name and T=task name; test names and operation expected results of the split cases are used in the child nodes; the module name comprises login and registration, and the text segment of the child node comprises the steps of opening a login page and clicking a registration button on the login page to jump to the registration page;
traversing the father node and the plurality of child nodes corresponding to the father node to obtain a plurality of groups of text values, and storing the plurality of groups of text values into a dynamic array Arraylist, wherein one group of text values is a use case;
acquiring a configuration file of a standard use case template file, wherein the configuration file comprises a plurality of use case names; if a field with no text value exists in a use case, taking a value corresponding to the field in a preset table as the text value of the field in the use case, wherein the preset table comprises a plurality of field names and text values corresponding to each field name;
analyzing the Arraylist to obtain a plurality of text values corresponding to the plurality of use case names;
and determining a standard table file according to the plurality of case names and the text values corresponding to the plurality of case names.
2. The method for converting a mind map use case file according to claim 1, wherein storing the plurality of text values into a dynamic array Arraylist comprises:
storing the text values into a plurality of linked lists LinkedList, wherein each LinkedList comprises a use case, and each use case comprises a text value in a father node and a text value in a plurality of child nodes corresponding to the father node;
storing the plurality of LinkedList to the Arraylist.
3. The method for converting a case file of a mind map according to claim 1, wherein the method further comprises:
when a new use case exists, updating a configuration file of the standard use case template file to obtain a new standard use case template file, and storing the new standard use case template file, wherein the configuration file comprises a use case name corresponding to the new use case.
4. The device is characterized by being applied to the field of electronic payment and comprising an acquisition unit, a processing unit and a determination unit;
the acquiring unit is configured to acquire the mind map use case file, where the mind map use case file includes a plurality of nodes, the plurality of nodes include a root node, a parent node, and at least one child node corresponding to the parent node, each node stores a text value, and the text value stored in the root node is used to represent a task name of the mind map use case file; the text value stored by the father node is used for representing the task name and/or the module name for executing the task; the text value stored by the child node corresponding to the father node is used for representing the test operation executable by the task and/or the module and the expected operation result;
wherein, the thinking guide graph case file is obtained according to the writing rule; the writing rule comprises the following steps: for the use cases of the modules and the tasks to be configured, the parent node is represented by M=module name and T=task name; test names and operation expected results of the split cases are used in the child nodes; the module name comprises login and registration, and the text segment of the child node comprises the steps of opening a login page and clicking a registration button on the login page to jump to the registration page;
the processing unit is used for traversing the father node and the plurality of child nodes corresponding to the father node to obtain a plurality of groups of text values, storing the plurality of groups of text values into a dynamic array, wherein one group of text values is a use case;
the acquiring unit is further configured to acquire a configuration file of the standard use case template file, where the configuration file includes a plurality of use case names; if a field with no text value exists in a use case, taking a value corresponding to the field in a preset table as the text value of the field in the use case, wherein the preset table comprises a plurality of field names and text values corresponding to each field name;
the processing unit is further used for analyzing the Arraylist to obtain a plurality of text values corresponding to the plurality of use case names;
the determining unit is used for determining a standard table file according to the plurality of case names and text values corresponding to the plurality of case names.
5. The device for converting a case document for a mind map according to claim 4, wherein the processing unit is specifically configured to:
storing the text values into a plurality of linked lists LinkedList, wherein each LinkedList comprises a use case, and each use case comprises a text value in a father node and a text value in a plurality of child nodes corresponding to the father node;
storing the plurality of LinkedList to the Arraylist.
6. The device for converting a case document for a mind map according to claim 4, wherein the processing unit is further configured to:
when a new use case exists, updating a configuration file of the standard use case template file to obtain a new standard use case template file, and storing the new standard use case template file, wherein the configuration file comprises a use case name corresponding to the new use case.
7. A computer readable storage medium storing one or more programs, wherein the one or more programs comprise instructions, which when executed by a computer, cause the computer to perform the method of converting a mind map use case file of any one of claims 1-3.
8. A computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of converting a mind map case file as claimed in any one of claims 1 to 3.
9. The device for converting the mind act drawing use case document is characterized by comprising the following components: a processor and a memory; wherein the memory is configured to store one or more programs, the one or more programs including computer-executable instructions that, when executed by the conversion device of the mind act upon document, cause the conversion device of the mind act upon document to perform the method of converting the mind act upon document of any one of claims 1 to 3.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811513165.3A CN109740122B (en) | 2018-12-11 | 2018-12-11 | Method and device for converting thinking guide graph use case file |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811513165.3A CN109740122B (en) | 2018-12-11 | 2018-12-11 | Method and device for converting thinking guide graph use case file |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109740122A CN109740122A (en) | 2019-05-10 |
| CN109740122B true CN109740122B (en) | 2023-08-29 |
Family
ID=66359018
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811513165.3A Active CN109740122B (en) | 2018-12-11 | 2018-12-11 | Method and device for converting thinking guide graph use case file |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109740122B (en) |
Families Citing this family (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110334024B (en) * | 2019-06-28 | 2023-08-08 | 浙江吉利控股集团有限公司 | Test case management method, device and terminal based on tree structure |
| CN110543427B (en) * | 2019-09-06 | 2023-07-21 | 五八有限公司 | Test case storage method and device, electronic equipment and storage medium |
| CN111338936A (en) * | 2020-02-17 | 2020-06-26 | 贵阳货车帮科技有限公司 | Brain graph data processing method and device, electronic equipment and storage medium |
| CN111290956B (en) * | 2020-02-17 | 2023-09-01 | 贵阳货车帮科技有限公司 | Brain graph-based test method and device, electronic equipment and storage medium |
| CN111538673B (en) * | 2020-06-04 | 2023-07-07 | 中国联合网络通信集团有限公司 | Processing method, device, equipment and storage medium based on test case |
| CN112463596B (en) * | 2020-11-17 | 2023-03-24 | 武汉木仓科技股份有限公司 | Test case data processing method, device and equipment and processing equipment |
| CN112579454B (en) * | 2020-12-23 | 2023-02-24 | 武汉木仓科技股份有限公司 | Task data processing method, device and equipment |
| CN113094288B (en) * | 2021-05-18 | 2022-06-21 | 绿漫科技有限公司 | Method for converting mind map into test case based on Xmind |
| CN113791980A (en) * | 2021-09-17 | 2021-12-14 | 中国平安人寿保险股份有限公司 | Test case conversion analysis method, device, equipment and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1973063A1 (en) * | 2007-03-23 | 2008-09-24 | Palo Alto Research Center Incorporated | Method and apparatus for creating and editing node-link diagrams in PEN computing systems |
| CN106033389A (en) * | 2015-03-11 | 2016-10-19 | 腾讯科技（深圳）有限公司 | A test use case display method and device |
| CN106294664A (en) * | 2016-08-03 | 2017-01-04 | 广州视睿电子科技有限公司 | A kind of method and apparatus generating mind map |
| CN108874671A (en) * | 2018-06-20 | 2018-11-23 | 上海哔哩哔哩科技有限公司 | Testing case management, device, system and storage medium |
-
2018
- 2018-12-11 CN CN201811513165.3A patent/CN109740122B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1973063A1 (en) * | 2007-03-23 | 2008-09-24 | Palo Alto Research Center Incorporated | Method and apparatus for creating and editing node-link diagrams in PEN computing systems |
| CN106033389A (en) * | 2015-03-11 | 2016-10-19 | 腾讯科技（深圳）有限公司 | A test use case display method and device |
| CN106294664A (en) * | 2016-08-03 | 2017-01-04 | 广州视睿电子科技有限公司 | A kind of method and apparatus generating mind map |
| CN108874671A (en) * | 2018-06-20 | 2018-11-23 | 上海哔哩哔哩科技有限公司 | Testing case management, device, system and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| xmind文件转excel文件，java实现;乘虚子;《CSDN》;20170724;第1页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109740122A (en) | 2019-05-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109740122B (en) | Method and device for converting thinking guide graph use case file | |
| US20190272261A1 (en) | Performing logical validation on loaded data in a database | |
| CN108628748B (en) | Automatic test management method and automatic test management system | |
| CN109726105A (en) | Test data building method, device, equipment and storage medium | |
| US20190147029A1 (en) | Method and system for generating conversational user interface | |
| CN101587441A (en) | Apparatus, method, and system of assisting software development | |
| CN112287013B (en) | Data conversion method and adapter | |
| US10769143B1 (en) | Composite index on hierarchical nodes in the hierarchical data model within case model | |
| CA2710405C (en) | Data comparison system | |
| CN116560683A (en) | Software updating method, device, equipment and storage medium | |
| US10503823B2 (en) | Method and apparatus providing contextual suggestion in planning spreadsheet | |
| CN109189688B (en) | Test case script generation method and device and electronic equipment | |
| CN108809896A (en) | A kind of information calibration method, device and electronic equipment | |
| CN117033249A (en) | Test case generation method and device, computer equipment and storage medium | |
| Wang et al. | User-oriented reliability modeling for a web system | |
| CN109474822B (en) | Android television multi-language automatic testing method and device | |
| CN109358919B (en) | Dynamic configuration method and device for universal page, computer equipment and storage medium | |
| WO2020093613A1 (en) | Page data processing method and apparatus, storage medium, and computer device | |
| CN111124883A (en) | Test case library introduction method, system and equipment based on tree form | |
| CN113867700B (en) | Model construction method, display platform, server and storage medium | |
| US11176022B2 (en) | Health diagnostics and analytics for object repositories | |
| CN115454382A (en) | Demand processing method and device, electronic equipment and storage medium | |
| US20210397745A1 (en) | Data providing server device and data providing method | |
| US9471569B1 (en) | Integrating information sources to create context-specific documents | |
| CN116755684B (en) | OAS Schema generation method, device, equipment and medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |