CN117234945A

CN117234945A - Display method and device of test thinking guide diagram, electronic equipment and storage medium

Info

Publication number: CN117234945A
Application number: CN202311489451.1A
Authority: CN
Inventors: 熊路
Original assignee: Innoda Chengdu Electronic Technology Co ltd
Current assignee: Innoda Chengdu Electronic Technology Co ltd
Priority date: 2023-11-10
Filing date: 2023-11-10
Publication date: 2023-12-15
Anticipated expiration: 2043-11-10
Also published as: CN117234945B

Abstract

The application relates to the technical field of computers, in particular to a method and a device for displaying a test thinking guide, electronic equipment and a storage medium, wherein the method comprises the following steps: receiving a first command in a target system, wherein the first command is used for indicating to print a catalog and/or a file under a target catalog on a terminal tool, and a test regression use case is added under at least one catalog; in response to the first command, a target script is invoked within the target system to obtain and expose a test mind map of the target test item on the end tool. Thus, after testing the test points and obtaining the test regression cases, the test regression cases can be added to the directory containing the corresponding test points, and the directory is contained in the mind map. Therefore, the application integrates the test regression use cases on the mind map, thereby avoiding the cross use of a plurality of software, reducing the carding difficulty of the corresponding relation between the test mind map and the test regression use cases and being beneficial to the preservation and maintenance of test data.

Description

Display method and device of test thinking guide diagram, electronic equipment and storage medium

Technical Field

The present application relates to the field of computer technologies, and in particular, to a method and apparatus for displaying a test mind map, an electronic device, and a storage medium.

Background

The EDA is commonly referred to as electronic design automation (Electronics Design Automation), which refers to the use of computer aided design software to aid in the completion of multiple processes such as design, fabrication, packaging, and testing of very large scale integrated circuit chips.

EDA software testing is the process of evaluating and verifying whether an EDA software product is operating as intended, by which errors can be prevented, development costs can be reduced, and performance can be improved. In the related art, in the process of performing a test, a test mind map is generally written using a tool such as Xmind, and a test regression use case is written using a tool such as Excel.

However, due to the cross-use of multiple software, preservation and maintenance of test data is not facilitated. For example, in general, after a worker writes a test regression case using a tool such as Excel, the worker needs to mark a test point corresponding to the test regression case in the test mind map, which indicates that the test has been performed on the test point. If the staff writes the test regression use case, forgetting to mark the test points corresponding to the test regression use case in the test thinking guide diagram, or misplacing the mark time, the test regression use case and the test thinking guide diagram cannot be correctly corresponding. Therefore, in the related art, the carding difficulty of the corresponding relation between the test thinking guide graph and the test regression use case is larger.

Disclosure of Invention

The application provides a display method, a display device, electronic equipment and a storage medium of a test thinking chart, which at least solve the problem that the carding difficulty of the corresponding relation between the test thinking chart and a test regression use case is larger in the related technology.

According to a first aspect of an embodiment of the present application, there is provided a method for displaying a test mind map, including: receiving a first command input into a terminal tool in a target system, wherein the first command is used for indicating that a target directory and/or a file under a target directory are printed in a tree diagram form on the terminal tool based on a target script, the target directory comprises a plurality of levels of subdirectories, the target directory and the levels of subdirectories are pre-created according to target test items, and a test regression use case obtained by testing a test point corresponding to at least one directory is added under at least one directory in the target directory and the levels of subdirectories; and responding to the first command, calling the target script in the target system to acquire and display a tree diagram corresponding to the target catalog on the terminal tool as a test thinking guide diagram of the target test item.

According to a second aspect of an embodiment of the present application, there is provided a display device for a test mind map, including: a first command receiving module configured to receive a first command input to a terminal tool in a target system, wherein the first command is used for indicating that a target directory and/or a file under a target directory are printed in a tree diagram form on the terminal tool based on a target script, the target directory comprises a plurality of levels of subdirectories, the target directory and the levels of subdirectories thereof are pre-created according to target test items, and a test regression case obtained by testing a test point corresponding to at least one directory is added under at least one directory in the target directory and the levels of subdirectories; and the test thinking diagram display module is configured to respond to the first command and call the target script in the target system so as to acquire and display a tree diagram corresponding to the target catalog on the terminal tool as a test thinking diagram of the target test item.

According to a third aspect of an embodiment of the present application, there is provided an electronic apparatus including: a processor; a memory for storing the processor-executable instructions; wherein the processor is configured to execute the instructions to implement the method of presentation of a test mind map in accordance with the present application.

According to a fourth aspect of embodiments of the present application, there is provided a computer-readable storage medium, which when executed by a processor of an electronic device, causes the electronic device to perform the presentation method of a test mind map according to the present application.

The technical scheme provided by the embodiment of the application at least has the following beneficial effects:

in the application, after testing the test points and obtaining the test regression cases, the test regression cases can be added to the directory containing the corresponding test points, and the directory is contained in the mind map. Therefore, the application integrates the test regression use cases on the mind map, thereby avoiding the cross use of a plurality of software, reducing the carding difficulty of the corresponding relation between the test mind map and the test regression use cases and being beneficial to the preservation and maintenance of test data.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application as claimed.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application and do not constitute a undue limitation on the application.

FIG. 1 is a file system tree diagram illustrating a Linux system according to an exemplary embodiment of the present application;

fig. 2 is a flowchart illustrating a presentation method of a test mind map according to an exemplary embodiment of the present application;

FIG. 3 is a schematic diagram illustrating content contained in a readme file according to an example embodiment of the present application;

FIG. 4 is a diagram illustrating the addition of test regression use cases under at least one catalog according to an exemplary embodiment of the present application;

FIG. 5 is a diagram illustrating a test mind map obtained after execution of a "/showmindmap demo" command in accordance with an exemplary embodiment of the present application;

FIG. 6 is a diagram illustrating a test mind map obtained after execution of a "/showmindmap demo-clean" command in accordance with an exemplary embodiment of the present application;

fig. 7 is a tree diagram illustrating connection of directories and files using tree structure connection symbols according to an exemplary embodiment of the present application;

fig. 8 is a tree diagram illustrating another connection of directories and files using tree structure connection symbols according to an exemplary embodiment of the present application;

fig. 9 is a block diagram illustrating a presentation apparatus of a test mind map according to an exemplary embodiment of the present application;

Fig. 10 is a block diagram illustrating an electronic device according to an exemplary embodiment of the present application.

Detailed Description

In order to enable a person skilled in the art to better understand the technical solutions of the present application, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings.

It should be noted that the terms "first," "second," and the like in the description and the claims of the present application and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the application described herein may be implemented in sequences other than those illustrated or otherwise described herein. The embodiments described in the examples below do not represent all embodiments consistent with the application. Rather, they are merely examples of apparatus and methods consistent with aspects of the application as detailed in the accompanying claims.

In the related technology, the test Mind map is generally written by using tools such as Mind Manager, XMIND and the like, and can help to visualize the structure and relation of the test work, and the test information is convenient to organize and view. In addition, in the related art, an Excel tool or other spreadsheet tools are generally used to write a test regression case, that is, a table is created by using the Excel tool or other spreadsheet tools, and information such as a test task, a test state, a test progress, a test priority and the like is recorded.

It should be noted that, the advantage of writing the test mind map by using the tools such as Xmind is obvious, but some disadvantages exist at the same time. The method has the advantages that a graphical interface can be adopted to write a test thinking guide graph, so that the method is clear and visual and is simple to operate; the defects are mainly the following 3 points:

1. each participant needing cooperative work installs related test thinking drawing software;

2. the problem of preservation and maintenance of the test thinking guide diagram;

3. the test thinking guide graph and the test regression case are difficult to accurately correspond to each other.

Moreover, the test regression use case is written by using an Excel tool and the like, so that corresponding advantages and disadvantages also exist. The Excel tool has the advantages that the Excel tool is complete in function and wide in coverage range, and the operation process of writing the test regression case by using the Excel tool is simple, quick and easy to implement; the defects are mainly the following 3 points:

1. each participant needing cooperative work installs relevant office software;

2. testing the storage and maintenance problems of the regression use case;

Therefore, in the related art, when the test mind map and the test regression use case are written, not only the third party software is needed, but also a plurality of third party software are needed to be used in an intersecting way, which increases the difficulty of carding the corresponding relation between the test mind map and the test regression use case and is not beneficial to the preservation and maintenance of test data.

In order to solve the above problems of the related art, the method, the device, the electronic device and the storage medium for displaying the test mind map provided by the application can add the test regression use case to the directory containing the corresponding test point after testing the test point and obtaining the test regression use case, and the directory is contained in the mind map. Therefore, the application integrates the test regression use cases on the mind map, thereby avoiding the cross use of a plurality of software, reducing the carding difficulty of the corresponding relation between the test mind map and the test regression use cases and being beneficial to the preservation and maintenance of test data.

It should be noted that in the Linux operating system, all files and directories may be organized into a tree structure starting with a root node "/". The "directory" here corresponds to a folder in the Windows system, and the directory may be stored in a file or other subdirectories, and the file stores data. In the end tool, the file system tree diagram of the Linux system can be viewed by commanding a "tree".

Fig. 1 is a file system tree diagram illustrating a Linux system according to an exemplary embodiment of the present application. Referring to FIG. 1, the next directory of "demo" has a total of 4 branch directories, which are respectively "test-dir-1", "test-dir-2", "test-dir-3", "test-dir-4", and all the 4 branch directories are connected with the directory "demo". And, there are two branch catalogs under this branch catalog of "test-dir-4", namely "test-dir-4-1" and "test-dir-4-2", these two branch catalogs are connected with catalog "test-dir-4" respectively. Further, a file is corresponding to each of the directory "demo", the directory "test-dir-1", the directory "test-dir-2", the directory "test-dir-3", the directory "test-dir-4-1" and the directory "test-dir-4-2", and the file may be a self-contained file (readme). Also shown at the bottom of fig. 1 is the number of branch directories: 6 directors, total number of files: 7 files.

Under the inspired of the tree diagram of the Linux file system, the application designs the code realization script of the test thinking diagram and the test progress statistics, and the code realization script can realize the functions of displaying the test thinking diagram and the test progress statistics in a terminal tool. The name of the code implementation script may be customized, and may be, for example, a showmindmap script. In addition, the tree command is not used in the code implementation script in the application, in other words, the application is different from the implementation mode for viewing the tree diagram of the Linux file system through the tree command.

Next, the method for displaying the test mind map provided by the present application will be explained in detail with reference to fig. 2 to 9. It should be noted that, the method for displaying the test mind map according to the exemplary embodiment of the present application may be applied to integrated circuit Electronic Design Automation (EDA) software testing, but the present application is not limited thereto, and those skilled in the art may apply the method to testing other types of software.

Fig. 2 is a flowchart illustrating a presentation method of a test mind map according to an exemplary embodiment of the present application.

Referring to fig. 2, in step 201, a first command input to an end tool may be received within a target system. Wherein the first command may be used to instruct printing of directories and/or files under the target directory in a tree view on the terminal tool based on the target script. The target catalog may contain multiple levels of subdirectories, and the target catalog and its multiple levels of subdirectories may be pre-created from the target test item. And a test regression case (case) obtained by testing the test point corresponding to the at least one directory, namely a tcl file, can be added under at least one directory in the target directory and the multi-level subdirectory. The "target system" may be, but is not limited to, a Linux system.

It should be noted that, the tester may edit the whole implementation process of displaying the test mind map and counting the test progress into an executable target script, i.e. a showmindmap script. The showmindmap script may use a tool command language (Tool Command Language, TCL) or other scripting languages, and the present application is not limited to what scripting language the code implementation script specifically uses. And, the showmindmap script mainly relates to two custom functions of '__ SHOW_TREE __' and '__ STATISTICS __'. Wherein. The function __ SHOW_TREE __ is mainly used for showing a test mind map corresponding to the corresponding directory; the function __ STATISTICS __ is mainly used for counting the test progress of the corresponding catalogue.

According to an exemplary embodiment of the present application, before receiving the first command input to the terminal tool in the target system, the target directory and the multi-level subdirectory may be further created according to the target test item, and thus a self-contained file (readme) may be created under each of the target directory and the multi-level subdirectory. Referring back to FIG. 1, the "target directory" may be a directory "demo", and the "multi-level subdirectory" may be a directory "test-dir-1", a directory "test-dir-2", a directory "test-dir-3", a directory "test-dir-4-1" and a directory "test-dir-4-2". And, each of these directories corresponds to a self-describing file.

Furthermore, corresponding test points (test) in the target test items can be written in the self-description file under each directory according to the first preset format, and test regression cases can be added under at least one directory. The test regression use case can be a test regression use case obtained by testing at least one test point written in the self-description file under at least one directory.

The "first preset format", that is, the format of the test point may be in the manner of "test point+test description", that is, the format of the test point may be: "test" + "number" + ": "+" description. By way of example, "test1: the description is written as a test point, and the name of the test point may be "test1".

It should be noted that, if the test point is not written according to the first preset format, the test point cannot be identified as the test point later. Illustratively, for "(not test point) test4: XXX ", since" test "is preceded by additional text content, i.e." not test point ", this will result in a format that does not match the first preset format, at which point this test4 will not be recognized as a test point in the subsequent process.

Fig. 3 is a schematic diagram illustrating contents contained in a readme file according to an exemplary embodiment of the present application. Referring to fig. 3, contents contained in the readme file corresponding to the branch directory "test-dir-4" under the target directory "demo" are shown. The readme file designates that 3 test points exist under the directory test_dir_4, namely test1, test2 and test3; in addition, the readme file also specifies that there are two sub-directories under the directory test_dir_4, i.e., two branch directories, i.e., two directions (there are some directions), respectively "test_dir_4_1" and "test_dir_4_2".

Therefore, the test can be targeted to the test points contained in the self-description file under the specific directory, and the corresponding test regression use case can be added to the directory containing the corresponding test points, and the directory is contained in the test thinking diagram. Therefore, the application integrates the test regression use cases on the test thinking guide graph, thereby avoiding the cross use of a plurality of software, reducing the carding difficulty of the corresponding relation between the test thinking guide graph and the test regression use cases and being beneficial to the preservation and maintenance of test data.

According to an exemplary embodiment of the present application, the test regression use case may include at least one of:

at least one test point written in accordance with the second preset format specification. Wherein, the "second preset format" may be: "set test { test points }" is used to indicate which test points are included in the test regression use case at bottom, i.e., to indicate for which test points the corresponding test regression use case is obtained for testing at bottom. The number of test points included in the test regression case may be plural. For example, the at least one test point specified in the second preset format may be: "set test { test1 test2 }).

It should be noted that, the "test point" in the present application may be represented by "test point" or may be represented by "test" directly, which is not limited by the present application. At this time, at least one test point specified in the second preset format may be expressed as: "set test { test1 test2}" may be also expressed as "set test point { test point 1 test point 2}" or the like.

The test regression use case may also contain verification data for verifying the written at least one test point; a simulated manual operation step for verifying the written at least one test point; the desired result; verifying a result; indication information of whether the expected result is matched with the verification result; the written at least one test point verifies whether the conclusion information is passed. The "verification result" may be a result obtained after performing the simulation manual operation step based on the verification data; the "expected result" described above may be an accurate result that should be obtained after performing the simulated manual operation step based on the verification data.

For example, assuming that the test point to be tested is one addition operation, the "verification data" may be set to data a=2 and data b=3; the above "simulation manual operation step" may include the following 4 simulation steps: (1) Inputting verification data a=2 and b=3 into a test regression system; (2) adding a=2 and b=3; (3) Comparing the verification result obtained by the addition operation based on the verification data with the expected result; (4) And outputting conclusion information of whether the addition operation test point passes or not based on the comparison result.

The "expected result" described above is the exact result that should be obtained after the addition operation is performed based on the verification data a=2, b=3: 5, a step of; the "verification result" is an actual result obtained after performing the addition operation based on the verification data a=2 and b=3, and the actual result may be a correct addition result or an incorrect addition result. For example, the actual result may be the correct addition result 5, or may be the wrong addition result 4, 6 or 7, etc.

The "indication information whether the expected result and the verification result are matched" is the indication information whether the correct addition result 5 is the same as the actual operation result; the "written conclusion information about whether the verification of at least one test point is passed" is "verification passed" information when the expected result 5 is the same as the actual operation result; or "verification failure" information when the expected result 5 is different from the actual operation result.

Fig. 4 is a schematic diagram illustrating the addition of test regression use cases under at least one catalog according to an exemplary embodiment of the present application. Referring to fig. 4, two test regression cases, 1.Tcl and 2.Tcl, respectively, are added under the target directory "demo"; under the branch directory "test-dir-1" 3 test regression cases were added, 1.Tcl, 2.Tcl and 3.Tcl, respectively, and so on. Also shown at the bottom of fig. 4 is the number of branch directories: 6 directors, total number of files: 15 files.

In this way, the test regression use case is controlled to contain the tested test points, so that the follow-up test regression use case is convenient to know which test points are tested in time based on the test points contained in the test regression use case, and the test progress can be conveniently and rapidly counted; further, the regression use case through control test comprises verification data, a simulated manual operation step, an expected result and a verification result; the indication information of whether the expected result is matched with the verification result or not and the conclusion information of whether the verification of the test point is passed or not are equivalent to the detailed record of the complete process of testing the test point, so that the follow-up leak detection and error correction are facilitated.

According to an exemplary embodiment of the present application, after receiving the first command input to the terminal tool in the target system, it may also be determined whether the path name of the directory is included in the first command. It should be noted that the code implementation script, that is, the showmindmap script may include "[ info exists v1]", where [ info exists v1] is used to determine whether the directory is specified in the first command.

When the first command includes a path name, a directory corresponding to the path name may be used as the target directory. That is, when [ info exists v1] determines that the directory is specified in the first command, the absolute path name of the specified directory may be assigned to the "workPath" variable to take the specified directory as the target directory.

Otherwise, the current working directory of the target system may be used as the target directory. That is, in the case where [ info exists v1] determines that the directory is not specified in the first command, the absolute path name of the current working directory may be assigned to the "workPath" variable to take the current working directory as the target directory.

Therefore, the user can decide whether to designate the corresponding catalogue in the first command according to the self requirement, namely, the user can decide which catalogue to display the test mind map according to the self requirement, and the autonomy and flexibility of displaying the test mind map are better. Furthermore, under the condition that the corresponding catalogue is not designated in the first command, the terminal can automatically determine the current working catalogue as the catalogue of the test mind act to be displayed, so that the operation steps of manually designating the catalogue by a user are saved, and the complexity of determining the catalogue of the test mind act to be displayed is reduced.

It should be noted that the code implementation script, i.e. the showmindmap script, may also contain many other functions and commands, eachThe individual functions or commands are used to implement their own functions. For example, a showmindmap script may include, but is not limited to, "" __ STATE __ "function", "" __ POINT_NUM __ "function", "pwd command", "cd command", "find command", "[ llength [ exec find ]{workPath} -name/>.tcl]]"and the like.

The "__ STATE __" function is used for counting the test working STATEs of the catalogue, and the "__ POINT_NUM __" function is used for counting the number of test POINTs of the catalogue.

The pwd (English full spelling: print work directory) command is used for displaying the working directory, and the absolute path name of the working directory where the current working directory is located can be immediately known by executing the pwd command.

The cd (english spelling) command is used to change the current working directory, and switch to the designated path. If the directory name is omitted, the directory name is changed to the home directory (home) of the user, that is, the directory where the user just logged in (login) is located. In addition, "-" also means the home directory; "." is a list showing the current location; "." then indicates the directory of the upper layer of the current directory location.

The find command is used to find files and directories under a specified directory, which can use different options to filter and limit the results of the find. Name pattern: searching by file name, supporting use of wild card ""sum".

[llength [exec find{workPath} -name/>.tcl]]In which "exec" is used to invoke an external command, such as a find command; "length" is used to obtain a specified listThe number of elements in the matrix.

In step 202, in response to the first command, a target script may be invoked within the target system to obtain and present on the terminal tool a tree diagram corresponding to the target catalog as a test mind map for the target test item. That is, in response to the first command, a showmindmap script may be invoked within the Linux system to expose the test mind map and to count the test progress.

It should be noted that the first command must include a basic command, and may include additional options.

The "basic command" may indicate a script path of the showmindmap script, a script name of the showmindmap script, and a target directory. Under the condition that the first command only comprises the basic command, the test thinking guide diagram under the target object can be completely displayed in a full flow and the test progress is counted. The "additional option" is an optional function option for realizing a personalized function such as "show only directory hierarchy", "maximum show directory hierarchy", "prohibit carrying color when printing", and the like.

Taking the example of "/showmindmap demo" where the first command contains only the base command. In the Linux command line, the directory ends with a forward slash "/", the "# indicates the directory in which it is currently located, the combined symbol"/"itself is not a command, but it allows the shell to run executable files directly from the terminal and install any interpreters in the system without double clicking on the files in the graphics file manager.

"showmindmap" is the name of the executable script, and demo is the target directory. Specifically, the "demo" part in the example command indicates that the target directory is a demo directory under the current directory, and in addition, the "demo" part in the example command may be omitted, and the target directory is the current working directory after the omission. Alternatively, the "remove" portion of the example command may also be replaced with the absolute path of the target directory to avoid errors.

After executing the command "/showmindmap demo", the test mind map corresponding to the target directory demo can be obtained. Fig. 5 is a diagram illustrating a test mind map obtained after execution of a "/showmindmap demo" command according to an exemplary embodiment of the present application. Referring to fig. 5, a target directory demo and multi-level subdirectories of the target directory demo are shown. And, the target catalog demo and each catalog in the multi-stage subdirectory thereof correspond to various types of files. By way of example, various types of files may include, but are not limited to, a self-explanatory file (readme), a test regression use case (case), i.e., a tcl file, a test progress file (statics), and the like. Also shown at the bottom of fig. 5 is the number of branch directories: 6 directors, total number of files: 22 files.

Further, take the first command as an example of "/showmindmap de-mo-clean" containing the additional option "- -clean". "-clean" can be the aforementioned "additional option" whose function is to leave no statistically generated "statics" file after the test mind map is presented. The method has the advantages that the displayed test thinking guide diagram is simpler, and the defect that the statistical result of the test progress cannot be further checked at this time due to the lack of the 'statics' file is overcome. And the additional option of "- -clean" can control the terminal not to execute the action of progress statistics, namely, the method of neglecting statics is adopted to display the test thinking guide graph, and the existing "statics" file is deleted.

After executing the first command "/showmindmap demo-clean" a test mind map may be obtained that does not contain a test progress file. Fig. 6 is a diagram illustrating a test mind map obtained after execution of a "/showmindmap demo-clean" command according to an exemplary embodiment of the present application. Referring to fig. 6, a target directory demo and multi-level subdirectories of the target directory demo are shown. And, the target catalog demo and each catalog in the multi-stage subdirectory thereof correspond to various types of files. Executing the "/showmindmap remove-clear" command differs from executing the "/showmindmap remove" command, i.e., fig. 6 differs from fig. 5 in that the test thinking map in fig. 6 does not contain a test progress file statistics. Further, the number of branch directories is also shown at the bottom of fig. 6: 6 directors, total number of files: 15 files.

According to the exemplary embodiment of the present application, at least one of the self-description file, the number of test points, the number of test regression cases, and the directory test state corresponding to each directory in the target directory and the multi-level subdirectory may also be displayed in the test mind map. The self-description file corresponding to any directory may include introduction information, test point information and branch directory information of any directory.

Illustratively, referring back to FIG. 5, the test thought graph in FIG. 5 shows a target directory "demo" and a multi-level subdirectory of the target directory "demo": "test-dir-1", "test-dir-2", "test-dir-3", "test-dir-4", "test-dir-4_1", "test-dir-4_2".

Each of the directories corresponds to a self-contained file (readme), and the self-contained file (readme) may include function introduction information of the corresponding directory, included test point information, and information of a branch directory, i.e., a sub-directory. For example, the self-contained file (readme) under the target directory "demo" may contain 0 site information, information of 4 branch directories ("test-dir-1", "test-dir-2", "test-dir-3", "test-dir-4"), and function introduction information of the target directory "demo"; alternatively, 3 site information, 2 branch directory information ("test_dir_4_1", "test_dir_4_2"), and function introduction information of the sub-directory "test-dir-4" may be contained in the self-description file (readme) under the sub-directory "test-dir-4".

Further, each of the directories may correspond to at least one of the number of test points, the number of test regression cases, and the directory test status. For example, the number of test points corresponding to the target directory "demo" is 18, that is, 18 test points (18 test points), and the number of test regression cases is 8, that is, 8 test regression cases (8 cases), and the directory test state is an "under test (running)" state; or the number of the test points corresponding to the subdirectory 'test-dir-1' is 3, namely 3 test points (3 test points), the number of the test regression cases is 3, namely 3 test regression cases (3 cases), and the directory test state is a 'done' state; or, the number of test points corresponding to the subdirectory "test-dir-4-2" is 3, namely 3 test points (3 test points), the number of test regression cases is 0, namely 0 test regression cases (0 cases), the directory test state is a "not yet started test (no start)" state, and the like.

Therefore, at least one of the number of the self-description files and the test points corresponding to each catalog, the number of the test regression cases and the catalog test state is displayed in the test thinking chart, so that the user can conveniently and intuitively and clearly know the test tasks of each catalog and the test progress speed, and the user can conveniently and macroscopically and roughly control the whole test condition.

According to the exemplary embodiment of the application, for each first subdirectory, according to the superposition condition of the test points contained in the self-description file under the first subdirectory and the test points contained in the test regression use case under the first subdirectory, the directory test state of the first subdirectory can be determined, and the directory test state can be displayed under the first subdirectory. The first subdirectory may be a subdirectory in which no subordinate directory exists in the multi-level subdirectory.

Referring back to fig. 5, the directories "test-dir-1", the directory "test-dir-2", the directory "test-dir-3", the directory "test-dir-4-1" and the directory "test-dir-4-2" in the test mind map shown in fig. 5 are all the first subdirectories in which the lower-level directory does not exist. For each first sub-directory, determining a directory test state of the first sub-directory according to the superposition of the test point contained in the self-description file under the first sub-directory and the test point contained in the test regression case under the first sub-directory, and displaying the directory test state on the right side of the first sub-directory.

For example, for the first subdirectory "test-dir-1", it may be determined first whether a test point is contained in the self-describing file (readme) underneath. Under the condition that the test point is not contained in the self-contained file, the directory test state corresponding to the first subdirectory 'test-dir-1' can be directly determined to be a completion state (done). When the test point is included in the self-contained file below, the coincidence between the test point included in the self-contained file and the test point included in the test regression case below (1. Tcl, 2.Tcl, 3. Tcl) can be determined, and the directory test state corresponding to the first subdirectory "test-dir-1" can be determined based on the coincidence.

Further, when the test points included in the file completely overlap with the test points included in the test regression cases (1.tcl, 2.tcl, 3.tcl), or the test points included in the file belong to a proper subset of the test points included in the test regression cases (1.tcl, 2.tcl, 3.tcl), it may be determined that the directory test state corresponding to the first subdirectory "test-dir-1" is "done state"; when the test point included in the self-description file partially coincides with the test point included in the test regression use case (1. Tcl, 2.Tcl, 3. Tcl), it may be determined that the directory test state corresponding to the first subdirectory "test-dir-1" is the "under test (running)" state; in the case where the test point included in the autofile does not overlap with the test point included in the test regression case (1. Tcl, 2.Tcl, 3. Tcl) at all, or the test point exists in the autofile, but the test regression case is not present under the first subdirectory "test-dir-1", it may be determined that the directory test state corresponding to the first subdirectory "test-dir-1" is a "not yet started test (nostart)" state. Further, the manner of determining the directory test state corresponding to the other first sub-directory is similar to the manner of determining the directory test state corresponding to the first sub-directory "test-dir-1" described above, and will not be described herein.

It should be noted that, because the test regression use case is obtained by testing the test point corresponding to the catalog, once a certain test point included in a certain test regression use case coincides with a certain test point included in the self-description file under the catalog, it is noted that the test point included in the self-description file has been tested. Therefore, whether all the test points corresponding to the directory are tested can be determined based on the coincidence condition of the test points contained in the self-describing file under the directory and the test points contained in the test regression use case under the directory, namely, the directory test state can be determined based on the coincidence condition of the test points, and the accuracy of the determined directory test state can be ensured.

According to the exemplary embodiment of the present application, for each of the target directory and the second sub-directory, the directory test state of each directory may be determined according to the test state of the test point included in the self-description file under each directory and the directory test state of the lower directory of each directory, and the directory test state may be presented under each directory. The second subdirectory may be a subdirectory in which a subordinate directory exists in the multi-level subdirectory.

Referring back to fig. 5, the directory "demo" in the test mind map shown in fig. 5 is a target directory, and the directory "test-dir-4" is a second subdirectory in which the lower-level directories ("test-dir-4-1" and "test-dir-4-2") exist. For the target directory demo and the second subdirectory 'test-dir-4', the directory test state of the corresponding directory can be determined according to the test state of the test point contained in the self-contained file under the corresponding directory and the directory test state of the lower directory of the corresponding directory, and the directory test state can be displayed on the right side of the corresponding directory.

Further, under the condition that the test state of the test point contained in the self-described file under the corresponding directory and the directory test states of all the lower-level directories of the corresponding directory are all complete states, determining that the directory test state of the corresponding directory is the complete state; under the condition that the test states of the test points contained in the self-contained files under the corresponding catalogs and the catalog test states of all the lower catalogs of the corresponding catalogs are not started, determining that the catalog test states of the corresponding catalogs are not started; otherwise, the directory test state of the corresponding directory may be determined to be the under-test state.

For example, for the target directory demo, the underlying self-describing file contains 0 test points, i.e. the underlying self-describing file does not contain any test points, so that the file test state corresponding to the self-describing file can be directly determined to be a completion state. In the lower-level catalogs of the target catalogs demo, namely, in the multi-level subdirectories, the catalogs test states corresponding to the catalogs test-dir-1 and the catalogs test-dir-4-1 are all complete states; the catalog test states corresponding to the catalog test-dir-2 and the catalog test-dir-4 are in-test states; the directory test states corresponding to the directory test-dir-3 and the directory test-dir-4-2 are not-yet-started test states. Therefore, the directories in the under-test state and the not-yet-started test state exist in the lower-level directories of the target directory demo, that is, all the lower-level directories of the target directory demo are not completely tested, so that the directory test state corresponding to the target directory demo can be determined to be the under-test (oning) state.

Or, for the second sub-directory test-dir-4, the lower self-description file contains 3 test points, and the directory test state corresponding to the directory "test-dir-4-1" in the lower directory of the second sub-directory test-dir-4 is a completion state; the directory test state corresponding to the directory 'test-dir-4-2' in the lower directory of the second subdirectory test-dir-4 is a not-yet-started test state. It can be seen that, the lower-level directories of the second sub-directory test-dir-4 still have directories in a state that the test has not been started, i.e. all the lower-level directories of the second sub-directory test-dir-4 are not completely tested, so that it can be determined that the directory test state corresponding to the second sub-directory test-dir-4 is an under-test (ongoing) state.

It should be noted that a certain directory may be a lower directory of another directory only if the relationship with the other directory is relatively close. Therefore, in determining the directory test state of the directory for the directory where the subordinate directory exists, it is necessary to consider the directory test states of all the subordinate directories of the directory in addition to the test states of the test points in the self-contained files under the directory itself. Therefore, the user can generally judge what test state the lower-level catalogue of the catalogue is in based on the catalogue test state of a certain catalogue, and the user can intuitively and clearly know what test state the lower-level catalogue of the current catalogue is in.

Further, in determining the directory test state of the target directory and the second subdirectory, there may be other manners besides the foregoing manner. For example, the directory test status of the corresponding directory may also be determined directly based on the coincidence of all the test points under the corresponding directory and the test points included in all the test regression cases under the corresponding directory. Wherein, all the test points under the corresponding directory include the test points contained in the self-describing file under the corresponding directory and the test points contained in the self-describing file of all the subordinate directories of the corresponding directory; the "all test regression cases under the corresponding directory" includes the test regression cases under the corresponding directory and all the test regression cases under the lower-level directory of the corresponding directory.

According to an exemplary embodiment of the present application, for each first subdirectory, the number of test points contained in the self-describing file under the first subdirectory may be determined. The first subdirectory may be a subdirectory in which no subordinate directory exists in the multi-level subdirectory. The number of test points contained in the self-contained file may then be presented under a first sub-list.

Referring back to fig. 5, the directories "test-dir-1", the directory "test-dir-2", the directory "test-dir-3", the directory "test-dir-4-1" and the directory "test-dir-4-2" in the test mind map shown in fig. 5 are all the first subdirectories in which the lower-level directory does not exist. For each first subdirectory, the number of test points contained in the self-contained file under the first subdirectory can be determined, and then the number of test points contained in the self-contained file can be displayed on the right side of the first subdirectory.

Illustratively, for a first subdirectory "test-dir-2" the number of test points contained in the underlying self-contained file may be presented to the right of the first subdirectory "test-dir-2": "3 test points"; alternatively, for the first subdirectory "test-dir-4-2", 3 test points are also contained in the underlying self-contained file, so the number of test points contained in the underlying self-contained file can be presented to the right of the first subdirectory "test-dir-4-2": "3 test points".

According to an exemplary embodiment of the present application, for each of the target directory and the second sub-directory, a first number of test points included in the self-contained file under each directory may be determined. Wherein the second subdirectory may be a subdirectory in which a subordinate directory exists in the multi-level subdirectory. Then, a second number of test points contained in the self-contained files of all the lower directories of each directory may also be determined. Next, the sum of the first number and the second number may be calculated to obtain the total number of test points. Finally, the total number of test points can be presented under each directory.

Referring back to fig. 5, the directory "demo" in the test mind map shown in fig. 5 is a target directory, and the directory "test-dir-4" is a second subdirectory in which the lower-level directories ("test-dir-4-1" and "test-dir-4-2") exist.

For a target directory demo, a first number of test points contained in the self-contained file under the target directory demo may be determined. Wherein the first number is 0. Then, a second number of test points contained in the self-explanatory file of all the lower directories of the target directory demo may also be determined. For example, all subordinate directories of the target directory demo may be determined: the second number of test points contained in the self-contained file of each lower directory in the directory "test-dir-1", the directory "test-dir-2", the directory "test-dir-3", the directory "test-dir-4-1" and the directory "test-dir-4-2". The second number of test points included in the self-file of each lower directory in the 6 lower directories may be 3. Next, the sum of the first number and the second number may be calculated to obtain the total number of test points: 0+3+3+3+3+3=18. Finally, the total number of test points can be presented on the right side of the target directory demo: "18 test points".

Alternatively, for the second sub-directory "test-dir-4", a first number of test points contained in the self-contained file under the second sub-directory "test-dir-4" may be determined. Wherein the first number is 3. Then, a second number of test points contained in the self-contained files of all the lower directories of the second sub-directory "test-dir-4" may also be determined. For example, all lower directories of the second subdirectory "test-dir-4" may be determined: the second number of test points contained in the self-contained file for each of the lower directories in the directories "test-dir-4-1" and "test-dir-4-2". The second number of test points included in the self-file of each of the 2 lower directories may be 3. Next, the sum of the first number and the second number may be calculated to obtain the total number of test points: 3+3+3=9. Finally, the total number of test points may be presented on the right side of the second subdirectory "test-dir-4": "9 test points".

Thus, as described above, a directory may be a lower directory of another directory only if it has a relatively close relationship with the other directory. Therefore, in determining the number of test points corresponding to a directory where a lower-level directory exists, it is necessary to consider the number of test points included in the self-contained files of all the lower-level directories of the directory in addition to the number of test points in the self-contained files under the directory itself. Therefore, a user can generally judge how many test points are approximately contained in the self-contained file of the lower-level directory of the directory only by the number of the test points corresponding to a certain directory, so that the user can intuitively and clearly know how many test points correspond to the lower-level directory of the current directory.

According to an exemplary embodiment of the present application, for each of the target directory and the second subdirectory, a third number of test regression cases under each directory may be determined. Then, a fourth number of test regression cases under all the lower level directories of each directory may also be determined. Next, the third number and the fourth number may be summed to obtain a total number of test regression cases. Finally, the total number of test regression cases may be presented under each catalog.

For a target catalog demo, a third number of test regression cases under the target catalog demo may be determined. Wherein the third number is 2, 1.Tcl and 2.Tcl, respectively. Then, a fourth number of test regression cases under all the lower level directories of the target directory demo may also be determined. For example, all subordinate directories of the target directory demo may be determined: the fourth number of test regression cases under each of the lower level directories in the directory "test-dir-1", the directory "test-dir-2", the directory "test-dir-3", the directory "test-dir-4-1" and the directory "test-dir-4-2". The fourth number of test regression cases under each directory in the directory of 'test-dir-2', the directory of 'test-dir-4' and the directory of 'test-dir-4-1' is 1; the fourth number of the test regression cases under each directory in the directory 'test-dir-3' and the directory 'test-dir-4-2' is 0; the fourth number of test regression cases under the catalog "test-dir-1" is 3. Next, the sum of the third number and the fourth number may be calculated to obtain the total number of test regression cases: 2+1+1+0+0+3=8. Finally, the total number of test regression cases can be presented on the right side of the target catalog demo: "8 cases".

Alternatively, for the second sub-directory "test-dir-4", a third number of test regression cases under the second sub-directory "test-dir-4" may be determined. Wherein the third number is 1. Then, a fourth number of test regression cases under all the lower level directories of the second sub-directory "test-dir-4" may also be determined. For example, all lower directories of the second subdirectory "test-dir-4" may be determined: fourth number of test regression cases under each lower level directory in the directories "test-dir-4-1" and "test-dir-4-2". Wherein, the fourth number of test regression cases under the catalog "test-dir-4-1" is 1; the fourth number of test regression cases under the catalog "test-dir-4-2" is 0. Next, the sum of the third number and the fourth number may be calculated to obtain the total number of test regression cases: 1+1+0=2. Finally, the total number of test regression cases may be presented on the right side of the second subdirectory "test-dir-4": "2 cases".

Thus, as described above, a directory may be a lower directory of another directory only if it has a relatively close relationship with the other directory. Therefore, when determining the number of test regression cases corresponding to a directory in which a lower-level directory exists, it is necessary to consider the number of test regression cases in all the lower-level directories of the directory in addition to the number of test regression cases in the directory itself. Therefore, the user can generally judge how many test regression cases are contained in the lower-level catalogue of the catalogue based on the number of the test regression cases corresponding to a certain catalogue, so that the user can intuitively and clearly know how many test regression cases correspond to the lower-level catalogue of the current catalogue.

Additional options may also be included in the first command described above, according to an exemplary embodiment of the present application. Wherein the additional options may include at least one of:

a manual for showing the script (the "—h" or "—hellp" option) is mainly used for showing the code implementation script, i.e., a manual for the showmindmap script.

The catalog to be presented, i.e. the target catalog that needs to present the test mind map, such as catalog demo in the example above, can be specified with one parameter (parameter).

Only the directory level is shown ("-d" option) and this additional option is mainly used to control the test mind map to show only the directory level, i.e. control the self-contained file (readme); testing regression cases (cases), i.e., X.tcl; files such as a test progress file (statics) are not shown.

It should be noted that if the first command includes the additional option "-D", the "__ showy_tree_d __" function in the showmindmap script may be called to SHOW the test mind map, and only the target directory and all levels of subdirectories will be shown in the test mind map, but files under the directory will not be shown; if the additional option "-d" is not included in the first command, the "__ SHOW_TREE __" function in the showmindmap script may be called to expose the test mind map. At this time, the test mind map includes a target directory, multi-level subdirectories under the target directory, and various types of files under each directory. The two functions, "__ showy_tree_d __" and "__ showy_tree __" are similar in overall execution flow, except that the print results are different.

Maximum show directory level ("-l < level >" option) that is used primarily to specify the maximum show directory level in the test mind map.

Illustratively, referring back to FIG. 5, the target directory demo has a presentation level of level 0; directory "test-dir-1", directory "test-dir-2", directory "test-dir-3", directory the display level of the directory "test-dir-4" is level 1; the display level of the directories "test-dir-4-1" and "test-dir-4-2" is level 2. If the user designates the maximum display directory level as level 1 in the first command, only the target directory demo will be displayed in the test mind map; an autofile (readme) under the target directory demo, a test regression use case (1. Tcl,2. Tcl), and a test progress file (statics); directory "test-dir-1", directory "test-dir-2", directory "test-dir-3", directory "test-dir-4". Other directories and/or files have corresponding display levels exceeding level 1, so that the directories and/or files with display levels exceeding level 1 are not displayed on the test mind map.

The color is prohibited to be carried when printing ("-color=none" option), and the additional option is mainly used for controlling the color is prohibited to be carried when printing the test mind map.

The presentation of the test progress file is prohibited ("-ignow = statistics" option) and this additional option is mainly used to control the presentation of the "statistics" file when printing the test mind map.

The presentation of the self-contained file and the test progress file ("-ignore" option) is prohibited, and the additional option is mainly used for controlling the presentation of the self-contained file and the test progress file to be prohibited when the test mind map is printed.

The retention of generated test progress files (statistics) is prohibited after presentation, and the additional option is mainly used for controlling that the generated statistics files are not retained after the test mind map is printed.

And acquiring and displaying the tree diagram corresponding to the target catalog on the terminal tool as a test thinking guide diagram of the target test item according to the additional options contained in the first command.

Therefore, the user can determine which additional options are contained in the first command according to the self requirement, and further can realize corresponding functions when the test mind map is displayed, namely, the user can autonomously determine why the test mind map is specifically displayed, and the autonomy and flexibility of displaying the test mind map are better.

According to the exemplary embodiment of the application, in the case that the first command contains the option of 'carrying color during printing' in the first command, the test mind map can be printed according to the default color preset in the target system and displayed on the terminal tool, namely, the test mind map can be printed according to the default color preset in the Linux system. For example, the default color preset in the Linux system may be black.

In the case where the option of "carry color during printing" is not included in the first command, each object may be printed to show the test mind act on the terminal tool based on the showing color preset for each object in the target script.

It should be noted that different types of color variables may be set in the target script, i.e., the showmindmap script in advance. Illustratively, the showmindmap script may include, but is not limited to, the following color variables: "default: cdefault "," catalog: cdirectory "," executable file: cfileexe "," document: cfilers "," character string: cstrred, cstrblue, cstrgreen, cstryellow, cstrbred).

If the first command contains the additional option "- -color=none" or "- -color=none", then the assignment of each color variable (e.g., cdefault, cdirectory, etc.) contained in the showmindmap script may be set to null. At this time, the test mind map is printed according to a default color preset in the Linux system.

If the first command does not include the additional option "- -color=none" or "- -color=none", the assignment can be performed for each color variable according to the custom color preset in the showmindmap script. For example, a "directory" may be set in advance in the showmindmap script: the color variable cdirectory "corresponds to the display color blue. Thus, when the test mind map is actually printed, the following description is given to the "directory" according to the showmindmap script: the color setting of this color variable prints the directory in the test mind map as blue.

Further, the variable values of "\033\0 m", "\033\1; 34m", "\033\32 m", etc. may be font values and/or color number values of the TCL script language itself. For example, "1" in "\033\1; 34m" may represent font bolding; "34" may represent a color number. The values of the two parts can be adjusted, and the rest parts are fixed usage.

Therefore, the user can preset the values of various color variables in the showmindmap script according to the self requirement, further different objects can be printed by using different colors, and the aim of presenting a test mind map with distinct boundaries and clear framework among different types of objects to the user can be achieved, so that the user can quickly and accurately know the organization framework and composition of the whole test mind map.

According to an exemplary embodiment of the present application, the target script may also be used to generate a target directory and a test progress file corresponding to each directory in the multi-level subdirectory. The test progress file corresponding to any directory may be used to indicate the test progress under any directory. I.e. after invoking the target script within the target system, a second command input to the end tool may also be received within the target system. The second command may include a path name of a specified directory, where the specified directory may be one of a target directory or a multi-level subdirectory. Next, in response to the second command, the contents in the test progress file under the specified directory may be printed on the terminal tool.

For example, referring back to fig. 5, the test mind map shown in fig. 5 includes a target directory demo and multiple levels of subdirectories of the target directory demo, where each of these directories corresponds to a test progress file (statistics). The user can display the specific content contained in the test progress file under the appointed directory only by filling one directory appointed in the directories in the second command. Therefore, the user can decide which content of the test progress file under the catalog is displayed according to the self requirement, and the autonomy and flexibility of the test progress corresponding to the display catalog are good.

According to an exemplary embodiment of the present application, at least one of the following included in the test progress file under the specified directory may be printed on the terminal tool:

the number of test points corresponding to the specified directory, the number of test regression cases corresponding to the specified directory, and the percentage between the number of test points which have completed testing among the test points corresponding to the specified directory and the number of all test points corresponding to the specified directory; the method comprises the steps of designating a file test state corresponding to a self-contained file under a catalog, designating a test point which is not started to be tested in a test point contained in the self-contained file under the catalog, and designating a percentage between the number of test points which are tested in the test point contained in the self-contained file under the catalog and the number of all test points contained in the self-contained file.

Illustratively, taking "cat remo/statistics" as an example of the second command, i.e., assume that the specified directory contained in the second command is the target directory remo.

Wherein "cat" in the second command "cat remove/statistics" is an abbreviation of "con cate" for creating, viewing and connecting files directly from the terminal, mainly for previewing files without opening the graphic text editor. The "deo/statics" in the second command "cat deo/statics" represents a "statics" file under the target directory deo.

The following is the contents of the test progress file shown after the execution of the second command "cat remove/statics":

YYY@ip-111111111111: ~ ]cat demo/statistics

The total number of the test points：18

The total number of the regression cases：8

The rate of progress（finished-test-point-num/ total-test-point-num）：8/18=44%

-- home/YYY/demo：done

-- home/YYY/demo/ test-dir-1：done

--The rate of progress of the home/YYY/demo/ test-dir-1：3/3=100%

-- home/YYY/demo/ test-dir-2：ongoing

-- test1 is not being tested

-- test3 is not being tested

-- The rate of progress of the home/YYY/demo/ test-dir-2：1/3=33%

-- home/YYY/demo/ test-dir-3：nostart

-- test1 is not being tested

-- test2 is not being tested

-- test3 is not being tested

-- The rate of progress of the home/YYY/demo/ test-dir-3：0/3=0%

-- home/YYY/demo/ test-dir-4：ongoing

-- test2 is not being tested

-- test3 is not being tested

-- The rate of progress of the home/YYY/demo/ test-dir-4：1/3=33%

-- home/YYY/demo/ test-dir-4/test-dir-4-1：done

--The rate of progress of the home/YYY/demo/ test-dir-4/ test-dir-4-1：3/3=100%

-- home/YYY/demo/ test-dir-4/test-dir-4-2：nostart

-- test1 is not being tested

-- test2 is not being tested

-- test3 is not being tested

-- The rate of progress of the home/YYY/demo/test-dir-4/test-dir-4-2：0/3=0%

the content in the test progress file shown after the second command "cat demo/statics" is executed can be known, and the "statics" file under the target directory demo contains the number of test points corresponding to the target directory demo: "The total number of the test points:18"; the number of test regression cases corresponding to the target catalog demo: "The total number of the regression cases: 8'; the percentage between the number of test points which have been tested in the test points corresponding to the target catalog demo and the number of all test points corresponding to the target catalog demo: "The rate of progress (final-test-point-num/total-test-point-num): 8/18 = 44% ".

Also, as described above, since the number of test points included in the self-contained file under the target directory demo is 0, that is, the self-contained file under the target directory demo does not include any test points, the file test state corresponding to the self-contained file under the target directory demo may be directly determined as "done state done", that is, "-home/YYY/demo: done).

Further, the test progress file of the target directory demo may further include test conditions of test points included in the test progress file under each level of sub-directory under the target directory demo. For example, a multi-level subdirectory under the target directory demo may also be shown: test status of test points contained in the self-contained file under each sub-directory in the directory "test-dir-1", the directory "test-dir-2", the directory "test-dir-3", the directory "test-dir-4-1" and the directory "test-dir-4-2".

For the subdirectory 'test-dir-1', the self-description file below contains 3 test points in total, and all the 3 test points are tested. Therefore, the file test state corresponding to the self-describing file under the subdirectory "test-dir-1" is the completion state: "-home/YYY/remove/test-dir-1: done "; the percentage between the number of test points which have completed the test in the test points contained in the self-contained file under the subdirectory "test-dir-1" and the total number of test points contained in the self-contained file is 100%: "The rate of progress of the home/YYY/demo/test-dir-1: 3/3=100% ".

For the subdirectory "test-dir-2", a total of 3 test points are contained in the underlying self-contained file, and two of the 3 test points have not yet been tested: "test1 is not being tested; test3 is not being tested). Therefore, the file test state corresponding to the self-describing file under the subdirectory "test-dir-2" is the under-test state: "-home/YYY/remove/test-dir-2: inging "; the percentage between the number of test points that have completed testing among the test points contained in the self-contained file under the subdirectory "test-dir-2" and the total number of test points contained in the self-contained file is 33%: "The rate of progress of the home/YYY/demo/test-dir-2: 1/3=33% ".

For the subdirectory "test-dir-3", a total of 3 test points are contained in the underlying self-contained file, and none of these 3 test points are tested: "test1 is not being tested, test2 is not being tested, test3 is not being tested". Therefore, the file test state corresponding to the self-describing file under the subdirectory "test-dir-3" is the not-yet-started test state: "-home/YYY/remove/test-dir-3: nodtart "; the percentage between the number of test points which have completed the test in the test points contained in the self-contained file under the subdirectory "test-dir-3" and the total number of test points contained in the self-contained file is 0%: "The rate of progress of the home/YYY/demo/test-dir-3: 0/3=0% ".

For the subdirectory "test-dir-4", a total of 3 test points are contained in the underlying self-contained file, and two of the 3 test points have not yet been tested: "test2 is not being tested, test3 is not being tested". Therefore, the file test state corresponding to the self-describing file under the subdirectory "test-dir-4" is the under-test state: "-home/YYY/remove/test-dir-4: inging "; the percentage between the number of test points that have completed testing from among the test points contained in the self-contained file under the subdirectory "test-dir-4" and the total number of test points contained in the self-contained file is 33%: "The rate of progress of the home/YYY/demo/test-dir-4: 1/3=33% ".

For the subdirectory "test-dir-4-1", the following self-contained files contain 3 test points in total, and all the 3 test points are tested, so the file test state corresponding to the self-contained files under the subdirectory "test-dir-4-1" is the completion state: "-home/YYY/remove/test-dir-4/test-dir-4-1: done "; the percentage between the number of test points which have completed testing in the test points contained in the self-contained file and the total number of test points contained in the self-contained file under the subdirectory of 'test-dir-4-1' is 100%: "The rate of progress of the home/YYY/demo/test-dir-4/test-dir-4-1: 3/3=100% ".

For the subdirectory "test-dir-4-2", a total of 3 test points are contained in the underlying self-contained file, and none of these 3 test points are tested: "test1 is not being tested, test2 is not being tested, test3 is not being tested". Therefore, the file test state corresponding to the self-described file under the subdirectory "test-dir-4-2" is the not-yet-started test state: "-home/YYY/remove/test-dir-4/test-dir-4-2: nodtart "; the percentage between the number of test points which have completed the test in the test points contained in the self-contained file and the total number of test points contained in the self-contained file under the subdirectory of "test-dir-4-2" is 0%: "The rate of progress of the home/YYY/deo/test-dir-4/test-dir-4-2: 0/3=0% ".

Alternatively, assuming that the second command is "cat demo/test-dir-4/statistics", that is, assuming that the directory instructed by the user in the second command is the directory "test-dir-4", the content of the test progress file under the directory "test-dir-4" may be presented after the second command "cat demo/test-dir-4/statistics" is executed.

By way of example, at least one of the following may be presented:

number of test-dir-4 corresponding test points: "The total number of the test points: 9'; number of test regression cases corresponding to test-dir-4: "The total number of the regression cases: 2'; the percentage between the number of the test points which are already tested in the test points corresponding to the test-dir-4 and the number of all the test points corresponding to the test-dir-4; the test states of the corresponding files under test-dir-4, namely the test states of 3 test points contained in the self-described files under test-dir-4; test-dir-4 is a test point which is not started to be tested in 3 test points contained in the self-contained file; the percentage between the number of test points that have completed testing in the 3 test points contained in the self-contained file under test-dir-4 and the total number of test points contained in the self-contained file, 3.

Therefore, by setting a plurality of contents related to the test points and the test regression cases in the test progress file, a user can clearly and comprehensively know the test progress under the corresponding directory, and the user can conveniently control the test conditions under the corresponding directory in an omnibearing manner.

According to the exemplary embodiment of the application, under the condition that test points contained in the self-describing file under the appointed directory are all tested, the file test state corresponding to the self-describing file under the appointed directory can be determined to be a finished state done; under the condition that test points contained in the self-contained file under the appointed directory are not tested, the file test state corresponding to the self-contained file under the appointed directory can be determined to be a non-started test state; otherwise, the file testing state corresponding to the self-describing file under the specified directory can be determined to be the state under test ong.

For example, referring back to the content of the test progress file of the target directory demo shown above, for the directory "test-dir-4-1", since all 3 test points included in the self-description file under the directory have been tested, it may be determined that the file test state corresponding to the self-description file under the directory "test-dir-4-1" is the done state done; for the directory "test-dir-4-2", no test is initiated since none of the 3 test points contained in the self-contained file under the directory: "test1 is not being tested, test2 is not being tested, test3 is not being tested", therefore, it can be determined that the file test state corresponding to the self-described file under the directory "test-dir-4-2" is not yet started test state nosttart; for the directory "test-dir-4", since two test points out of 3 test points contained in the file under the directory have not yet been tested: "test2 is not being tested, test3 is not being tested", it is thus possible to determine that the file test status corresponding to the self-contained file under the directory "test-dir-4" is the under-test status ong.

According to the exemplary embodiment of the present application, the target directory is further used as a starting point, and the directory and/or the file under the target directory are sequentially printed in a recursive traversal manner until the target directory, the multi-level subdirectory, the file under the target directory and the file under the multi-level subdirectory are traversed. Namely, the target catalog demo is taken as a starting point, and the catalog and/or the file under the target catalog demo are sequentially printed in a recursion traversing manner until the target catalog demo, the multi-level subdirectory (catalog "test-dir-1", catalog "test-dir-2", catalog "test-dir-3", catalog "test-dir-4-1" and catalog "test-dir-4-2"), the file under the target catalog demo and the file under the multi-level subdirectory are traversed.

Wherein for each traversal, the following operations may be performed:

the type of the current traversal object is obtained. The types of the current traversal object can include two types, namely a directory type and a file type.

In the case that the type of the current traversal object is a file, the current traversal object may be printed based on a presentation color preset for the file in the target script. It should be noted that, the user may preset the display colors of different types of files in the showmindmap script. For example, the test regression use case may be preset to show a color of black, a color of blue-green from the document, and so on. Therefore, when the test thinking guide graph is actually printed, corresponding files can be printed according to preset display colors aiming at different types of files in the showmindmap script.

Under the condition that the type of the current traversal object is a directory, the directory test state, the number of test points and the number of test regression cases corresponding to the current traversal object can be obtained, the current traversal object can be printed based on the display color preset for the directory in the target script, and the directory test state, the number of test points and the number of test regression cases corresponding to the current traversal object can be printed under the current traversal object based on the display color preset for the character string in the target script.

It should be noted that, the user may preset the catalog and the display colors of the different types of character strings in the showmindmap script. For example, the display color of the catalog may be preset to be blue, the number of test points and the number of test regression cases may be preset to be yellow, the display color of the catalog test state of "complete test" may be preset to be green, the display color of the catalog test state of "under test" may be purple, the display color of the catalog test state of "not yet started test" may be red, and so on. Therefore, when the test mind map is actually printed, corresponding objects can be printed according to preset display colors aiming at the catalogue and various character strings in the showmindmap script.

In this way, by printing each directory and/or file in a recursive traversal manner, any directory or file may be prevented from being missed. In addition, by presetting the display colors of different types of objects in the showmindmap script, a test thinking guide diagram with clear boundaries and clear framework among different types of objects can be presented to a user, so that the user can quickly and accurately know the organization framework, component composition and test condition of the whole test thinking guide diagram.

It should be noted that, a connection symbol variable for connecting different directories and connecting the directories and files may also be preset in the showmindmap script. For example, the following connection symbol variables representing different positions may be preset in the showmindmap script:

first alignment symbol: branch_vline, used for an element in a specified directory if the specified directory is not the last element in its previous hierarchical directory (an element refers to a directory or file);

second alignment symbol: branch_null is used for an element in a specified directory if the specified directory is the last element in its previous hierarchical directory;

Middle branch symbol: middlebranch end, for use if the element in the specified directory is not the last element in the specified directory;

last branch symbol: last_branch_end, used in case the element in the specified directory is the last element in the specified directory;

hierarchical pair Ji Bianliang: branch_sum is used to cooperate with "branch_vline" or "branch_null" to align the level branches when printing the test mind map.

Furthermore, corresponding tree structure connection symbols can be preset for different connection symbol variables in the showmindmap script. Illustratively, the first alignment symbology: the tree structure connection symbol corresponding to the branch_vline may be: "|·"; second alignment symbol: the tree structure connection symbol corresponding to branch_null may be: "-"; middle branch symbol: the tree structure connection symbol corresponding to the middle_branch_end may be: "-x"; last branch symbol: the tree structure connection symbol corresponding to last_branch_end may be: "-x".

According to the exemplary embodiment of the present application, in the case where the element to be printed currently is the element directly contained in the target directory, it may be determined whether the element to be printed currently is the last element in the target directory. As described above, the meaning of "element" herein may be "directory" or "file". Fig. 7 is a tree diagram illustrating connection of directories and files using tree structure connection symbols according to an exemplary embodiment of the present application. Referring to fig. 7, the target directory demo next contains 7 elements directly in total, and is respectively a directory "test-dir-1", a directory "test-dir-2", a directory "test-dir-3", a directory "test-dir-4", a self-contained file (readme), 1.Tcl and 2.Tcl in order. For any one of the 7 elements, it may be determined whether the any one element is the last element under the target directory demo.

And under the condition that the element to be printed is not the last element in the target directory, connecting the target directory and the element to be printed in the tree diagram by utilizing a preset first symbol. For example, assuming that the element to be printed currently is the directory "test-dir-2", since the directory "test-dir-2" is the 2 nd element under the directory demo, that is, the directory "test-dir-2" is not the last element under the target directory demo, the target directory demo and the element to be printed currently can be connected in the tree diagram by using the preset first symbol: catalog "test-dir-2". The "preset first symbol" may be the above intermediate branch symbol: "-Ix".

Otherwise, the target catalog and the element to be printed currently can be connected in the tree diagram by using the preset second symbol under the condition that the element to be printed currently is the last element in the target catalog. For example, referring back to fig. 7, assuming that the element to be printed is a 2.Tcl file under the target directory demo, since "2.Tcl file" is the 7 th element under the target directory demo, that is, "2.Tcl file" is the last element under the target directory demo, the target directory demo and the element to be printed can be connected in the tree diagram by using the preset second symbol: "2.Tcl File". The "preset second symbol" may be the last branch symbol described above: "-x".

Therefore, the method and the device can realize that a test thinking chart with distinct and clear levels is presented to a user by connecting the elements to be printed and the catalog by using different types of tree structure connection symbols based on the positions of the elements to be printed in the catalog, thereby being convenient for the user to quickly and accurately comb the architecture relations among different catalogs and among files and catalogs.

According to an exemplary embodiment of the present application, in the case where an element to be currently printed is an element indirectly included in a target directory, for each directory in each hierarchical upper-level directory of elements to be currently printed, it may be determined whether or not the each directory is the last element under the immediately upper-level directory of the each directory. Fig. 8 is a tree diagram illustrating another connection of directories and files using tree structure connection symbols according to an exemplary embodiment of the present application. Referring to fig. 8, the target directory demo contains 7 elements directly in total, and the target directory demo is a self-contained file (readme), a.tcl, b.tcl, a directory "zz-dir-1", a directory "zz-dir-2", a directory "zz-dir-3", and a directory "zz-dir-4" respectively in order of sequence. The branch directory and the file under each directory in the directory "zz-dir-1", the directory "zz-dir-2", the directory "zz-dir-3" and the directory "zz-dir-4" are the elements indirectly contained in the target directory demo.

In the case that each directory is not the last element under the immediately superior directory of each directory, the immediately superior directory and the element to be printed currently may be connected in the tree diagram using a preset third symbol. The "preset third symbol" may be the first alignment symbol number: "|·.

For example, referring back to fig. 8, for the self-contained file (readme) under the directory "zz-dir-1", the upper level directory of the self-contained file (readme) is the directory "zz-dir-1", and since the upper level directory "zz-dir-1" is the 4 th element under the directly upper level directory demo of the upper level directory "zz-dir-1", that is, the upper level directory "zz-dir-1" is not the last element under the directly upper level directory demo of the upper level directory "zz-dir-1", the directly upper level directory demo and the element to be printed currently can be connected in the tree diagram with a preset third symbol: the self-describing file (readme) under the directory "zz-dir-1" can in turn obtain such a tree structure: "|· · readme", see in particular (a) in fig. 8.

Otherwise, that is, in the case that each directory is the last element under the immediately superior directory of each directory, the immediately superior directory and the element to be printed currently may be connected in the tree diagram by using the preset fourth symbol. The "preset fourth symbol" may be the second alignment symbol number: ".

For example, referring back to fig. 8, for the 1.Tcl file below the directory "zz-dir-4", the upper level directory of the "1.Tcl file" is the directory "zz-dir-4", and since the upper level directory "zz-dir-4" is the 7 th element under the direct upper level directory demo of the upper level directory "zz-dir-4", i.e., the upper level directory "zz-dir-4" is the last element under the direct upper level directory demo of the upper level directory "zz-dir-4", the direct upper level directory demo and the element to be printed currently can be connected in the tree diagram with a preset fourth symbol: the 1.Tcl file under the directory "zz-dir-4" can then obtain such a tree structure: ". 1.Tcl", see (B) of FIG. 8.

Alternatively, referring back to FIG. 8, for the self-contained file (readme) below the directory "zz-dir-2-1", there are two upper directories in total, directory "zz-dir-2-1" and directory "zz-dir-2", respectively. For the upper-level directory "zz-dir-2-1", since the upper-level directory "zz-dir-2-1" is the 3 rd element under the direct upper-level directory "zz-dir-2" of the upper-level directory "zz-dir-2-1", that is, the upper-level directory "zz-dir-2-1" is the last element under the direct upper-level directory "zz-dir-2" of the upper-level directory "zz-dir-2-1", the direct upper-level directory "zz-dir-2" and the element to be printed currently can be connected in the tree diagram by using a preset fourth symbol: the self-describing file (readme) under the directory "zz-dir-2-1" can then obtain such a tree structure: ". Cndot. C-readme", see (C1) in FIG. 8.

Further, for the upper level directory "zz-dir-2", since the upper level directory "zz-dir-2" is the 5 th element under the direct upper level directory "remo" of the upper level directory "zz-dir-2", i.e., the upper level directory "zz-dir-2" is not the last element under the direct upper level directory "remo" of the upper level directory "zz-dir-2", the direct upper level directory "remo" and the element to be printed currently can be connected in the tree diagram by using a preset third symbol: the self-describing file (readme) under the directory "zz-dir-2-1" can then obtain such a tree structure: "|··j|j| -readme", see (C2) in fig. 8.

Alternatively, referring back to FIG. 8, for 1.Tcl below the directory "zz-dir-4-1," there are two upper level directories in total, directory "zz-dir-4-1" and directory "zz-dir-4", respectively. Wherein, for the upper-level directory "zz-dir-4-1", since the upper-level directory "zz-dir-4-1" is the 3 rd element under the direct upper-level directory "zz-dir-4" of the upper-level directory "zz-dir-4-1", that is, the upper-level directory "zz-dir-4-1" is not the last element under the direct upper-level directory "zz-dir-4" of the upper-level directory "zz-dir-4-1", the direct upper-level directory "zz-dir-4" and the element to be printed currently can be connected in the tree diagram by using the preset third symbol: the following 1.Tcl of the directory "zz-dir-4-1" may in turn obtain such a tree structure: "|.+ -..+ -. 1.Tcl", see (D1) in FIG. 8.

Further, for the upper level directory "zz-dir-4", since the upper level directory "zz-dir-4" is the 7 th element under the direct upper level directory "remo" of the upper level directory "zz-dir-4", i.e., the upper level directory "zz-dir-4" is the last element under the direct upper level directory "remo" of the upper level directory "zz-dir-4", the direct upper level directory "remo" and the element to be printed currently can be connected in the tree diagram by using a preset fourth symbol: the following 1.Tcl of the directory "zz-dir-4-1" may in turn obtain such a tree structure: "-, the% -1. Tcl", see in particular (D2) in fig. 8.

Therefore, the method and the device can realize the presentation of a test thinking guide graph with clear level and clear level to a user by connecting the elements to be printed currently with the upper-level catalogs of each level by using different types of tree structure connection symbols based on the positions of the elements to be printed currently in the catalogs and the positions of the upper-level catalogs of each level of the elements to be printed currently in the corresponding upper-level catalogs, and facilitate the user to quickly and accurately comb the architecture relations among different catalogs and among files and catalogs.

Hereinafter, a procedure of "branch_sum" and "branch_vline" are described as specific examples. Specifically, when printing the element fn in the specified directory, the format thereof may be " {branch_sum}/>{middle_branch_end}/>{ fn } ", wherein the specific matching manner thereof can be as follows: />

The initial assignment of branch_sum may be null at the target directory level, i.e., when an element of the first level is printed, the branch_sum may be null so that branch_vline is not printed before the corresponding element, and the printing result of the corresponding element may be: "-IJE-{ fn } "is alternatively" - + ">{fn}”。

Illustratively, referring back to FIG. 8, the target directory demo in FIG. 8 is the level 0 element, while the directory "zz-dir-1", directory "zz-dir-2", directory "zz-dir-3", and directory "zz-dir-4" belong to the level 1 element, such that when printing the first level element, branch_sum may be empty, i.e., branch_vline is not printed before the corresponding element, at which time the print result of the corresponding element may be "— - —{ fn } "is alternatively" - + ">{ fn }. For example, the directory "zz-dir-1" may be printed as "-zz-dir-1", the directory "zz-dir-4" may be printed as "-zz-dir-4", and so on.

By "set branch_sum" when printing elements in the second hierarchy "{branch_sum}/>{ branch_vline } ", add branch_sum value +.>{ branch_vline }, so that 1 branch_vline can be printed before the corresponding element, and the result of printing the corresponding element can be "| -v- >{ fn } "is either" |. Cndot. ++ ->{fn}”。

Illustratively, referring back to FIG. 8, the self-describing file (readme), 1.Tcl, directory "zz-dir-2-1" under directory "zz-dir-2" all belong to elements of the second hierarchy, at which point "set branch_sum" may be passed "{branch_sum}/>{ branch_vline } ", add branch_sum value +.>{ branch_vline }, so that 1 branch_vline can be printed before the corresponding element, and the result of printing the corresponding element can be "| -v->{ fn } "is either" |. Cndot. ++ ->{ fn }. For example, the print result of the self-contained file (readme) under the directory "zz-dir-2" may be "|. Readme", the print result of 1.tcl under the directory "zz-dir-2" may be "|. Dir-1. Tcl", and the print result of the lower directory "zz-dir-2-1" of the directory "zz-dir-2" may be "|. Dir-2-1".

In printing the elements in the third hierarchy, the "set branch_sum" can be passed again "{branch_sum}/>{ branch_vline } ", add branch_sum value +.>{ branch_vline }, so that 2 branch_vlines are printed before the corresponding element, at this time, the print result of the corresponding element can the contents are "|··as a->{fn}”、“|·····└──/>{fn}”、“···|··├──/>{fn}”、“···|··└──/>{fn}”、“······└──/>{ fn } ", etc.

Illustratively, referring back to FIG. 8, the self-describing file (readme), 1.Tcl under the directory "zz-dir-2-1" are all elements of the third hierarchy, at this time, the liquid crystal display device, self-describing file (readme) under directory "zz-dir-2-1" the printing result can be "|·······"; 1.Tcl print results under the directory "zz-dir-2-1" can be "|. Cndot. 1. Tcl). Alternatively, the self-contained file (readme) under the directory "zz-dir-4-2" is an element of the third hierarchy, at this time, the print result of the self-contained file (readme) under the directory "zz-dir-4-2" may be ". Cndot.cndot.cndot.cndot.c., -readme". In printing elements in subsequent levels, and so on, no further description is given here.

In the process of recursive printing, when the element of the next hierarchy is backed up to the element of the previous hierarchy, the element of the next hierarchy can be printed by the method of "set branch_sum [ string range ]{branch_sum} 0 end-[string length{branch_vline}]]"decrease the assignment of branch_sum 1 times->{branch_vline}。

Referring back to fig. 7 and 8, fig. 7 and 8 are two examples of the printing result of the tree structure connection symbol. Wherein the example in FIG. 7 mainly shows the case where "branch_sum" is matched with "branch_vline", including "|. Cndot. Of the present invention {fn}”、“|··|··├──/>{fn}”、“|··└──/>{ fn } "and so on; the example in FIG. 8 mainly shows the case where "branch_sum" is matched with "branch_null", including ". Cndot. Is ]>{fn}”、“|··├──/>{fn}”、“···|··├──/>{fn}”、“···└─/>{ fn } ", etc. />

Fig. 9 is a block diagram illustrating a presentation apparatus of a test mind map according to an exemplary embodiment of the present application.

Referring to fig. 9, the test mind map display apparatus 900 may include a first command receiving module 901 and a test mind map display module 902. The first command receiving module 901 is configured to receive a first command input to the terminal tool in the target system. The first command may be used to instruct to print, on the terminal tool, a directory and/or a file under a target directory in a tree diagram form based on a target script, where the target directory may include multiple levels of subdirectories, the target directory and the multiple levels of subdirectories may be created in advance according to a target test item, and a test regression case obtained by testing a test point corresponding to at least one directory may be added under at least one of the target directory and the multiple levels of subdirectories. And, the test mind map display module 902 is configured to call a target script in the target system in response to the first command, so as to obtain and display, on the terminal tool, a tree map corresponding to the target directory as a test mind map of the target test item.

According to an exemplary embodiment of the present application, presentation apparatus 900 may also include other information presentation modules. The other information display module is used for displaying at least one of the self-description files, the number of test points, the number of test regression cases and the directory test state corresponding to each directory in the target directory and the multi-level subdirectory in the test thinking diagram. The self-description file corresponding to any directory may include introduction information, test point information and branch directory information of any directory.

According to an exemplary embodiment of the present application, the other information display module may be further configured to determine, for each first sub-directory, a directory test state of the first sub-directory according to a coincidence condition of a test point included in the self-description file under the first sub-directory and a test point included in the test regression case under the first sub-directory, and may display the directory test state under the first sub-directory. The first subdirectory may be a subdirectory in which no subordinate directory exists in the multi-level subdirectory.

According to an exemplary embodiment of the present application, the other information presentation module may be further configured to determine, for each of the target directory and the second sub-directory, a directory test state of each directory according to a test state of a test point included in the self-explanatory file under each directory and a directory test state of a lower directory of each directory, and may present the directory test state under each directory. The second subdirectory may be a subdirectory in which a subordinate directory exists in the multi-level subdirectory.

According to an exemplary embodiment of the present application, the other information presentation module may be further configured to determine, for each first sub-directory, a number of test points included in the self-contained file under the first sub-directory. The first subdirectory may be a subdirectory in which no subordinate directory exists in the multi-level subdirectory. The number of test points contained in the self-contained file may then be presented under a first sub-list.

According to an exemplary embodiment of the present application, the other information presentation module may be further configured to determine, for each of the target directory and the second sub-directory, a first number of test points included in the self-describing file under each of the target directories. The second subdirectory may be a subdirectory in which a subordinate directory exists in the multi-level subdirectory. Then, a second number of test points contained in the self-contained files of all the lower directories of each directory may be determined. Next, the sum of the first number and the second number may be calculated to obtain the total number of test points. Finally, the total number of test points can be presented under each directory.

According to an exemplary embodiment of the present application, the other information presentation module may be further configured to determine, for each of the target directory and the second sub-directory, a third number of test regression cases under each directory. Then, a fourth number of test regression cases under all the lower level directories of each directory may be determined. Next, the third number and the fourth number may be summed to obtain a total number of test regression cases. Finally, the total number of test regression cases may be presented under each catalog.

According to an exemplary embodiment of the present application, the target script may also be used to generate a target directory and a test progress file corresponding to each directory in the multi-level subdirectory. The test progress file corresponding to any directory is used for indicating the test progress under any directory. Presentation device 900 may also include a second command receiving module and a test progress file printing module. The second command receiving module is used for receiving a second command input into the terminal tool in the target system. The second command may include a path name of a specified directory, where the specified directory may be one of a target directory or a multi-level subdirectory. And the test progress file printing module is used for responding to the second command and printing the content in the test progress file under the appointed directory on the terminal tool.

According to an exemplary embodiment of the present application, the test progress file printing module may be configured to print at least one of the following included in the test progress file under the specified directory on the terminal tool: the number of test points corresponding to the specified directory, the number of test regression cases corresponding to the specified directory, and the percentage between the number of test points which have completed testing among the test points corresponding to the specified directory and the number of all test points corresponding to the specified directory; the method comprises the steps of designating a file test state corresponding to a self-contained file under a catalog, designating a test point which is not started to be tested in a test point contained in the self-contained file under the catalog, and designating a percentage between the number of test points which are tested in the test point contained in the self-contained file under the catalog and the number of all test points contained in the self-contained file.

According to an exemplary embodiment of the present application, presentation apparatus 900 may also include a completion status determination module, a not yet activated test status determination module, and a status under test determination module. The completion state determining module is used for determining that the file test state corresponding to the self-contained file under the appointed directory is a completion state under the condition that all test points contained in the self-contained file under the appointed directory are tested; the test state determination module is used for determining that the file test state corresponding to the self-contained file under the specified directory is the test state which is not started under the condition that the test points contained in the self-contained file under the specified directory are not started; the under-test state determination module is configured to: otherwise, determining the file testing state corresponding to the self-described file under the appointed directory as the state under test.

Additional options may also be included within the first command according to an exemplary embodiment of the present application. Wherein the additional options may include at least one of: the method comprises the steps of displaying a script application manual, displaying a catalog to be displayed, displaying only a catalog level, displaying the catalog level maximally, preventing carrying colors during printing, preventing displaying a test progress file, preventing displaying a self-description file and the test progress file, and preventing reserving the generated test progress file after displaying. The test mind map display module 902 may be further configured to obtain and display, on the terminal tool, a tree map corresponding to the target directory as a test mind map of the target test item according to the additional options included in the first command.

According to an exemplary embodiment of the present application, the test mind map display module 902 may also be configured to print and display a test mind map on a terminal tool according to a default color preset in a target system in a case where an option to prohibit carrying a color when printing is included in the first command; and in the case where the option of prohibiting carrying color at the time of printing is not included in the first command, printing each object based on the display color preset for each object in the target script to display the test mind map on the terminal tool.

According to an exemplary embodiment of the present application, the test mind map display module 902 may be further configured to print the directory and/or the file under the target directory sequentially by using the target directory as a starting point through a recursive traversal manner until the target directory, the multi-level sub-directory, the file under the target directory, and the file under the multi-level sub-directory are traversed. Wherein for each traversal, the following operations may be performed: acquiring the type of the current traversal object; in the case of a file of the type, the current traversal object can be printed based on the preset display color for the file in the target script; under the condition that the type is the directory, the directory test state, the number of test points and the number of test regression cases corresponding to the current traversal object can be obtained. Then, the current traversal object may be printed based on a preset display color for the directory in the target script, and the directory test state, the number of test points, and the number of test regression cases corresponding to the current traversal object may be printed under the current traversal object based on the preset display color for the character string in the target script.

According to an exemplary embodiment of the present application, the display apparatus 900 may further include a judging module, a first executing module, and a second executing module. The judging module is used for judging whether the first command contains the path name of the catalog or not; the first execution module is used for taking a directory corresponding to the path name as a target directory when the first command contains the path name; the second execution module is used for: otherwise, the current working catalog of the target system is taken as the target catalog.

According to an exemplary embodiment of the present application, presentation apparatus 900 may further include a catalog creation module, a self-description file creation module, and a test regression use case addition module. The catalog creation module is used for creating a target catalog and a multi-level subdirectory according to the target test item; the self-describing file creating module is used for creating self-describing files under each of the target directory and the multi-level subdirectory; the test regression use case adding module is used for writing corresponding test points in the target test items in the self-description files under each catalog according to a first preset format, and can add test regression use cases under at least one catalog. The test regression use case can be a test regression use case obtained by testing at least one test point written in the self-description file under at least one directory.

According to an exemplary embodiment of the present application, the test regression use case may include at least one of: the method comprises the steps of compiling at least one test point according to a second preset format, verifying data used for verifying the compiled at least one test point, simulating manual operation steps used for verifying the compiled at least one test point, expected results, verifying results, indication information of whether the expected results are matched with the verifying results, and conclusion information whether the compiled at least one test point is verified to pass or not; the verification result is obtained after the simulation manual operation step is executed based on the verification data; the desired result is an accurate result that should be obtained after performing the simulated manual operation step based on the verification data.

According to an exemplary embodiment of the present application, the test mind map display module 902 may also be configured to determine, in a case where an element to be printed is an element directly included in the target directory, whether the element to be printed is a last element in the target directory. Under the condition that the element to be printed is not the last element in the target catalog, the target catalog and the element to be printed are connected in the dendrogram by utilizing a preset first symbol; otherwise, the target directory and the element to be printed currently can be connected in the dendrogram by using a preset second symbol.

According to an exemplary embodiment of the present application, the test mind map display module 902 may be further configured to determine, for each directory in the hierarchical upper directories of the element to be printed, whether each directory is the last element under the immediately upper directory of each directory, in a case where the element to be printed is the element indirectly included in the target directory. Under the condition that each catalog is not the last element under the directly upper-level catalog of each catalog, the directly upper-level catalog and the element to be printed currently can be connected in the dendrogram by utilizing a preset third symbol; otherwise, the direct superordinate directory and the element to be printed currently can be connected in the dendrogram by using a preset fourth symbol.

Fig. 10 is a block diagram illustrating an electronic device 1000 according to an exemplary embodiment of the present application.

Referring to fig. 10, an electronic device 1000 includes at least one memory 1001 and at least one processor 1002, the at least one memory 1001 having instructions stored therein that, when executed by the at least one processor 1002, perform a presentation method of a test mind map according to an exemplary embodiment of the present application.

By way of example, the electronic device 1000 may be a PC computer, tablet device, personal digital assistant, smart phone, or other device capable of executing the instructions described above. Here, the electronic device 1000 is not necessarily a single electronic device, but may be any apparatus or a collection of circuits capable of executing the above-described instructions (or instruction sets) individually or in combination. The electronic device 1000 may also be part of an integrated control system or system manager, or may be configured as a portable electronic device that interfaces with either locally or remotely (e.g., via wireless transmission).

In electronic device 1000, processor 1002 may include a Central Processing Unit (CPU), a Graphics Processor (GPU), a programmable logic device, a special purpose processor system, a microcontroller, or a microprocessor. By way of example, and not limitation, processors may also include analog processors, digital processors, microprocessors, multi-core processors, processor arrays, network processors, and the like.

The processor 1002 may execute instructions or code stored in the memory 1001, wherein the memory 1001 may also store data. The instructions and data may also be transmitted and received over a network via a network interface device, which may employ any known transmission protocol.

The memory 1001 may be integrated with the processor 1002, for example, RAM or flash memory disposed within an integrated circuit microprocessor or the like. In addition, the memory 1001 may include a separate device, such as an external disk drive, a storage array, or other storage device that may be used by any database system. The memory 1001 and the processor 1002 may be operatively coupled or may communicate with each other, for example, through an I/O port, a network connection, etc., so that the processor 1002 can read files stored in the memory.

In addition, the electronic device 1000 may also include a video display (such as a liquid crystal display) and a user interaction interface (such as a keyboard, mouse, touch input device, etc.). All components of the electronic device 1000 may be connected to each other via buses and/or networks.

According to an exemplary embodiment of the present application, there may also be provided a computer-readable storage medium, which when executed by a processor of an electronic device, enables the electronic device to perform the above-described presentation method of a test mind map. Examples of the computer readable storage medium herein include: read-only memory (ROM), random-access programmable read-only memory (PROM), electrically erasable programmable read-only memory (EEPROM), random-access memory (RAM), dynamic random-access memory (DRAM), static random-access memory (SRAM), flash memory, nonvolatile memory, CD-ROM, CD-R, CD + R, CD-RW, CD+RW, DVD-ROM, DVD-R, DVD + R, DVD-RW, DVD+RW, DVD-RAM, BD-ROM, BD-R, BD-R LTH, BD-RE, blu-ray or optical disk storage, hard Disk Drives (HDD), solid State Disks (SSD), card memory (such as multimedia cards, secure Digital (SD) cards or ultra-fast digital (XD) cards), magnetic tape, floppy disks, magneto-optical data storage, hard disks, solid state disks, and any other means configured to store computer programs and any associated data, data files and data structures in a non-transitory manner and to provide the computer programs and any associated data, data files and data structures to a processor or computer to enable the processor or computer to execute the programs. The computer programs in the computer readable storage media described above can be run in an environment deployed in a computer device, such as a client, host, proxy device, server, etc., and further, in one example, the computer programs and any associated data, data files, and data structures are distributed across networked computer systems such that the computer programs and any associated data, data files, and data structures are stored, accessed, and executed in a distributed fashion by one or more processors or computers.

According to the method, the device, the electronic equipment and the storage medium for displaying the test thinking guide graph, which are provided by the application, after the test points are tested and the test regression use cases are obtained, the test regression use cases can be added to the directory containing the corresponding test points. Furthermore, the test can be targeted to the test points contained in the self-description file under the specific directory, and the corresponding test regression use case can be added to the directory containing the corresponding test points, and the directory is contained in the test thinking diagram. Therefore, the application integrates the test regression use cases on the mind map, thereby avoiding the cross use of a plurality of software, reducing the carding difficulty of the corresponding relation between the test mind map and the test regression use cases and being beneficial to the preservation and maintenance of test data.

Furthermore, the test regression use case is controlled to contain the tested test points, so that the follow-up test regression use case is convenient to know which test points are tested in time based on the test points contained in the test regression use case, and the test progress can be conveniently and rapidly counted; further, the regression use case through control test comprises verification data, a simulated manual operation step, an expected result and a verification result; the indication information of whether the expected result is matched with the verification result or not and the conclusion information of whether the verification of the test point is passed or not are equivalent to the detailed record of the complete process of testing the test point, so that the follow-up leak detection and error correction are facilitated.

Further, the user can decide whether to designate the corresponding catalogue in the first command according to the self-requirement, namely, the user can decide which catalogue to display the test mind map according to the self-requirement, and the autonomy and flexibility of displaying the test mind map are better. Furthermore, under the condition that the corresponding catalogue is not designated in the first command, the terminal can automatically determine the current working catalogue as the catalogue of the test mind act to be displayed, so that the operation steps of manually designating the catalogue by a user are saved, and the complexity of determining the catalogue of the test mind act to be displayed is reduced.

Furthermore, at least one of the number of self-description files and test points corresponding to each catalog, the number of test regression cases and the catalog test state is displayed in the test thinking chart, so that the user can conveniently and intuitively and clearly know the test tasks of each catalog and the test progress speed, and the user can conveniently and macroscopically and roughly control the whole test condition.

Further, since the test regression use case is obtained by testing the test point corresponding to the catalog, once a certain test point contained in a certain test regression use case coincides with a certain test point contained in the self-description file under the catalog, the test point contained in the self-description file is described as being tested. Therefore, whether all the test points corresponding to the directory are tested can be determined based on the coincidence condition of the test points contained in the self-describing file under the directory and the test points contained in the test regression use case under the directory, namely, the directory test state can be determined based on the coincidence condition of the test points, and the accuracy of the determined directory test state can be ensured.

Further, a directory may be a lower directory of another directory only if it has a relatively close relationship with the other directory. Therefore, in determining the directory test state of the directory for the directory where the subordinate directory exists, it is necessary to consider the directory test states of all the subordinate directories of the directory in addition to the test states of the test points in the self-contained files under the directory itself. Therefore, the user can generally judge what test state the lower-level catalogue of the catalogue is in based on the catalogue test state of a certain catalogue, and the user can intuitively and clearly know what test state the lower-level catalogue of the current catalogue is in. In addition, when determining the number of test points corresponding to a directory in which a lower-level directory exists, it is necessary to consider the number of test points included in the self-contained file of all lower-level directories of the directory in addition to the number of test points in the self-contained file of the directory itself. Therefore, a user can generally judge how many test points are approximately contained in the self-contained file of the lower-level directory of the directory only by the number of the test points corresponding to a certain directory, so that the user can intuitively and clearly know how many test points correspond to the lower-level directory of the current directory. And, for the directory where the lower-level directory exists, when determining the number of test regression cases corresponding to the directory, the number of test regression cases under all the lower-level directories of the directory needs to be considered in addition to the number of test regression cases under the directory itself. Therefore, the user can generally judge how many test regression cases are contained in the lower-level catalogue of the catalogue based on the number of the test regression cases corresponding to a certain catalogue, so that the user can intuitively and clearly know how many test regression cases correspond to the lower-level catalogue of the current catalogue.

Furthermore, the user can determine which additional options are contained in the first command according to the self-requirement, and further can realize corresponding functions when the test mind map is displayed, namely, the user can autonomously determine why the test mind map is specifically displayed, and the autonomy and flexibility of displaying the test mind map are better.

Furthermore, the user can preset the values of various color variables in the showmindmap script according to the self requirement, further different objects can be printed by using different colors, and the aim of presenting a test thinking graph with clear boundaries and clear framework among different types of objects to the user can be achieved, so that the user can quickly and accurately know the organization framework and composition of the whole test thinking graph.

Further, the user can decide to display the content of the test progress file under which directory according to the self requirement, and the autonomy and flexibility of the test progress corresponding to the display directory are good.

Furthermore, by setting a plurality of contents related to test points and test regression cases in the test progress file, a user can clearly and comprehensively understand the test progress under the corresponding directory, and can control the test conditions under the corresponding directory in an omnibearing manner.

Further, by printing each directory and/or file in a recursive traversal manner, any directory or file can be prevented from being missed. In addition, by presetting the display colors of different types of objects in the showmindmap script, a test thinking guide diagram with clear boundaries and clear framework among different types of objects can be presented to a user, so that the user can quickly and accurately know the organization framework, component composition and test condition of the whole test thinking guide diagram.

Furthermore, the current element to be printed and the affiliated catalog are connected by using different types of tree structure connection symbols based on the position of the current element to be printed in the affiliated catalog, and the current element to be printed and the affiliated catalog are connected by using different types of tree structure connection symbols based on the position of the current element to be printed in the affiliated catalog and the position of each hierarchical upper catalog of the current element to be printed in the corresponding direct upper catalog, so that a test thinking diagram with distinct and clear grades can be presented to a user, and the user can conveniently and rapidly and accurately comb the architecture relations among different catalogs and among files and catalogs.

Other embodiments of the application will be apparent to those skilled in the art from consideration of the specification and practice of the application disclosed herein. This application is intended to cover any variations, uses, or adaptations of the application following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the application pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.

It is to be understood that the application is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the application is limited only by the appended claims.

Claims

1. The display method of the test thinking guide graph is characterized by comprising the following steps of:

receiving a first command input into a terminal tool in a target system, wherein the first command is used for indicating that a target directory and/or a file under a target directory are printed in a tree diagram form on the terminal tool based on a target script, the target directory comprises a plurality of levels of subdirectories, the target directory and the levels of subdirectories are pre-created according to target test items, and a test regression use case obtained by testing a test point corresponding to at least one directory is added under at least one directory in the target directory and the levels of subdirectories;

And responding to the first command, calling the target script in the target system to acquire and display a tree diagram corresponding to the target catalog on the terminal tool as a test thinking guide diagram of the target test item.

2. The display method of claim 1, wherein the display method further comprises:

displaying at least one of the self-contained files, the number of test points, the number of test regression cases and the directory test states corresponding to the target directory and each directory in the multi-level subdirectory in the test thinking guide graph;

the self-contained file corresponding to any directory contains introduction information, test point information and branch directory information of the any directory.

3. The display method according to claim 2, wherein displaying at least one of the self-contained files, the number of test points, the number of test regression cases, and the directory test status corresponding to each directory in the target directory and the multi-level subdirectory in the test mind map includes:

and aiming at each first subdirectory, determining the directory test state of the first subdirectory according to the superposition condition of the test points contained in the self-contained file under the first subdirectory and the test points contained in the test regression case under the first subdirectory, and displaying the directory test state under the first subdirectory, wherein the first subdirectory is the subdirectory without the lower-level directory in the multi-level subdirectory.

4. The display method according to claim 2, wherein displaying at least one of the self-contained files, the number of test points, the number of test regression cases, and the directory test status corresponding to each directory in the target directory and the multi-level subdirectory in the test mind map includes:

and aiming at each directory in the target directory and the second subdirectory, determining the directory test state of each directory according to the test state of the test point contained in the self-contained file under each directory and the directory test state of the lower-level directory of each directory, and displaying the directory test state under each directory, wherein the second subdirectory is the subdirectory with the lower-level directory in the multi-level subdirectory.

5. The display method according to claim 2, wherein displaying at least one of the self-contained files, the number of test points, the number of test regression cases, and the directory test status corresponding to each directory in the target directory and the multi-level subdirectory in the test mind map includes:

determining the number of test points contained in the self-contained file under the first subdirectory for each first subdirectory, wherein the first subdirectory is a subdirectory in which no subordinate directory exists in the multi-level subdirectory;

And displaying the number of the test points contained in the self-contained file under the first sub-directory.

6. The display method according to claim 2, wherein displaying at least one of the self-contained files, the number of test points, the number of test regression cases, and the directory test status corresponding to each directory in the target directory and the multi-level subdirectory in the test mind map includes:

determining a first number of test points contained in the self-contained file under each directory for each directory in the target directory and a second sub-directory, wherein the second sub-directory is a sub-directory with a lower-level directory in the multi-level sub-directory;

determining a second number of test points contained in the self-contained files of all subordinate directories of each directory;

calculating the sum of the first quantity and the second quantity to obtain the total quantity of test points;

the total number of test points is shown under each directory.

7. The display method according to claim 2, wherein displaying at least one of the self-contained files, the number of test points, the number of test regression cases, and the directory test status corresponding to each directory in the target directory and the multi-level subdirectory in the test mind map includes:

Determining a third number of test regression cases under each directory for each of the target directory and the second subdirectory;

determining a fourth number of test regression cases under all lower-level directories of each directory;

calculating the sum of the third quantity and the fourth quantity to obtain the total quantity of the test regression cases;

the total number of test regression cases is shown under each catalog.

8. The display method of claim 1, wherein the target script is further configured to generate a test progress file corresponding to each of the target directory and the multi-level subdirectory, wherein the test progress file corresponding to any directory is used to indicate a test progress under any directory;

wherein after the target script is invoked in the target system, the exhibition method further comprises:

receiving a second command input into the terminal tool in the target system, wherein the second command comprises a path name of a specified directory, and the specified directory is one of the target directory or the multi-level subdirectory;

and responding to the second command, and printing the content in the test progress file under the specified directory on the terminal tool.

9. The display method according to claim 8, wherein the printing of the content in the test progress file under the specified directory on the terminal tool includes:

printing at least one of the following items contained in the test progress file under the specified directory on the terminal tool:

the number of test points corresponding to the specified directory, the number of test regression cases corresponding to the specified directory, and the percentage between the number of test points which have been tested in the test points corresponding to the specified directory and the number of all test points corresponding to the specified directory; the method comprises the steps of determining a file test state corresponding to a self-contained file under a specified directory, determining a test point which is not started to be tested in test points contained in the self-contained file under the specified directory, and determining the percentage between the number of test points which are tested in the test points contained in the self-contained file under the specified directory and the number of all test points contained in the self-contained file.

10. The display method of claim 9, wherein the display method further comprises:

under the condition that test points contained in the self-contained file under the specified directory are all tested, determining a file test state corresponding to the self-contained file under the specified directory as a finished state;

Under the condition that test points contained in the self-contained files under the specified directory are not started, determining that the file test state corresponding to the self-contained files under the specified directory is a not-started test state;

otherwise, determining the file testing state corresponding to the self-describing file under the appointed directory as the state under test.

11. The display method of claim 1, wherein an additional option is further included within the first command, wherein the additional option includes at least one of:

the method comprises the steps of displaying a manual of a script, displaying a catalog to be displayed, displaying only a catalog level, displaying a maximum catalog level, prohibiting carrying color during printing, prohibiting displaying a test progress file, prohibiting displaying a self-description file and a test progress file, and prohibiting reserving the generated test progress file after displaying;

the step of obtaining and displaying the tree diagram corresponding to the target catalog on the terminal tool as a test thinking guide diagram of the target test item comprises the following steps:

and according to the additional options contained in the first command, acquiring and displaying a tree diagram corresponding to the target catalog on the terminal tool as a test thinking guide diagram of the target test item.

12. The display method as set forth in claim 11, wherein the obtaining and displaying, according to the additional options included in the first command, the tree diagram corresponding to the target directory on the terminal tool as the test mind map of the target test item includes:

under the condition that the first command contains the option of prohibiting carrying color during printing, printing according to a default color preset in the target system and displaying the test thinking guide graph on the terminal tool;

and under the condition that the option of prohibiting carrying color during printing is not included in the first command, printing each object based on the preset display color for each object in the target script so as to display the test mind map on the terminal tool.

13. The display method according to claim 1, wherein the obtaining and displaying, on the terminal tool, the tree diagram corresponding to the target directory as the test mind map of the target test item includes:

sequentially printing the catalogs and/or files under the target catalogs by taking the target catalogs as a starting point in a recursion traversing manner until the target catalogs, the multi-stage subdirectories, the files under the target catalogs and the files under the multi-stage subdirectories are traversed;

Wherein for each traversal, the following is performed:

acquiring the type of the current traversal object;

if the type is a file, printing a current traversal object based on a preset display color aiming at the file in the target script;

under the condition that the type is a directory, acquiring a directory test state, the number of test points and the number of test regression cases corresponding to the current traversal object;

and printing a current traversal object based on the display color preset for the catalogue in the target script, and printing the catalogue test state, the number of test points and the number of test regression cases corresponding to the current traversal object under the current traversal object based on the display color preset for the character string in the target script.

14. The presentation method of claim 1, wherein after receiving the first command input to the end tool within the target system, the presentation method further comprises:

judging whether the first command contains the path name of the catalog or not;

taking a directory corresponding to the path name as the target directory when the path name is contained in the first command;

Otherwise, the current working catalog of the target system is used as the target catalog.

15. The presentation method of claim 1, wherein prior to receiving the first command input to the end tool within the target system, the presentation method further comprises:

creating the target catalog and the multi-level subdirectory according to the target test item;

creating a self-contained file under each of the target directory and the multi-level subdirectory;

writing corresponding test points in the target test items in the self-contained files under each directory according to a first preset format, and adding test regression cases under the at least one directory, wherein the test regression cases are test regression cases obtained by testing at least one test point written in the self-contained files under the at least one directory.

16. The display method of claim 15, wherein the test regression use case comprises at least one of:

the written at least one test point specified according to a second preset format is used for verifying verification data of the written at least one test point, a simulation manual operation step for verifying the written at least one test point, an expected result, a verification result, indication information of whether the expected result is matched with the verification result or not, and conclusion information of whether the written at least one test point passes verification or not;

Wherein the verification result is a result obtained after the step of simulating manual operation is performed based on the verification data;

the expected result is an accurate result that should be obtained after performing the simulated manual operation step based on the verification data.

17. The display method according to claim 1, wherein the obtaining and displaying, on the terminal tool, the tree diagram corresponding to the target directory as the test mind map of the target test item includes:

judging whether the element to be printed is the last element in the target catalog or not under the condition that the element to be printed is the element directly contained in the target catalog;

under the condition that the element to be printed is not the last element under the target directory, connecting the target directory and the element to be printed in the tree diagram by using a preset first symbol;

otherwise, connecting the target directory with the elements to be printed currently in the tree diagram by using a preset second symbol.

18. The display method according to claim 1, wherein the obtaining and displaying, on the terminal tool, the tree diagram corresponding to the target directory as the test mind map of the target test item includes:

Under the condition that the element to be printed is indirectly contained in the target catalog, judging whether each catalog is the last element under the directly upper catalog of each catalog aiming at each catalog in the upper catalog of each hierarchy of the element to be printed;

under the condition that each catalog is not the last element under the directly upper-level catalog of each catalog, connecting the directly upper-level catalog with the element to be printed currently in the dendrogram by utilizing a preset third symbol;

otherwise, connecting the directly superior directory with the element to be printed currently in the tree diagram by using a preset fourth symbol.

19. A display device for a test mind map, comprising:

a first command receiving module configured to receive a first command input to a terminal tool in a target system, wherein the first command is used for indicating that a target directory and/or a file under a target directory are printed in a tree diagram form on the terminal tool based on a target script, the target directory comprises a plurality of levels of subdirectories, the target directory and the levels of subdirectories thereof are pre-created according to target test items, and a test regression case obtained by testing a test point corresponding to at least one directory is added under at least one directory in the target directory and the levels of subdirectories;

And the test thinking diagram display module is configured to respond to the first command and call the target script in the target system so as to acquire and display a tree diagram corresponding to the target catalog on the terminal tool as a test thinking diagram of the target test item.

20. An electronic device, comprising:

a processor;

a memory for storing the processor-executable instructions;

wherein the processor is configured to execute the instructions to implement the method of presentation of a test mind map as claimed in any one of claims 1 to 18.

21. A computer readable storage medium, wherein instructions in the computer readable storage medium, when executed by a processor of an electronic device, enable the electronic device to perform the method of presentation of a test mind map as claimed in any one of claims 1 to 18.