Cycle follow-up method and cycle follow-up system for demand test

Abstract

The invention relates to the technical field of demand testing, and discloses a cycle follow-up method and cycle follow-up system for demand testing, and the method comprises the steps: a test task creation module obtains preset information required by a test task, and creates a demand test task based on the preset information; the test case uploading module is used for analyzing the Xmind file based on the Xmind file of the uploaded test case to obtain data of the test case; wherein the test case is generated based on a demand test task; and the test result generation module is used for generating test progress daily report and quality report information in the execution process of the test case based on the data of the test case. According to the method provided by the embodiment of the invention, the test result generation module can automatically generate the test progress daily report and the quality report, so that the time of manual statistics and reporting is reduced, and a tester can timely and quickly follow up the test, thereby optimizing the efficiency of the demand test.

Description

Technical Field

[0001] The present disclosure relates to the technical field of demand testing, and in particular to a cycle tracking method and a cycle tracking system for demand testing. Background Art

[0002] Requirements testing refers to the process of verifying and confirming the requirements document and its implementation during the software development process to ensure that the functions and performance of the software system meet user needs and business goals. With the dynamic changes in user needs, the iteration speed and frequency of requirements testing are gradually increasing.

[0003] The testing tools in related technologies are often unable to adapt to the rapid iteration of demand testing work, and may not be able to quickly follow up on the high-frequency iteration of demand testing, resulting in low efficiency of demand testing. Therefore, how to quickly follow up on the high-frequency iteration of demand testing and improve the efficiency of demand testing has become a problem that needs to be solved. Summary of the invention

[0004] In view of this, the present disclosure provides a cycle follow-up method and a cycle follow-up system for demand testing to solve the problem of how to quickly follow up testing for high-frequency iterative requirements and improve the efficiency of demand testing.

[0005] On the one hand, the present disclosure provides a cycle tracking method for demand testing, which is applied to a cycle tracking system. The cycle tracking system includes: a test task creation module, a test case upload module and a test result generation module. The method includes: a test task creation module, which obtains preset information required for the test task, and creates a demand test task based on the preset information; a test case upload module, which parses the Xmind file based on the uploaded test case to obtain the data of the test case; wherein the test case is generated based on the demand test task; and a test result generation module, which generates a daily report on the test progress and quality report information of the test case during execution based on the test case data.

[0006] On the other hand, the present disclosure also provides a cycle tracking system, which includes a test task creation module, a test case upload module and a test result generation module, wherein: the test task creation module is used to obtain preset information required for the test task, and create a required test task based on the preset information; the test case upload module is used to parse the Xmind file based on the uploaded test case to obtain the data of the test case; wherein the test case is generated based on the required test task; the test result generation module is used to generate a daily test progress report and quality report information of the test case during execution based on the test case data.

[0007] On the other hand, the present disclosure further provides a computer-readable storage medium, on which computer instructions are stored, and the computer instructions are used to enable a computer to implement the above-mentioned cycle tracking method of demand testing.

[0008] On the other hand, the present disclosure further provides a computer program product, including computer instructions, where the computer instructions are used to enable a computer to execute the above-mentioned cycle tracking method of demand testing.

[0009] Through the cycle tracking method and cycle tracking system of the demand test of the above-mentioned embodiments of the present invention, the test result generation module can automatically generate a daily test progress report and a quality report based on the uploaded test case data, thereby improving the process transparency of the test progress, reducing the time for manual statistics and reporting, and ensuring that testers can follow up on the test in a timely and rapid manner, thereby optimizing the efficiency of the demand test.

[0010] In addition, by automatically acquiring and integrating the required preset information through the test task creation module, it is possible to quickly and accurately create demand testing tasks, reduce manual input errors and repetitive work, improve the efficiency and accuracy of task creation, and further improve the efficiency of demand testing. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order to more clearly illustrate the specific embodiments of the present disclosure or the technical solutions in the related technologies, the drawings required for use in the specific embodiments or the related technical descriptions will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0012] Figure 1a An exemplary schematic diagram showing the architecture of a cycle tracking system applied to a cycle tracking method for demand testing according to an embodiment of the present disclosure;

[0013] Figure 1b It is a flowchart of a cycle follow-up method for demand testing provided by an embodiment of the present disclosure;

[0014] Figure 2 A specific flow chart of a cycle follow-up method for demand testing according to an embodiment of the present disclosure is shown;

[0015] Figure 3 is a structural diagram of another periodic follow-up system provided by an embodiment of the present disclosure;

[0016] Figure 4 It is a structural diagram of another periodic follow-up system provided by an embodiment of the present disclosure. DETAILED DESCRIPTION

[0017] Requirements testing refers to the process of verifying and confirming the requirements document and its implementation during the software development process to ensure that the functions and performance of the software system meet user needs and business goals. The main purpose of requirements testing is to ensure that the functions implemented by the development team are consistent with business requirements and user needs, and can correctly solve practical problems.

[0018] Due to the pressure of market competition, dynamic changes in user needs, data-driven decision-making, upgrades in development technology and other factors, the iteration speed and frequency of software product demand will inevitably increase.

[0019] The related technologies often have the following problems:

[0020] 1. Often rely on manual input and data aggregation, especially when generating quality reports, a large amount of information needs to be manually counted, which is not only time-consuming but also prone to errors. There is also a lag in the tracking of test results and progress, which affects the efficiency of demand testing.

[0021] 2. Existing open source testing tools cannot meet the needs of actual testing work. It is necessary to develop customized tools for specific projects to improve testing efficiency and ensure high-quality delivery.

[0022] 3. Project management lacks sufficient quality data support, which makes it difficult to standardize and normalize the project process, thus failing to achieve the goal of improving efficiency.

[0023] To solve the above problems, various embodiments of the present invention provide a cycle tracking method for demand testing, which is applied to a cycle tracking system. The cycle tracking system includes: a test task creation module, a test case upload module and a test result generation module. The method includes: a test task creation module, which obtains preset information required for the test task, and creates a demand test task based on the preset information; a test case upload module, which parses the Xmind file based on the uploaded test case to obtain the data of the test case; wherein the test case is generated based on the demand test task; and a test result generation module, which generates a daily report on the test progress and quality report information of the test case during execution based on the test case data.

[0024] In order to make the purpose, technical solution and advantages of the embodiments of the present disclosure clearer, the technical solution in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are part of the embodiments of the present disclosure, rather than all the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present disclosure.

[0025] Please refer to Figure 1a , Figure 1aFIG. 1 is an exemplary schematic diagram showing the architecture of a cycle tracking system applied to a cycle tracking method for demand testing according to an embodiment of the present disclosure. Figure 1a As shown, the cycle tracking system may include: a test task creation module, a test case upload module and a test result generation module.

[0026] like Figure 1a As shown, the cycle tracking system can be a management system that tracks and manages the requirement testing cycle in an automated manner.

[0027] Among them, the test task creation module can be used to create and manage requirement test tasks, the test case upload module can be used to receive test cases uploaded by testers, and the test result generation module can generate daily test progress reports and quality reports based on test case data to help the development team monitor and evaluate the test process.

[0028] Further references Figure 1b , Figure 1b is a flow chart of a cycle follow-up method for demand testing provided by an embodiment of the present disclosure, which is applied to the above Figure 1a The cycle follow-up system shown in , the process of the method may include the following steps:

[0029] Step S101, a test task creation module obtains preset information required for a test task, and creates a required test task based on the preset information.

[0030] In this embodiment, a test task may refer to an independent work unit in a test process, and a tester may include the entire test life cycle of the test process. Further, a requirement test task may be a test work unit created based on a specific requirement.

[0031] The preset information of the test task may refer to the basic data that needs to be defined and obtained in advance when creating the test task, which can be used to clarify the task scope, task objectives, responsibility allocation, etc. of the test task.

[0032] As an example, the preset information of the test task may include, but is not limited to: task name, task number, requirement type, requirement priority, etc.

[0033] Step S102, the test case upload module parses the Xmind file based on the uploaded test case to obtain the data of the test case.

[0034] In this embodiment, test cases are generated based on demand test tasks.

[0035] The Xmind file of the test case can be a test case file created by the tester through the Xmind tool based on the required test task. Among them, the Xmind file can represent the structure, content and association relationship of the test case in the form of a mind map.

[0036] Specifically, the test cases in the Xmind file can be displayed in the form of root nodes, branch nodes, and leaf nodes. The root node can be used to represent the name of the test object, the branch node can be used to represent the sub-function or test scenario to be tested, and the leaf node can be used to represent a specific test case.

[0037] Furthermore, each child node in the Xmind file can carry tag information.

[0038] In a possible implementation, the test case upload module can simultaneously receive an Xmind file of at least one test case.

[0039] Step S103: The test result generation module generates a daily test progress report and quality report information of the test case during execution based on the test case data.

[0040] In this embodiment, the daily test progress report can be used to track the execution progress of the test tasks on a daily basis, so that the testers can quickly obtain the statistical results of the test execution status. The quality report information can be used to quantify the accumulated data structure during the test process.

[0041] As an example, the daily test progress report may include but is not limited to: the test progress of the day, bug status, and risk warning information. The quality report information may include but is not limited to: test case cumulative data, bug cumulative data, and test process cumulative data.

[0042] In a possible implementation, the daily test progress report can be automatically sent to the work group, or it can be exported manually, which is not specifically limited here. The output form of the quality report information can include but is not limited to: a matrix file (such as EXCEL), and the quality report information can be automatically sent to relevant personnel, for example, to the project leader, development manager, test leader, etc.

[0043] In the cycle follow-up method and cycle follow-up system for demand testing in the above-mentioned embodiments of the present disclosure, the test result generation module can automatically generate a daily test progress report and a quality report based on the uploaded test case data, thereby improving the process transparency of the test progress, reducing the time for manual statistics and reporting, and ensuring that testers can follow up on the test in a timely and rapid manner, thereby optimizing the efficiency of demand testing. By automatically acquiring and integrating the required preset information through the test task creation module, demand test tasks can be created quickly and accurately, which can reduce manual input errors and repetitive work, improve the efficiency and accuracy of task creation, and further improve the efficiency of demand testing.

[0044] In a possible implementation of step S101, the test task includes:

[0045] A test task creation module obtains the first test task creation module required for the test task, obtains the preset information required for the test task, and creates the requirement information and the second information based on the preset information; the first information is used to represent the basic information of the Jira task, and the second information is used to represent the basic information of the quality report information;

[0046] The test task creation module queries the target Jira task in the Jira system based on the Jira task ID in the first information, and obtains the task information in the target Jira task;

[0047] The test task creation module creates a requirement test task based on the first information, the second information and the task information, and associates the requirement test task with a target Jira task.

[0048] In this embodiment, the test task creation module obtains the first information and the second information filled in by the user based on the visual configuration interface.

[0049] In a possible implementation, the first information may be used to characterize part of the basic information of the test task, and the second information may be used to characterize part of the information required in the quality report information, so as to support the subsequent generation of the quality report information.

[0050] As an example, the first information may include but is not limited to: the Jira task ID corresponding to the current requirement test task, the requirement task name, the Jira execution status, the requirement review time, the test submission time, the online time, and the test person in charge.

[0051] Here, the first information may be manually input by the tester, or automatically associated and input after the target Jira task is determined. The task information may refer to detailed task data determined based on the target Jira task.

[0052] Furthermore, Jira can be a project management and issue tracking tool that can provide centralized task management, demand planning, work tracking, and project collaboration capabilities. Jira can be directly associated with test tasks through Jira task IDs.

[0053] Among them, the Jira task ID can be used as a unique identifier in the Jira system to locate the requirement test task. The requirement task name can refer to the task title of the target Jira task in the Jira system. The Jira execution status can indicate the status of the current requirement test task. The requirement review time can refer to the time when the test leader confirms and reviews the test task. The test submission time can refer to the time when the test task is submitted to the tester for testing. The launch time can refer to the time when the test task is planned to be released to the production environment after the test is completed.

[0054] In the cycle tracking method and cycle tracking system of the requirements test of the above embodiment of the present disclosure, by automatically obtaining the Jira task ID and related information, and creating the requirements test task based on this information, the workload of manual input can be greatly simplified, thereby achieving real-time tracking of the requirements test and improving the test efficiency. By automatically creating test tasks and binding them with Jira tasks, project managers can more easily manage the generation of requirements, test progress and quality reports, thereby promoting project progress more efficiently.

[0055] In a possible implementation of the above step S102, the test case upload module parses the Xmind file based on the uploaded test case and obtains the data of the test case based on the following steps:

[0056] The test case upload module receives the Xmind file of the test case uploaded by the user based on the preset scanning entrance, parses the Xmind file, and determines at least one node in the Xmind file; the at least one node includes: a root node and a leaf node;

[0057] The test case upload module parses the tag information of each node in at least one node, classifies and counts each node according to the tag information of each node, and uses the classification and statistics results as the data of the test case; the tag information includes at least one of the following: execution status tag, priority tag.

[0058] In this embodiment, the test case upload module receives at least one Xmind file uploaded by the user through a preset scanning entrance;

[0059] The test case upload module identifies the root node, branch node and leaf node in each Xmind file of at least one Xmind file;

[0060] The test case upload module reads and parses the marker information contained in the root node, branch node and leaf node in each Xmind file, and classifies and counts each node according to execution status and priority.

[0061] The execution status may include but is not limited to: successful execution, failed, blocked, and unexecuted, and the priority may include but is not limited to: P0, P1, P2, and P3. Here, P0 has the highest priority.

[0062] The test case upload module classifies and counts each node and uses the classification and statistical results as test case data, which may include:

[0063] The test case upload module counts the number of test cases in each execution state and the number of test cases with different priorities, and determines the classification statistics corresponding to each test task.

[0064] Furthermore, the test case upload module can generate a statistical report based on the results of the classification statistics, and provide the statistical report to the test leader and testers.

[0065] In the cycle follow-up method and cycle follow-up system for demand testing of the above-mentioned embodiments of the present disclosure, the data of the current test case execution can be quickly output with one click through the preset scanning entrance, and the next work can be carried out more quickly and accurately based on the parsed data. By docking with Xmind files, the data of test cases can be automatically extracted, the workload of testers can be reduced, and the efficiency of demand testing can be improved. Automated statistical results can speed up the decision-making process. The test team can understand the execution status and quality of the test cases in real time, make adjustments quickly, and reduce time waste.

[0066] In a possible implementation of the above step S103, the test result generation module generates a daily test progress report and quality report information of the test case during execution based on the test case data, which is implemented based on the following steps:

[0067] The test result generation module obtains the execution status of the target Jira task, where the execution status includes at least one of the following: testing, testing completed, or closed;

[0068] The test result generation module generates a daily report on the test progress of the day based on the first template when the execution status of the target Jira task is in testing;

[0069] The test result generation module, when the execution status of the target Jira task is test completion, traverses the final version of the Xmind file to determine whether there are any missed test cases in the Xmind file. When it is determined that there are missed test cases, a missed test reminder message is sent to the test leader;

[0070] The test result generation module generates quality report information based on the second template when the execution status of the target Jira task is closed, and sends the quality report information to the test leader and the project leader.

[0071] In this embodiment, testing may indicate that the tester has started executing the test case and is tracking and recording the test results. Testing completed may indicate that the test task has completed the execution of all test cases and the tester has evaluated all test results. Closed may indicate that the test task has been completely completed and the tester believes that there is no further work to be done on the test task.

[0072] The test result generation module generates a daily report of the test progress for the day based on the first template when the execution status of the target Jira task is in testing, including:

[0073] The test result generation module generates a daily report of the test progress for the day based on the final version of the Xmind file of the previous day, the final version of the Xmind file of the day, and the data of the target Jira task when the execution status of the target Jira task is in testing.

[0074] Specifically, the test result generation module obtains the XMind file uploaded and finally confirmed the day before, the XMind file uploaded and finally confirmed on the day, and the relevant data of the target Jira task, and generates the daily test progress report for the day.

[0075] Among them, the final version of the Xmind file of the previous day includes all the test cases and execution status of the previous day, and the final version of the Xmind file of the day includes all the test cases and execution status of the day. The relevant data of the target Jira task may include but is not limited to: the status of the Jira task, the number of test cases executed, the number of bugs found, and the bug repair status.

[0076] As an example, the daily test progress report for the day may include, but is not limited to: the number of test cases successfully executed on the day, the number of test cases not executed or blocked on the day, the number of bugs found on the day and their repair status, the execution status of the test tasks on the day, the execution progress of the test tasks and the comparison with the expected plan.

[0077] The test result generation module, when the execution status of the target Jira task is test completion, traverses the final version of the Xmind file to determine whether there are any missed test cases in the Xmind file. When it is determined that there are missed test cases, a missed test reminder message is sent to the test person in charge, which may include:

[0078] The test result generation module, when the execution status of the target Jira task is test completed, traverses the final version of the Xmind file of the day, checks the execution status of each test case, determines whether there are test cases with an execution status of not executed or blocked, and sends a missed test reminder message to the test leader as a missed test case.

[0079] As an example, the missed test reminder information may include, but is not limited to: a list of missed test cases and detailed information of the missed test cases. The missed test reminder information may be sent via email, instant messaging tools, or a project management system.

[0080] In the cycle tracking method and cycle tracking system of the demand test in the above embodiment of the present disclosure, the daily progress report, missed test reminder and quality report are automatically generated, which reduces the workload of manual statistics and report writing, and significantly saves time and labor costs. While saving time and labor costs, the accuracy, timeliness and standardization of information are ensured, so that the team can perform testing and project management more efficiently.

[0081] In a possible implementation of the above embodiment, the quality report information includes at least one of the following: test quality, product quality, development quality, test quality, efficiency, and data source; wherein:

[0082] Quality of test submissions, including at least one of the following: number of test submissions, number of format returns, product quality, including: number of PRD revisions;

[0083] Development quality, including at least one of the following: number of feature rollbacks, number of bugs of different priorities, number of front-end bugs, back-end bugs, number of bugs of different bug types, number of revisions of technical design documents, and bug repair rate;

[0084] Test quality, including at least one of the following: whether test cases are reviewed, number of test cases, test case execution rate, percentage of bugs with preset priorities, percentage of bug numbers, bug efficiency, and test case review change rate;

[0085] Efficiency, including at least one of the following: timeliness of fixing bugs of preset priority, rate of change of testing workload, rate of change of project schedule, timeliness of verifying bugs of preset priority;

[0086] Data sources include at least one of the following: the number of unfixed bugs, the number of unexecuted test cases, the number of invalid bugs, the number of preset priority bugs that take longer than the preset time to resolve, project estimated tests, project actual tests, project estimated total cycle, project total cycle, the number of preset priority bugs that take longer than the preset time to verify, the total number of test case reviews, and the total number of test case reviews.

[0087] In this embodiment, the number of test requests in the test quality may refer to the number of test requests completed by the tester for a certain requirement or functional module within one cycle, and the number of format rejections may refer to the number of times the test case document or requirement document format does not comply with regulations or is incomplete, resulting in the inability to test and is thus returned for reorganization.

[0088] The number of PRD revisions in product quality may refer to the number of revisions that the Product Requirement Document (PRD) undergoes during the entire product development process.

[0089] The number of function rejections in development quality may refer to the number of times a completed function is required to be redeveloped during the development process because it does not meet requirements or quality standards. The number of bugs of different priorities may refer to the number of bugs of different priorities. Front-end bugs may refer to front-end user interface bugs, and back-end bugs may refer to system back-end bugs. The number of bugs of different bug types may refer to the number of each bug type after classifying them by bug type. The number of technical design document revisions may refer to the number of times the technical design document has been modified. The bug fix rate may refer to the ratio of the number of bugs fixed by the development team to the total number of reported bugs.

[0090] Whether use case review is conducted in test quality may refer to whether a formal review process is carried out after the test case is written; the number of test cases may refer to the total number of test cases designed and created in the project; the test case execution rate may refer to the ratio of the number of executed test cases to the total number of test cases; the proportion of preset priority bugs may refer to the ratio of P1 and P2 level bugs; the proportion of the number of bugs may refer to the ratio of various types of bugs among all defects; the bug efficiency rate may refer to the ratio of reported bugs that have been verified to be real problems; the test case review change rate refers to the ratio of changes between the number of reviewed test cases and the total number of test cases over a period of time.

[0091] The preset priority bug repair time limit in efficiency may refer to the time interval from the discovery and reporting of P1 and P2 level bugs to their repair completion; the test workload change rate may refer to the extent of change in the test workload during the test cycle relative to the previous stage; the project progress change rate may refer to the degree of difference between the actual completion time of the project plan and the expected completion time; the preset priority bug verification time limit may refer to the time interval from the completion of the P1 and P2 level bugs submission of the bug repair to the completion of the bug status verification by the tester.

[0092] The number of unfixed bugs in the data source may refer to the total number of bugs reported but not yet fixed during the test cycle; the number of unexecuted test cases may refer to the number of test cases designed in the test plan that have not been executed; the number of invalid bugs may refer to the number of bugs submitted during the test process that are determined by the development team as non-actual problems; the number of preset priority bugs with a resolution time greater than the preset time may refer to the number of P1 and P2 level bugs with a resolution time greater than 1 day; the estimated project test may refer to the estimated test cycle time when the project is launched, and the actual project test may refer to the actual time consumed from the start of the test to the completion of the test; the estimated total project cycle may refer to the estimated time from the start to the completion of the project as a whole, and the total project cycle may refer to the actual total time from the start to the final completion of the project; the number of preset priority bugs with a verification time greater than the preset time may refer to the number of P1 and P2 level bugs with a verification time greater than 1 day; the total number before test case review may refer to the number of test cases designed before the start of the test case review, and the total number after test case review may refer to the number of final test cases revised after the test case review is completed.

[0093] In one possible implementation, based on a preset scanning entry, an Xmind file of a test case uploaded by a user is received to quickly obtain the execution data of the current test case, thereby greatly saving the time cost of manually calculating and filling in data.

[0094] In the cycle follow-up method and cycle follow-up system of the requirement test in the above-mentioned embodiment of the present disclosure, by covering indicators of multiple dimensions such as test quality, product quality, development quality, test quality, efficiency and data source in the quality report information, the quality and efficiency of the testing link and related development processes are fully reflected. Each dimension contains detailed sub-indicators, such as the number of test submissions, the number of PRD revisions, the bug fix rate, etc., which can accurately describe the key issues and improvement points in the testing process. 7. The function covers the test-related work in two stages: during the test execution and after the test is completed, enabling the smooth advancement of the work.

[0095] In a specific embodiment, Figure 2 A specific flow chart of a cycle follow-up method for demand testing according to an embodiment of the present disclosure is shown, and the figure includes the following steps:

[0096] Step S201, creating a demand test task;

[0097] Here, the test task creation module obtains the preset information required for the test task and creates the required test task based on the preset information;

[0098] Step S202, upload the Xmind file through the preset scanning entry;

[0099] Here, the test case upload module receives the Xmind file of the test case uploaded by the user based on the preset scanning entrance;

[0100] Step S203, inputting the preset information required for the test task;

[0101] Here, the test task creation module obtains the first information and the second information required for the test task;

[0102] Step S204, connecting to the Jira system to obtain task information;

[0103] Here, the test task creation module queries the target Jira task in the Jira system based on the Jira task ID in the first information, and obtains the task information in the target Jira task;

[0104] Step S205, uploading the test case Xmind file;

[0105] Here, the test case upload module receives the Xmind file of the test case uploaded by the user based on the preset scanning entrance;

[0106] Step S206, parsing the Xmind file and counting the use case data;

[0107] Here, the test case upload module parses the Xmind file and obtains the test case data;

[0108] Step S207, parsing the Xmind file and counting the use case data;

[0109] Here, the test case upload module parses the Xmind file and obtains the test case data;

[0110] Step S208, determining whether the Jira execution status is test completed;

[0111] Here, the test result generation module obtains the execution status of the target Jira task and determines whether the Jira execution status is test completed;

[0112] Step S209, generating a daily report on the test progress;

[0113] Here, the test result generation module generates a daily report of the test progress for the day based on the first template when the execution status of the target Jira task is in testing, and returns to step S205;

[0114] Step S210, determining whether there are any test cases that are missed;

[0115] Here, the test result generation module, when the execution status of the target Jira task is test completed, traverses the final version of the Xmind file to determine whether there are any missed test cases in the Xmind file;

[0116] Step S211, sending missed detection reminder information;

[0117] Here, when the test result generation module determines that there is a missed test case, it sends a missed test reminder message to the test person in charge, and returns to step S205;

[0118] Step S212, determining whether the Jira execution status is closed;

[0119] Here, the test result generation module determines whether the execution status of the target Jira task is closed;

[0120] Step S213, generating quality report information;

[0121] Here, the test result generation module generates quality report information based on the second template when the execution status of the target Jira task is closed;

[0122] Step S214, sending a quality report information email;

[0123] Here, the test result generation module sends quality report information to the test leader and project leader.

[0124] In one embodiment, a cycle tracking system 300 is provided, and the cycle tracking system 300 corresponds one-to-one with the cycle tracking method of the demand test in the above embodiment. Figure 3 As shown, the cycle tracking system 300 includes a test task creation module 301, a test case upload module 302 and a test result generation module 303, wherein each functional module is described in detail as follows:

[0125] The test task creation module 301 is used to obtain the preset information required for the test task and create the required test task based on the preset information;

[0126] The test case upload module 302 is used to parse the Xmind file based on the uploaded test case and obtain the data of the test case; wherein the test case is generated based on the required test task;

[0127] The test result generation module 303 is used to generate a daily test progress report and quality report information of the test case during execution based on the test case data.

[0128] In one embodiment, the test task creation module 301 is used to query the target Jira task in the Jira system based on the Jira task ID in the first information, and obtain the task information in the target Jira task;

[0129] The test task creation module 301 is used to create a requirement test task based on the first information, the second information and the task information, and associate the requirement test task with a target Jira task.

[0130] In one embodiment, the test case upload module 302 is used to receive the Xmind file of the test case uploaded by the user based on the preset scanning entrance, parse the Xmind file, and determine at least one node in the Xmind file; the at least one node includes: a root node and a leaf node;

[0131] The test case upload module 302 is used to parse the tag information of each node in at least one node, classify and count each node according to the tag information of each node, and use the classification and statistics results as the data of the test case; the tag information includes at least one of the following: execution status tag, priority tag.

[0132] In one embodiment, the test result generation module 303 is used to obtain the execution status of the target Jira task, and the execution status includes at least one of the following: testing, testing completed, and closed;

[0133] The test result generating module 303 is used to generate a daily test progress report for the day based on the first template when the execution status of the target Jira task is in testing;

[0134] The test result generation module 303 is used to traverse the final version of the Xmind file when the execution status of the target Jira task is test completion, determine whether there are any missed test cases in the Xmind file, and send a missed test reminder message to the test person in charge when it is determined that there are missed test cases;

[0135] The test result generation module 303 is used to generate quality report information based on the second template when the execution status of the target Jira task is closed, and send the quality report information to the test leader and the project leader.

[0136] In one embodiment, the test result generation module 303 is used to generate a daily test progress report for the day based on the final version of the Xmind file of the previous day, the final version of the Xmind file of the day, and the data of the target Jira task when the execution status of the target Jira task is under testing.

[0137] In one embodiment, the quality report information includes at least one of the following: test quality, product quality, development quality, test quality, efficiency, and data source; wherein:

[0138] Quality of test submissions, including at least one of the following: number of test submissions, number of format returns, product quality, including: number of PRD revisions;

[0139] Development quality, including at least one of the following: number of feature rollbacks, number of bugs of different priorities, number of front-end bugs, back-end bugs, number of bugs of different bug types, number of revisions of technical design documents, and bug repair rate;

[0140] Test quality, including at least one of the following: whether test cases are reviewed, number of test cases, test case execution rate, percentage of bugs with preset priorities, percentage of bug numbers, bug efficiency, and test case review change rate;

[0141] Efficiency, including at least one of the following: timeliness of fixing bugs of preset priority, rate of change of testing workload, rate of change of project schedule, timeliness of verifying bugs of preset priority;

[0142] Data sources include at least one of the following: the number of unfixed bugs, the number of unexecuted test cases, the number of invalid bugs, the number of preset priority bugs that take longer than the preset time to resolve, project estimated tests, project actual tests, project estimated total cycle, project total cycle, the number of preset priority bugs that take longer than the preset time to verify, the total number of test case reviews, and the total number of test case reviews.

[0143] It should be noted that: the cycle tracking system provided in the above embodiment only uses the division of the above program modules as an example to illustrate when implementing the cycle tracking method of the corresponding demand test. In actual application, the above processing can be assigned to different program modules as needed, that is, the internal structure of the above system can be divided into different program modules to complete all or part of the above-described processing. Figure 1b The embodiments of the method shown belong to the same concept, and the specific implementation process is detailed in the method embodiments, which will not be repeated here.

[0144] The present disclosure also provides a computer device having the above Figure 3 The cycle follow-up method for requirement testing is shown.

[0145] See also Figure 4 , Figure 4 is a structural diagram of another cycle follow-up system provided by an embodiment of the present disclosure, such as Figure 4As shown, the computer device includes: one or more processors 10, a memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. Various components are connected to each other using different buses for communication, and can be installed on a common mainboard or installed in other ways as needed. The processor can process the instructions executed in the computer device, including instructions stored in or on the memory to display the graphical information of the GUI on an external input / output device (such as, a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple computer devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Figure 4 A processor 10 is taken as an example.

[0146] The processor 10 may be a central processing unit, a network processor or a combination thereof. The processor 10 may further include a hardware chip. The hardware chip may be a dedicated integrated circuit, a programmable logic device or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic or any combination thereof.

[0147] The memory 20 stores instructions executable by at least one processor 10, so that at least one processor 10 executes the method shown in the above embodiment.

[0148] The memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the computer device, etc. In addition, the memory 20 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some optional embodiments, the memory 20 may optionally include a memory remotely arranged relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0149] The memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid state drive; the memory 20 may also include a combination of the above types of memory.

[0150] The computer device also includes an input device 30 and an output device 40. The processor 10, the memory 20, the input device 30 and the output device 40 may be connected via a bus or other means. Figure 4 The example of connecting through bus is taken in the following.

[0151] The input device 30 can receive input digital or character information, and generate key signal input related to the user settings and function control of the computer device, such as a touch screen, a keypad, a mouse, a track pad, a touch pad, an indicator bar, one or more mouse buttons, a trackball, a joystick, etc. The output device 40 may include a display device, an auxiliary lighting device (e.g., an LED) and a tactile feedback device (e.g., a vibration motor), etc. The above-mentioned display device includes but is not limited to a liquid crystal display, a light emitting diode, a display and a plasma display. In some optional embodiments, the display device can be a touch screen.

[0152] The computer device also includes a communication interface, which is used for the computer device to communicate with other devices or a communication network.

[0153] The embodiments of the present disclosure also provide a computer-readable storage medium. The above-mentioned method according to the embodiments of the present disclosure can be implemented in hardware, firmware, or can be implemented as a computer code that can be recorded in a storage medium, or can be implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and will be stored in a local storage medium and downloaded through a network, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state drive, etc.; further, the storage medium can also include a combination of the above-mentioned types of memory. It can be understood that a computer, a processor, a microprocessor controller, or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor, or hardware, the method shown in the above embodiment is implemented.

[0154] A part of the present disclosure may be applied as a computer program product, such as a computer program instruction, which, when executed by a computer, can call or provide the method and / or technical solution according to the present disclosure through the operation of the computer. Those skilled in the art should understand that the existence of computer program instructions in computer-readable media includes, but is not limited to, source files, executable files, installation package files, etc., and accordingly, the way in which computer program instructions are executed by a computer includes, but is not limited to: the computer directly executes the instruction, or the computer compiles the instruction and then executes the corresponding compiled program, or the computer reads and executes the instruction, or the computer reads and installs the instruction and then executes the corresponding installed program. Here, the computer-readable medium can be any available computer-readable storage medium or communication medium accessible to the computer.

[0155] Although the embodiments of the present disclosure have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present disclosure, and such modifications and variations are all within the scope defined by the appended claims.

Claims

1. A cycle follow-up method for demand testing, characterized in that: Applied to a cycle follow-up system, the cycle follow-up system includes: a test task creation module, a test case upload module and a test result generation module, the method includes: A test task creation module obtains preset information required for the test task and creates a required test task based on the preset information; A test case upload module, based on an Xmind file of an uploaded test case, parses the Xmind file to obtain data of the test case; wherein the test case is generated based on the required test task; The test result generation module generates a daily test progress report and quality report information of the test case during execution based on the data of the test case.

2. The method according to claim 1, characterized in that The test task creation module obtains the preset information required for the test task and creates the required test task based on the preset information, including: A test task creation module is used to obtain first information and second information required for the test task; the first information is used to represent the basic information of the Jira task, and the second information is used to represent the basic information of the quality report information; The test task creation module queries the target Jira task in the Jira system based on the Jira task ID in the first information, and obtains the task information in the target Jira task; The test task creation module creates a requirement test task based on the first information, the second information and the task information, and associates the requirement test task with the target Jira task.

3. The method according to claim 2, characterized in that The test case upload module parses the Xmind file based on the uploaded test case and obtains the data of the test case based on the following steps: The test case upload module receives the Xmind file of the test case uploaded by the user based on the preset scanning entrance, parses the Xmind file, and determines at least one node in the Xmind file; The at least one node includes: a root node and a leaf node; The test case upload module parses the tag information of each node in at least one node, classifies and counts each node according to the tag information of each node, and uses the results of the classification and statistics as the data of the test case; the tag information includes at least one of the following: execution status tag, priority tag.

4. The method according to claim 3, characterized in that: The test result generation module generates the test progress report and quality report information of the test case during the execution process based on the data of the test case, which is implemented based on the following steps: The test result generation module obtains the execution status of the target Jira task, where the execution status includes at least one of the following: testing, test completed, closed; The test result generation module generates a daily test progress report for the day based on the first template when the execution status of the target Jira task is in testing; The test result generation module, when the execution status of the target Jira task is test completion, traverses the final version of the Xmind file to determine whether there are any missed test cases in the Xmind file, and when it is determined that there are any missed test cases, sends a missed test reminder message to the test person in charge; The test result generation module generates quality report information based on the second template when the execution status of the target Jira task is closed, and sends the quality report information to the test leader and the project leader.

5. The method according to claim 4, characterized in that The test result generation module generates a daily report of the test progress for the day based on the first template when the execution status of the target Jira task is in testing, including: The test result generation module generates a daily report of the test progress for the day based on the final version of the Xmind file of the previous day, the final version of the Xmind file of the day, and the data of the target Jira task when the execution status of the target Jira task is in testing.

6. The method according to claim 4, characterized in that The quality report information includes at least one of the following: test quality, product quality, development quality, test quality, efficiency, and data source; wherein: The quality of the test submission includes at least one of the following: the number of test submissions and the number of format rejections; the product quality includes: the number of PRD revisions; The development quality includes at least one of the following: the number of function rollbacks, the number of bugs of each priority level, the number of front-end bugs, back-end bugs, the number of bugs of different bug types, the number of revisions of technical design documents, and the bug repair rate; The test quality includes at least one of the following: whether a test case is reviewed, the number of test cases, the test case execution rate, the percentage of bugs with preset priorities, the percentage of the number of bugs, the bug efficiency, and the test case review change rate; The efficiency includes at least one of the following: the timeliness of fixing a preset priority bug, the rate of change of testing workload, the rate of change of project progress, and the timeliness of verifying a preset priority bug; The data source includes at least one of the following: the number of unfixed bugs, the number of unexecuted test cases, the number of invalid bugs, the number of preset priority bugs that take longer than a preset time to resolve, the project's estimated test, the project's actual test, the project's estimated total cycle, the project's total cycle, the number of preset priority bugs that take longer than a preset time to verify, the total number of test case reviews, and the total number of test case reviews.

7. A periodic follow-up system, characterized in that: The cycle tracking system includes a test task creation module, a test case upload module and a test result generation module, wherein: A test task creation module is used to obtain preset information required for the test task and create a required test task based on the preset information; A test case upload module, used to parse the Xmind file based on the uploaded test case, and obtain the data of the test case; wherein the test case is generated based on the required test task; The test result generation module is used to generate a daily test progress report and quality report information of the test case during execution based on the data of the test case.

8. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the cycle tracking method for demand testing according to any one of claims 1 to 6.

9. A computer program product, characterized in that The method comprises computer instructions, wherein the computer instructions are used to cause a computer to execute the cycle tracking method for demand testing according to any one of claims 1 to 6.

Images