Test case life cycle iteration management method and system and medium

Abstract

The present disclosure provides a test case life cycle iteration management method and system, characterized in that the method comprises the following steps: writing test cases according to a mind map document template; batch importing the written test cases based on the mind map document template; storing the imported test cases and marking them, wherein the marking comprises marking the test cases as manual test cases; and establishing automated test cases and associating the automated test cases with the manual test cases.

Description

Technical Field

[0001] This invention relates to the field of software testing technology, and more specifically to a test case lifecycle iteration management method and system, as well as an associated computer-readable storage medium. Background Technology

[0002] Currently, enterprises have numerous software business services, and these services iterate rapidly. Traditional test case management systems require manual input of test cases, which is time-consuming both in writing and inputting them, and is no longer sufficient to meet the timeliness requirements of rapid iteration. To adapt to the fast iteration pace, document-based test case writing methods have become more popular, such as using software like Excel and X-mind. However, while simplifying test case creation, iterative management of test cases for business scenarios becomes difficult. Software testing often faces problems such as lack of test case management and scattered storage of test cases leading to test case loss. When faced with a system architecture redesign even if the business scenario remains unchanged, regression test cases need to be rewritten, which may even lead to omissions and potential online incidents. Summary of the Invention

[0003] Therefore, this invention proposes a test case lifecycle iteration management method, system, and medium for test case management, thereby assisting in better tracking the management and iteration of test cases.

[0004] According to one aspect of the present invention, a test case lifecycle iteration management method is provided, characterized in that the method includes the following steps: writing test cases according to a mind map document template; importing the written test cases in batches based on the mind map document template; storing the imported test cases and marking them, wherein marking includes marking the test cases as manual test cases; and creating automated test cases and associating the automated test cases with the manual test cases.

[0005] Furthermore, according to one or more embodiments of one aspect of the present invention, the method further includes adding manual test cases associated with the automated test cases.

[0006] Furthermore, according to one or more embodiments of one aspect of the present invention, the method further includes discarding manual test cases associated with the automated test cases.

[0007] Furthermore, according to one or more embodiments of one aspect of the present invention, the method further includes updating the association between the automated test cases and the manual test cases by adding or discarding manual test cases associated with the automated test cases.

[0008] Furthermore, according to one or more embodiments of one aspect of the present invention, the association is to use the number of the automated test case as a prefix of the number of the associated manual test case.

[0009] Furthermore, according to one or more embodiments of one aspect of the present invention, the method further includes labeling the test cases as automated test cases and manual test cases by assigning "automated" and "manual" labels to the test cases.

[0010] Furthermore, according to one or more embodiments of one aspect of the present invention, the method further includes marking the test cases as custom test cases by assigning custom tags to the test cases.

[0011] Furthermore, according to one or more embodiments of one aspect of the present invention, the custom label includes one or more of the following labels: "automation", "manual", "API", "Web", "iOS", "Android", "implemented", and "not implemented".

[0012] Furthermore, according to one or more embodiments of one aspect of the present invention, the method further includes checking the tags and associations of the test cases.

[0013] Furthermore, according to one or more embodiments of one aspect of the present invention, the method further includes reporting the tags and associations of the imported test cases via push notifications.

[0014] Furthermore, according to one or more embodiments of one aspect of the present invention, the method further includes statistically analyzing one or more of the following data: the number of imported test cases, labels, type distribution, and associations.

[0015] According to another aspect of the present invention, a test case lifecycle iteration management system is provided, the system comprising: a mind map document module configured to provide mind map document templates for writing test cases; a test case analysis module configured to batch import written test cases based on the mind map document templates; a test case management module configured to store and mark the imported test cases, wherein marking includes marking the test cases as manual test cases; and the test case management module is further configured to create automated test cases and associate the automated test cases with the manual test cases.

[0016] Furthermore, according to one or more embodiments of another aspect of the present invention, the test case management module is configured to add manual test cases associated with the automated test cases.

[0017] Furthermore, according to one or more embodiments of another aspect of the present invention, the test case management module is configured to discard manual test cases associated with the automated test cases.

[0018] Furthermore, according to one or more embodiments of another aspect of the present invention, the test case management module is configured to update the association between the automated test cases and the manual test cases by adding or discarding manual test cases associated with the automated test cases.

[0019] Furthermore, according to one or more embodiments of another aspect of the invention, the association is to use the number of the automated test case as a prefix of the number of the associated manual test case.

[0020] Furthermore, according to one or more embodiments of another aspect of the present invention, the test case management module is configured to mark the test cases as automated test cases and manual test cases by labeling the test cases with "automated" and "manual" tags.

[0021] Furthermore, according to one or more embodiments of another aspect of the present invention, the test case management module is configured to mark the test cases as custom test cases by assigning custom tags to the test cases.

[0022] Furthermore, according to one or more embodiments of another aspect of the present invention, the custom label includes one or more of the following labels: "automation", "manual", "API", "Web", "iOS", "Android", "implemented", and "not implemented".

[0023] Furthermore, according to one or more embodiments of another aspect of the present invention, the test case analysis module is configured to examine the tags and associations of the test cases.

[0024] Furthermore, according to one or more embodiments of another aspect of the present invention, the test case analysis module is configured to report the tags and associations of imported test cases via push notifications.

[0025] Furthermore, according to one or more embodiments of another aspect of the present invention, the test case analysis module is configured to statistically analyze one or more of the following data: the number of imported test cases, tags, type distribution, and associations.

[0026] The present invention also provides a computer-readable storage medium storing instructions, characterized in that, when the instructions are executed by a processor, the processor performs the method as described above.

[0027] Compared to existing technologies, the method and system provided by this invention can batch edit and save multiple test cases, and dynamically manage multiple test cases by using automated test cases. Simultaneously, this invention can also customize the display of test cases and show related information, such as the number of manual test cases, the number of automated test cases, their proportional distribution, module test case distribution, front-end test case distribution, and interface test case distribution. It can also display relevant information such as the test case's "name, business line, and description," thereby enabling users to gain a comprehensive understanding of a project from the perspective of test cases. Attached Figure Description

[0028] Figure 1 A block diagram of a test case lifecycle iteration system 1000 according to an embodiment of the present invention is shown.

[0029] Figure 2 A flowchart of a test case lifecycle iteration method 2000 according to an embodiment of the present invention is shown.

[0030] Figure 3 A flowchart of a test case lifecycle iteration method 3000 according to an embodiment of the present invention is shown.

[0031] Figure 4 A block diagram of a test case lifecycle iteration system 4000 according to an embodiment of the present invention is shown.

[0032] Figure 5 A computer device is shown that illustrates a test case lifecycle iteration method according to an embodiment of the present invention. Detailed Implementation

[0033] The following is a detailed description of the test case lifecycle iteration management method and system according to the present invention, with reference to the accompanying drawings. It should be noted that the specific embodiments described below are exemplary and not limiting, intended to provide a basic understanding of the invention, and not intended to identify key or decisive elements of the invention or limit the scope of protection.

[0034] The invention is described below with reference to block diagrams, diagrams, and / or flowcharts illustrating methods and apparatus according to embodiments of the invention. It will be understood that each block of these block diagrams and / or diagrams, and combinations thereof, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to form a machine, such that these instructions, executable by the processor of the computer or other programmable data processing apparatus, create components for implementing the functions / operations specified in these block diagrams and / or diagrams and / or one or more block diagrams.

[0035] These computer program instructions may be stored in a computer-readable storage medium, which may instruct a computer or other programmable processor to perform functions in a particular manner, such that the instructions stored in the computer-readable storage medium constitute an instruction set comprising one or more boxes of an implementation flowchart and / or block diagram that specify the functions / operations.

[0036] These computer program instructions can be loaded onto a computer or other programmable data processor to cause a series of operational steps to be executed on the computer or other programmable processor, thereby constituting a computer-implemented process, such that these instructions, which execute on the computer or other programmable data processor, provide steps for implementing the functions or operations specified in one or more boxes of this flowchart and / or block diagram. It should also be noted that in some alternative implementations, the functions / operations shown in the boxes may not occur in the order shown in the flowchart. For example, two boxes shown sequentially may actually be executed substantially simultaneously, or these boxes may sometimes be executed in reverse order, depending on the functions / operations involved.

[0037] This invention provides a method and system for iterative management of the test case lifecycle. It combines a mind mapping module, a test case analysis module, and a test case management module to comprehensively manage and analyze test cases throughout their lifecycle, thus avoiding the problems encountered in existing test case management technologies. Specifically, the mind mapping module can be any software or system commonly used in the field for creating mind maps, UML diagrams, architecture diagrams, topology diagrams, flowcharts, business process diagrams, and other mind maps, such as GetMind or MindMaster. The test case analysis module can be software or systems commonly used in the data analysis field, such as Excel or SPSS, or dedicated data analysis code written in languages ​​such as R or Python. The test case management module can be commonly used test case, project management, and process management software and related plugins, such as Jira Xray. The test case lifecycle iterative management method and system provided by this invention can realize test case inspection, automated and manual test case management, and correlation operations. Based on these operations, it can achieve iterative management of test cases, enabling users to obtain a better connection and organization of test cases at every stage of using and writing test cases. It should be noted that, in the context of this invention, association can refer to the action of associating feature A with feature B, or to the associated relationship or relationship generated through the action of associating.

[0038] The test case lifecycle iteration management method and system provided by this invention utilizes a mind map document module to quickly write test cases using mind map document templates within the test case iteration cycle. Editing test cases using mind map document templates enables rapid interaction and inspection with business / product / development processes. The test case analysis module can import multiple test cases written using the mind map document module into a test case management module (such as Jira Xray) for management and analysis. Test cases imported into the test case management module are set as manual test cases by default, and users can use the test case management module to create automated test cases, which can be associated with manual test cases. Associated manual test cases can be added or discarded, thus updating and iterating the manual test cases. Automated and manual test cases can be linked using a Link, specifically using the automated test case number as a prefix to the manual test case number. Additionally, other custom tags can be used to mark test cases in the test case management system for managing and statistically analyzing various data, including: test case type, test case coverage, number of manual test cases, number of automated test cases, test case ratio distribution, test case distribution, front-end test case distribution, and test case interface test case distribution, etc. The methods and systems can also display relevant information such as "name, business line, description, and relationship" of test cases, thereby enabling statistical analysis of test cases from multiple dimensions.

[0039] The test cases involved in this invention can be any type of test case commonly used in the art, such as test case titles, test case conditions, operation steps, expected results, etc. A test case may contain multiple titles, conditions, steps, and results.

[0040] Figure 1 A block diagram of a test case lifecycle iteration system 1000 according to an embodiment of the present invention is shown. Figure 1 As shown, the test case lifecycle iteration system 1000 includes three modules: a mind map document module 101, configured to provide mind map document templates for writing test cases; a test case analysis module 102, configured to batch import written test cases to a test case management module based on the mind map document templates; and a test case management module 103, configured to store and mark the imported test cases, including marking the test cases as manual test cases; the test case management module 103 is also configured to create automated test cases and associate the automated test cases with the manual test cases. Figure 1As shown, users can edit the mind map document module 101 to edit test cases in the form of mind map documents. Specifically, users can edit multiple test cases in the form of mind map documents. Test cases edited in this way can have hierarchical or parallel relationships according to project needs, thus reflecting the relationship between project requirements and test cases. Users can send the edited test cases (in the form of mind map documents) to the test case analysis module 102. The test case analysis module 102 can batch import multiple test cases into the test case management module 103 (such as Jira Xray). After being imported into the test case management module 103, the multiple test cases associated with the mind map documents will be stored as parallel scattered test cases for processing by the test case management module 103. This method enables the batch import of multiple test cases.

[0041] Test cases imported in this way will be marked as manual test cases by default in the test case management module 103. Users can also add test cases to the test case management module 103 one by one and add custom test case tags. Test case tags can include one or more of the following tags: "Automation", "Manual", "API", "Web", "iOS", "Android", "Implemented", "Not Implemented", and any other tags that may need to be categorized in the project. After adding tags, users can categorize test cases in the test case management module 103, for example, marking manually created test cases as automated test cases with the "Automation" tag or marking test cases as "iOS" test cases. Users can also associate tagged test cases, for example, associating automated test cases with previously imported manual test cases, thereby establishing a 1:N test case relationship network. Specifically, an automated test case can be associated with N (N is a natural number greater than 0) manual test cases, while a manual test case can only be associated with 1 automated test case. Association can be achieved by editing the numbers of automated test cases within the test case management module 103 (e.g., Jira business numbers) as prefixes to manual test cases. Association can also be accomplished through other methods commonly used in the field. After associating automated and manual test cases, the test case analysis module 102 can extract the relationships between test cases and visualize them for the user, allowing the user to observe the relationships between test cases in the project. The test case analysis module 102 can also synchronize other tags added by the user within the test case management module 103 and extract the tags attached to test cases, thereby dynamically displaying to the user the types of test cases in the project, test case coverage, number of manual test cases, number of automated test cases, test case ratio distribution, test case distribution, front-end test case distribution, and test case interface test case distribution. The test case analysis module can also display relevant information such as test case "name, business line, description, and association relationship," enabling multi-dimensional statistical analysis of test cases.

[0042] As described above, by tagging and associating test cases within the test case management module 103, users can iteratively update the relationship between automated test cases and manual test cases. Figure 2 A flowchart of a test case lifecycle iteration method 2000 according to an embodiment of the present invention is shown. Figure 2As shown, in step S201, the user can create a new automated test case in the test case management module and associate it with two manual test cases, for example, manual test case 1 and manual test case 2. In step S202, the user can add a new associated manual test case, for example, associating the automated test case with a new manual test case 3, thus adding a new associated manual test case. In step S203, the user can update the manual test cases 2 and 3 associated with the automated test case to other manual test cases, for example, manual test case 4 and manual test case 5. Similarly, the user can also discard associated manual test cases, for example, discarding manual test case 4. Finally, through update iterations, the automated test case is associated with manual test case 1 and manual test case 5. All the above operations and relationships can be visualized to the user through the test case analysis module, allowing the user to observe changes in test cases and dynamically adjust test cases according to project requirements, avoiding the related problems encountered in test case management in the prior art.

[0043] Through the above operations, users can use the system and method of this invention to add test cases, classify test case tags, manually / automatically mark test cases, associate test cases, update test cases, iterate test cases, and discard test cases. Based on the above operations, users can use the test case analysis module to periodically check abnormal test case data in the test case management module, eliminate dirty data that does not conform to the management relationship, supplement test case data, and correct erroneous test case relationships or data.

[0044] The mind map document module provides users with a way to create test cases in batches during the integration testing phase, allowing for the creation of multiple related test cases for a single project. Mind map document templates can be customized and developed to meet specific needs.

[0045] As mentioned above, users can import test cases into the test case management module through the test case analysis module, thereby generating multiple manual test cases within the test case management module. These test cases can also be customized into different types such as "API" test cases, "web" test cases, "iOS" test cases, and "Android" test cases, and are associated with each other. The tag association method provides self-service combination and update. While ensuring a good user experience for quickly creating test cases, it also simultaneously and quickly realizes the storage and classification of test cases.

[0046] As described above, when creating automated test cases, users set the "Automated" tag in the test case management module and associate the automated test cases with 1 to N manual test cases, thus establishing a relationship network between automated and manual test cases. Simultaneously, the test case number in the automated test case is used as a prefix for the manual test case number. The system provided by this invention supports periodically checking whether the prefix of the number in the automated test case is consistent with the associated manual test case data. If there is a discrepancy, the system can remind the user to update the relationship via message push. The system can also periodically synchronize the information and relationships of all test cases within the test case management system, and an appropriate synchronization update mechanism can be set according to the estimated test case data volume level. Furthermore, users can also update the automated test cases. The updated data will be synchronized to the system via scheduled tasks. By updating and discarding unorganized test cases and their directory structure, the system achieves timely reminders to users to complete the organization and archiving work via periodic message pushes.

[0047] Figure 3 A flowchart of a test case lifecycle iteration method 3000 according to an embodiment of the present invention is shown. Figure 3 As shown, the test case lifecycle iteration management method 3000 includes the following steps: Step S301, writing test cases according to the mind map document template; Step S302, importing the written test cases in batches based on the mind map document template; Step S303, storing the imported test cases and marking them, wherein marking includes marking the test cases as manual test cases; and Step S304, establishing automated test cases and associating the automated test cases with the manual test cases.

[0048] In method 3000, automated test cases can be associated with multiple manual test cases in a 1:N ratio (N is a natural number greater than 0). Users can update the manual test cases associated with the automated test cases, for example, by adding or discarding manual test cases associated with the automated test cases. Updating the association between the automated and manual test cases is achieved by adding or discarding manual test cases associated with the automated test cases. In method 3000, association is achieved by using the number of the automated test case as a prefix to the number of the associated manual test case. Users mark test cases as both automated and manual test cases by labeling them with "Automated" and "Manual" tags. In method 3000, users can also mark test cases as custom test cases by labeling them with custom tags. Custom tags include one or more of the following tags: "Automated," "Manual," "API," "Web," "iOS," "Android," "Implemented," and "Not Implemented." Method 3000 may further include checking the tags and associations of the imported test cases and reporting the tags and associations of the imported test cases via push notification. Additionally, method 3000 may include statistically analyzing one or more of the following data: the number of imported test cases, tags, type distribution, and associations.

[0049] Figure 4 A block diagram of a test case lifecycle iteration system 4000 according to an embodiment of the present invention is shown. Figure 4 As shown, the test case lifecycle iteration management system 4000 includes: a mind map document module 401, configured to provide mind map document templates for users to write test cases; a test case analysis module 402, configured to batch import written test cases based on the mind map document templates; and a test case management module 403, which stores and marks the imported test cases, including marking the test cases as manual test cases; and the test case management module 403 is also configured to create automated test cases and associate the automated test cases with the manual test cases.

[0050] In System 4000, automated test cases can be associated with multiple manual test cases in a 1:N ratio (N is a natural number greater than 0). Users can update the manual test cases associated with the automated test cases, for example, by adding or discarding them. Adding or discarding associated manual test cases updates the association between the automated and manual test cases. In System 4000, association uses the number of the automated test case as a prefix to the number of the associated manual test case. Users label test cases as both automated and manual test cases by tagging them with "Automated" and "Manual" labels. In System 4000, users can also label test cases as custom test cases by tagging them with custom labels. Custom labels include one or more of the following labels: "Automated," "Manual," "API," "Web," "iOS," "Android," "Implemented," and "Not Implemented." System 4000 may also include checking the tags and associations of the imported test cases and reporting the tags and associations of the imported test cases via push notification. Additionally, system 4000 may include statistical analysis of one or more of the following data: the number of imported test cases, tags, type distribution, and associations.

[0051] Figure 5 A computer device is shown that illustrates a test case lifecycle iteration method according to an embodiment of the present invention. Figure 5 As shown, computer device 5000 includes a memory 501 and a processor 502. Although not shown, computer device 500 also includes a computer program stored on the memory 501 and executable on the processor 502. When the processor executes the program, it implements... Figure 1 and Figure 3 The steps are shown in the figure.

[0052] Additionally, as described above, the present invention can also be implemented as a readable storage medium storing a program for causing a computer to execute the test case lifecycle iteration method described above.

[0053] Here, as a readable storage medium, it can be a storage medium of various types, such as disks (e.g., magnetic disks, optical disks, etc.), cards (e.g., memory cards, optical cards, etc.), semiconductor memory (e.g., ROM, non-volatile memory, etc.), tapes (e.g., magnetic tape, cassette tape, etc.).

[0054] By recording and distributing computer programs that enable computers to execute the test case lifecycle iteration method in the above embodiments or that enable computers to implement the functions of the test case lifecycle iteration method in the above embodiments in these readable storage media, it is possible to reduce costs and improve portability and versatility.

[0055] Furthermore, by loading the aforementioned readable storage medium onto a computer, the computer reads the computer program recorded in the storage medium and stores it in a memory. The processor (CPU: Central Processing Unit, MPU: Micro Processing Unit) of the computer reads the computer program from the memory and executes it. Thus, the device that can execute the test case lifecycle iteration method in the above embodiments and realize the function of the test case lifecycle iteration method in the above embodiments is able to perform the test case lifecycle iteration method.

[0056] Those skilled in the art will understand that the present invention is not limited to the embodiments described above, and that the invention may be implemented in many other forms without departing from its spirit and scope. Therefore, the examples and embodiments shown are to be considered illustrative rather than restrictive, and the invention may encompass various modifications and substitutions without departing from the spirit and scope of the invention as defined by the appended claims.

Claims

1. A test case lifecycle iteration management method, characterized in that, The method includes the following steps: Write test cases based on the mind map document template; The test cases were imported in batches based on the mind map document template. Store and label the imported test cases, where imported test cases are marked as manual test cases by default; and Create automated test cases and associate the automated test cases with at least one imported manual test case, wherein the association is achieved by using the number of the automated test case as a prefix of the number of the at least one manual test case; The statistics include the number, tags, type distribution, and relationships of imported test cases; and Check and report the tags and associations of the imported test cases via push notifications.

2. The method according to claim 1, characterized in that, The method also includes adding manual test cases associated with the automated test cases.

3. The method according to claim 1, characterized in that, The method also includes discarding manual test cases associated with the automated test cases.

4. The method according to claim 2 or 3, characterized in that, The method also includes updating the association between the automated test cases and the manual test cases by adding or discarding manual test cases associated with the automated test cases.

5. The method according to claim 1, characterized in that, The method also includes labeling the test cases as automated test cases and manual test cases by assigning them the labels "automated" and "manual".

6. The method according to claim 1, characterized in that, The method also includes marking the test cases as custom test cases by assigning custom tags to the test cases.

7. The method according to claim 6, characterized in that, The custom tags include one or more of the following tags: "Automation", "Manual", "API", "Web", "iOS", "Android", "Implemented", and "Not Implemented".

8. A test case lifecycle iteration management system, characterized in that, The system includes: Mind map document module, configured to provide mind map document templates for writing test cases; A test case analysis module, configured to import written test cases in batches based on the mind map document template; A test case management module, configured to store and mark imported test cases, wherein imported test cases are marked as manual test cases by default; and The test case management module is also configured to create automated test cases and associate the automated test cases with at least one imported manual test case, wherein the association is achieved by using the number of the automated test case as a prefix of the number of the at least one manual test case; The test case analysis module is configured to: count the number, tags, type distribution, and associations of imported test cases; and check and report the tags and associations of imported test cases via message push.

9. The system according to claim 8, characterized in that, The test case management module is configured to add manual test cases associated with the automated test cases.

10. The system according to claim 8, characterized in that, The test case management module is configured to discard manual test cases associated with the automated test cases.

11. The system according to claim 9 or 10, characterized in that, The test case management module is configured to update the association between the automated test cases and the manual test cases by adding or discarding manual test cases associated with the automated test cases.

12. The system according to claim 8, characterized in that, The test case management module is configured to mark test cases as automated test cases and manual test cases by labeling them with "automated" and "manual" tags.

13. The system according to claim 8, characterized in that, The test case management module is configured to mark the test cases as custom test cases by assigning them custom tags.

14. The system according to claim 13, characterized in that, The custom tags include one or more of the following tags: "Automation", "Manual", "API", "Web", "iOS", "Android", "Implemented", and "Not Implemented".

15. A computer-readable storage medium storing instructions, characterized in that, When the instruction is executed by the processor, it causes the processor to perform the method as described in any one of claims 1-7.

Images