Software test management method, storage medium, and system
Patent Information
- Application Number
- CN202211310119.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-10-25
- Publication Date
- 2026-11-03
- Estimated Expiration
- 2042-10-25
AI Technical Summary
The increased workload of software testing has led to scattered and complex work among software testers, making them difficult to manage effectively.
By acquiring test data from software testing tasks, configuring task evaluation rules, reviewing and analyzing the test data, quantifying and matching test work indicators, and dynamically adjusting evaluation rules, management efficiency can be improved.
It enables accurate evaluation and effective management of software testers' work, improves management efficiency, and adapts to the actual execution of software testing tasks.
Smart Images

Figure CN115617670B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the technical field of software test management systems, specifically to a software test management method, storage medium, and system. Background Technology
[0002] Ping An Bank regularly upgrades and updates its software to provide users with more and more stable financial services. Before any upgrade or update, the software must be tested. This testing is typically conducted by software testers.
[0003] With the increasing frequency of software upgrades and the growing number of software vulnerabilities, the workload of software testing has also increased accordingly. Therefore, more software testers are needed. However, because the software testing tasks performed by software testers are often scattered and complex, it is difficult to effectively manage the work of these testers. Summary of the Invention
[0004] This application provides a software testing management method, storage medium, and system that can improve the management efficiency of software testing personnel.
[0005] In a first aspect, embodiments of this application provide a software testing management method, applied to a software testing management system, the method comprising:
[0006] Acquire test data for software testing tasks, and configure task evaluation rules for software testing tasks;
[0007] The test data is reviewed and analyzed according to the task evaluation rules to obtain the analysis results of the test data.
[0008] The analysis results are quantified according to preset quantification rules to obtain the test work indicators of the analysis results;
[0009] The test work indicators are matched with the task production indicators to obtain the matching results, and the task evaluation rules are adjusted based on the matching results.
[0010] Secondly, embodiments of this application also provide a computer-readable storage medium storing a computer program thereon, which, when run on a computer, causes the computer to execute the software test management method provided in any embodiment of this application.
[0011] Thirdly, embodiments of this application also provide a software testing management system, including:
[0012] The software test coordination module is used to collect test data for software testing tasks.
[0013] The rule maintenance module is used to configure task evaluation rules for software testing tasks, and to update task evaluation rules in response to optimization instructions;
[0014] The software testing management module is used to review and analyze test data according to task evaluation rules to obtain the analysis results of the test data; to quantify the analysis results according to preset quantification rules to obtain the test work indicators of the analysis results; and to match the test work indicators with the task production indicators to obtain the matching results, and to determine whether to adjust the task evaluation rules based on the matching results.
[0015] The results display module provides a user interface and displays the data obtained through the software test management module on the user interface.
[0016] The technical solution provided in this application involves acquiring test data from software testing tasks and configuring task evaluation rules for those tasks; reviewing and analyzing the test data according to the evaluation rules to obtain analysis results; quantifying the analysis results according to preset quantification rules to obtain test work indicators; matching these indicators with task production indicators to obtain matching results; and determining whether to adjust the task evaluation rules based on the matching results. On one hand, by constructing a complete software testing management system, the testing work performed by software testers can be evaluated intuitively, and the evaluation indicators are applicable to each software tester, improving the accuracy of evaluating their work efficiency. On the other hand, by dynamically adjusting the task evaluation rules, the system can adapt to the actual execution of software testing tasks, making the evaluation results more accurate and facilitating effective management of software testers. Attached Figure Description
[0017] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0018] Figure 1 This is a flowchart illustrating the software testing management method provided in an embodiment of this application.
[0019] Figure 2 A detailed schematic diagram illustrating the software testing method provided in the embodiments of this application.
[0020] Figure 3 This is a schematic diagram of the structure of the software testing management system provided in an embodiment of this application. Detailed Implementation
[0021] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the protection scope of this application.
[0022] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.
[0023] Software testing: Describes a process used to facilitate the identification of the correctness, integrity, security, and quality of software. In other words, software testing is a review or comparison process between actual output and expected output.
[0024] Software testing includes requirements review, design review, test planning, test case review, and test execution. Different test data will be generated during the software testing process depending on the specific test content.
[0025] This application provides a software test management method. The executing entity of this method can be a device such as a smartphone, tablet, handheld computer, or desktop computer, or a server. The server can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms, but is not limited to these. This software test management method is applied to a software test management system.
[0026] Please see Figure 1 , Figure 1 This is a flowchart illustrating the software testing management method provided in this application embodiment. The specific flow of the software testing management method provided in this application embodiment can be as follows:
[0027] 101. Obtain test data for software testing tasks, and configure task evaluation rules for software testing tasks.
[0028] Software testing tasks include various tasks in the software testing process, such as software network performance testing, software stability testing, software compatibility testing with electronic devices, software interface display testing, and software redirection testing.
[0029] After the software testing tasks are determined, they can be assigned to the corresponding software testers. A software tester can have multiple software testing tasks, and a software testing task can also be assigned to multiple software testers. The specific situation is not limited here.
[0030] For example, the test data for a software testing task may include the software tester, the name of the software testing task, the items to be tested, the testing process, and the information to be detected at each test node.
[0031] The task evaluation rules are pre-configured task evaluation specifications corresponding to the software testing task. Specifically, by obtaining the task evaluation rules corresponding to the software testing task, the execution status of the software testing task can be evaluated after the task is completed, or at each stage of the task's completion. This evaluation indicates the quality of the software testing task's completion.
[0032] 102. Review and analyze the test data according to the task evaluation rules to obtain the analysis results of the test data.
[0033] By using task evaluation rules to review and analyze test data, the analysis results can indicate the quality of the test data.
[0034] The task evaluation rules can be multi-dimensional. By reviewing and analyzing the test data from each dimension, a comprehensive analysis result can be obtained, which can more accurately represent the completion status of the software testing task.
[0035] 103. Quantify the analysis results according to the preset quantification rules to obtain the test work indicators of the analysis results.
[0036] This approach quantifies the analysis results into numerical values, which are then used to visually represent the results as numerical test performance indicators. For example, if the analysis results include "pass" and "fail," "pass" can be quantified as 1, and "fail" as -1. Similarly, if the analysis results are categorized as "excellent," "good," "average," or "poor," "excellent" can be quantified as 0.8, "good" as 0.6, "average" as 0.4, and "poor" as 0.2. Understandably, there are various quantification methods and ways to express analysis results, and any method for quantifying non-numerical analysis results into numerical test performance indicators can be used in this application's embodiments.
[0037] 104. Match the test work indicators with the task production indicators to obtain the matching results, and determine whether to adjust the task evaluation rules based on the matching results.
[0038] Among them, the task production index is the minimum index corresponding to the software testing task. The task production index is obtained through statistical collection. For example, the inherent defects of the software testing task itself are collected within a certain period of time, and the test defects caused by the software testers are excluded, thereby obtaining the task production index.
[0039] Here's an example: when testing a piece of software, there's an inherent performance issue that affects the test results regardless of the testing conditions. This issue causes a 20% drop in the software's test performance metrics. If the maximum score for the test performance metrics is 1, the task productivity metric could be 0.2.
[0040] In practice, this application is not limited by the execution order of the described steps. Without causing conflicts, some steps may be performed in other orders or simultaneously.
[0041] In some embodiments, test data includes: the number of test cases, test time, and the number of test defects; task evaluation rules include evaluation of test efficiency, test case output rate, and defect rate.
[0042] The test data is reviewed and analyzed according to the task evaluation rules, and the analysis results of the test data are obtained, including:
[0043] The number of test cases and test time were reviewed and analyzed based on test efficiency to obtain the test efficiency difference in the test data; and...
[0044] The number of test cases and the number of test defects are reviewed and analyzed based on the test case output rate to obtain the test defect difference in the test data; and...
[0045] The defect rate is used to review and analyze the number of test defects and the number of test cases to obtain the defect rate difference of the test data.
[0046] The ratio of the number of test cases to the test time is the test efficiency of executing the test case. By comparing the test efficiency of executing the test case with the test efficiency in the task evaluation rules, the test efficiency difference between the two can be obtained. This test efficiency difference can indicate the analysis results of the test efficiency of the test cases in the test data.
[0047] Accordingly, the ratio of the number of test cases to the number of test defects is the test case output rate of executing the test case, and the corresponding test defect difference can indicate the analysis results of the test case output rate of the test cases in the test data.
[0048] Accordingly, the ratio of the number of test defects to the test time is the defect rate of executing the test case, and the corresponding defect rate difference can indicate the analysis results of the defect rate of the test cases in the test data.
[0049] Defects can include software testing failures, such as regression test failures, delayed modifications, and abnormal software interface display. Test time refers to the time spent executing software testing tasks.
[0050] For example, test data may also include: the number of required business processes, the number of R&D test tasks, and the types of test defects.
[0051] Specifically, comparing the number of required business functions and the number of test cases can reveal whether the workload of software testers is saturated. Comparing development test task data with the number of required business functions can also describe the development capabilities of software testers. Analyzing defect categories can also describe common testing problems that occur during software testing, allowing for targeted alerts about those defects.
[0052] In addition, the task evaluation rules also include: requirement coverage and defect discovery rate. By reviewing and analyzing the number of requirement business operations and the number of test cases using requirement coverage, a requirement difference is obtained, which indicates the analysis results of the requirement coverage of the test cases. Similarly, by reviewing and analyzing the number of defects and the time consumed using defect discovery rate, a defect discovery rate difference is obtained, which indicates the analysis results of the defect discovery rate of the test cases.
[0053] As shown above, by reviewing and analyzing the task evaluation rules of the test data in each dimension, we can obtain the task review results indicated by the task evaluation rules in each dimension, and the set of these task review results represents the analysis results of the test data.
[0054] In some embodiments, the analysis results are quantified according to preset quantification rules to obtain the test performance indicators of the analysis results, including:
[0055] According to the weight coefficients indicated by the preset quantification rules, the corresponding weight coefficients are assigned to the test efficiency difference, test defect difference, and defect rate difference, respectively.
[0056] According to the statistical function indicated by the preset quantification rules, the test efficiency difference, test defect difference, and defect rate difference are statistically analyzed based on the corresponding weight coefficients to obtain the test work indicators of the analysis results.
[0057] Among them, the quantification rules not only indicate which statistical function to use to calculate the difference in test efficiency, the difference in test defects, and the difference in defect rate, but also indicate the weight coefficient corresponding to each difference.
[0058] The statistical function can be either linear or nonlinear. By substituting the difference in test efficiency, the difference in test defects, and the difference in defect rate as calculation quantities into the statistical function, a statistical value can be obtained, which is called the test performance indicator.
[0059] For example, this only provides a scheme for quantifying the test efficiency difference, test defect difference, and defect rate difference as analysis results, but the scheme provided in this embodiment can be used as a reference for more analysis results.
[0060] The weighting coefficients indicated by the preset quantification rules can change according to different analysis results. The weighting coefficients corresponding to each difference in the analysis results can be the same or different, or some differences may have weighting coefficients while others may not. There are various specific implementation methods, which will not be listed here.
[0061] As described above, test data can first be reviewed and analyzed across multiple dimensions using task evaluation rules. The analysis results are expressed as differences in test efficiency, test defects, and defect rates. Then, the analysis results are quantified using preset quantitative rules to obtain a test performance indicator that characterizes the task completion status of software testers. This allows for accurate analysis of software testers' work performance and provides a clear, quantifiable description of their work through test performance indicators. This facilitates horizontal and vertical comparisons of the work performance of different departments or individual software testers, enabling effective management. Furthermore, the test performance indicators reveal shortcomings in the work of software testers, facilitating corrective action and improving their work efficiency.
[0062] In some embodiments, test performance indicators are matched with task production indicators to obtain matching results, and the task evaluation rules are adjusted based on the matching results, including:
[0063] Determine whether the difference between the test work indicators and the task production indicators is greater than a preset threshold. The task production indicators are used to measure the preset defects of the software test tasks.
[0064] If so, it is determined that the test work indicators and task production indicators do not match, and the task evaluation rules are adjusted according to the difference in indicators.
[0065] In this embodiment, the task production metric corresponds to the minimum metric, which includes defects that normally occur during software testing, such as functional defects and / or performance defects. The task production metric can be the defect rate of a certain defect type that occurs most frequently within a certain time period. By comparing this defect rate with the testing efficiency, the task production metric can be obtained.
[0066] Of course, the performance metrics for this task can also be an empirical value, or a value pre-assessed by the task. These metrics reflect the ideal performance indicators for performing software testing tasks.
[0067] Specifically, when matching testing performance indicators with task production indicators, if the testing performance indicators are greater than the task production indicators, it indicates that the testing performance indicators are reasonable, or that the software testers have performed their software testing tasks satisfactorily. If the testing performance indicators are less than the task production indicators, it indicates that the testing performance indicators are unreasonable, or that the software testers have performed their software testing tasks satisfactorily.
[0068] Specifically, the difference between testing work metrics and task production metrics is calculated, and the absolute value of this difference is taken to obtain the metric difference value. When the testing work metrics exceed the task production metrics, the difference is positive. If the metric difference exceeds a preset threshold, it indicates that the software testers' software testing task execution is far better than expected, suggesting an unreasonable task evaluation rule. In this case, the task evaluation rule needs to be optimized. Optimization methods could include revising the calculation rules for testing efficiency, test case output rate, and defect rate. Taking testing efficiency as an example, the aforementioned testing efficiency difference can be weighted to obtain the analysis results, where the weight can be less than 1.
[0069] If the testing performance metrics equal the task production metrics, the task evaluation rules are reasonable. However, if the testing performance metrics are less than the task production metrics, the difference is negative, and the absolute value of this difference is the metric difference. If the metric difference exceeds a preset threshold, it indicates that the software testers' performance in executing the software testing tasks is far below expectations, suggesting that the task evaluation rules are unreasonable. In this case, the task evaluation rules need to be optimized. Optimization methods could include improving testing efficiency, test case output rate, and defect rate in the analysis results.
[0070] When the difference between the above indicators is less than the preset threshold, it indicates that the task evaluation rules are reasonable. The difference between the indicators can be used to measure the performance of software testers in their software testing tasks.
[0071] Understandably, the preset threshold here can be updated according to the actual situation, or it can be set by the user. The specific implementation method is not limited here.
[0072] In some embodiments, adjusting task evaluation rules based on indicator differences includes:
[0073] Optimization prompts are generated based on the differences in indicators to refine the task evaluation rules.
[0074] In response to optimization instructions generated based on optimization prompts, the task evaluation rules are updated.
[0075] In this embodiment, when it is necessary to provide optimization prompts for the task evaluation rules, optimization prompt information can be generated to prompt staff to optimize the task evaluation rules. The optimization prompt information can be sent via SMS, voice, telephone, email, etc., and can also carry the indicator difference value, so that when the staff receives the optimization prompt information, they can make a reasonable optimization plan based on the indicator difference value.
[0076] The optimization command generated based on the optimization prompt information can be an operation to adjust the task evaluation rules. After executing the optimization command, the task evaluation rules can be adjusted. Alternatively, the optimization command can also be a new task evaluation rule. Upon receiving the new task evaluation rule, the old task evaluation rule can be replaced with the new one. The specific implementation method can be selected according to actual needs and is not limited here.
[0077] For example, the optimization prompt message may also include optimization suggestions. After receiving these suggestions, users can directly select them to optimize the task evaluation rules, or they can choose to make adjustments based on the suggestions to further optimize the task evaluation rules. In this way, by providing a basis for optimizing the task evaluation rules, users can accurately grasp the degree of optimization, making the optimized task evaluation rules more reasonable.
[0078] As mentioned above, by evaluating software testing tasks and the work performance of software testers, the task evaluation rules are dynamically and continuously updated according to the actual situation to form a closed-loop management system.
[0079] In some embodiments, after determining whether the difference between the test performance metrics and the task production metrics is greater than a preset threshold, the method further includes:
[0080] If not, then determine whether the test work indicators match the task production indicators;
[0081] Visual charts are generated based on test performance metrics, task production metrics, and test data for presentation.
[0082] In this embodiment, if the test performance metrics match the task production metrics, it indicates that the task evaluation rules are reasonable and no optimization is needed. Visual charts can be generated directly based on the test performance metrics, task production metrics, and test data.
[0083] Among them, the visual charts can take the form of pie charts, column charts, bar charts, line charts, donut charts, histograms, etc.
[0084] Furthermore, analytical data can be generated based on test work indicators, task production indicators, and test data. This analytical data can be mapped to each test case, software test task, or software tester. For example, it can take the form of: what software test tasks a software tester completed, how long it took, what their test work indicators are, what their task production indicators are, what the difference is between the test work indicators and the task production indicators, what types and numbers of defects occurred during the testing process, and then evaluate the software tester's work performance based on each indicator.
[0085] The visualization charts can also display the completion status of internal tasks by department or group, or show the contributions of multiple software testers to a software testing task. Of course, data such as completion time and software version can also be displayed. Since the display method is optional, it will not be described in detail.
[0086] In addition, the visualization charts provided in this embodiment can also be displayed on the user interface, allowing users to perform data filtering, data statistics, and chart display operations based on the visualization charts. The conditions for data filtering operations can be, for example, version, time, group, etc.
[0087] When the visual charts are displayed on the user interface, they can also be shown on an H5 page. An export button is also included to generate offline chart or text data.
[0088] In summary, regarding the content mentioned in the above embodiments, a schematic diagram is provided here to fully explain the details of the embodiments of this application. Please refer to... Figure 2 , Figure 2This is a detailed schematic diagram illustrating the software testing method provided in an embodiment of this application. The method involves acquiring test data for a software testing task, including the number of test cases, test time, and number of defects. It also involves acquiring task evaluation rules for the software testing task, including test efficiency, test case output rate, and defect rate. The test data is reviewed and analyzed using these task evaluation rules to obtain analysis results. These results are then quantified using preset quantification rules to obtain testing performance indicators. These performance indicators are matched with task output indicators; if a match is successful, a visual chart is created; otherwise, optimization prompts are sent.
[0089] As can be seen from the above, the software testing management method proposed in this embodiment of the invention can automatically collect test data, compare the test data with task evaluation rules, and efficiently and effectively review and analyze the test data. The analysis results are then quantified to obtain test performance indicators. Simultaneously, various defects during the testing process are statistically analyzed to obtain task production indicators, which are then matched with the test performance indicators. When the two match, a report is generated and displayed to the manager on the user interface for easy management. When the two do not match, optimization prompts are pushed to the personnel who formulated the task evaluation rules, providing optimization suggestions so that they can optimize the rules. This achieves fully online, process-oriented management of software testing tasks, improving the efficiency of management of software testing personnel.
[0090] One embodiment also provides a software testing management system. See also... Figure 3 , Figure 3 A schematic diagram of the structure of a software testing management system 200 provided in an embodiment of this application. The software testing management system 200 includes:
[0091] The software test coordination module 201 is used to collect test data for software test tasks.
[0092] The rule maintenance module 202 is used to configure task evaluation rules for software testing tasks and to update the task evaluation rules in response to optimization instructions.
[0093] The software test management module 203 is used to review and analyze test data according to task evaluation rules to obtain the analysis results of the test data; and to quantify the analysis results according to preset quantification rules to obtain the test work indicators of the analysis results; and to match the test work indicators with the task production indicators to obtain the matching results, and to determine whether to adjust the task evaluation rules based on the matching results.
[0094] The results display module 204 is used to provide a user interface and display the data obtained through the software test management module 203 on the user interface.
[0095] Among them, the input data and generated data of the software test coordination module 201 can be maintained by software test staff, the formulation and updating of task evaluation rules of the rule maintenance module 202 can be maintained by the rule setter, the software test management module 203 can be maintained by the backend server, and the result display module 204 can be maintained and operated by the administrator.
[0096] For specific implementation methods, please refer to the content mentioned above, which will not be repeated here.
[0097] In some embodiments, test data includes: the number of test cases, test time, and the number of test defects; task evaluation rules include evaluation of test efficiency, test case output rate, and defect rate; the software test management module 203 is further used for:
[0098] The number of test cases and test time are reviewed and analyzed based on test efficiency to obtain the test efficiency difference in the test data; and...
[0099] The number of test cases and the number of test defects are reviewed and analyzed based on the test case output rate to obtain the test defect difference in the test data; and...
[0100] The defect rate is used to review and analyze the number of test defects and the number of test cases to obtain the defect rate difference of the test data.
[0101] In some embodiments, the software test management module 203 is further configured to:
[0102] According to the weight coefficients indicated by the preset quantification rules, the corresponding weight coefficients are assigned to the test efficiency difference, test defect difference, and defect rate difference, respectively.
[0103] According to the statistical function indicated by the preset quantification rules, the test efficiency difference, test defect difference, and defect rate difference are statistically analyzed based on the corresponding weight coefficients to obtain the test work indicators of the analysis results.
[0104] In some embodiments, the software test management module 203 is further configured to:
[0105] Determine whether the difference between the test work indicators and the task production indicators is greater than a preset threshold. The task production indicators are used to measure the preset defects of the software test tasks.
[0106] If so, it is determined that the test work indicators and task production indicators do not match, and the task evaluation rules are adjusted according to the difference in indicators.
[0107] In some embodiments, the software test management module 203 is further configured to:
[0108] Optimization prompts are generated based on the differences in indicators to refine the task evaluation rules.
[0109] In response to optimization instructions generated based on optimization prompts, the task evaluation rules are updated.
[0110] In some embodiments, after determining whether the difference between the test performance indicators and the task production indicators is greater than a preset threshold, the software test management module 203 is further configured to:
[0111] If not, then determine whether the test work indicators match the task production indicators;
[0112] Visual charts are generated based on test performance metrics, task production metrics, and test data for presentation.
[0113] In some embodiments, the software test management module 203 is further configured to:
[0114] If the test work indicators are determined to match the task production indicators, a visualization chart is generated based on the test work indicators, task production indicators, and test data, and the visualization chart is sent to the result display module 204 for display.
[0115] If it is determined that the test work indicators do not match the task production indicators, then an optimization prompt message is generated for the task evaluation rules based on the indicator difference, and the optimization prompt message is pushed to the rule maintenance module 202 for prompting.
[0116] In some embodiments, the rule maintenance module 202 is used for:
[0117] Receive rule setting instructions, and determine task evaluation rules for test efficiency, test case output rate, and defect rate based on the rule setting instructions; and,
[0118] Receive optimization instructions generated based on optimization prompts, and update the task evaluation rules for test efficiency, test case output rate, and defect rate according to the optimization instructions.
[0119] Among these, the rule-makers can modify the task evaluation rules individually at any time, or add new task evaluation rules, or delete task evaluation rules.
[0120] In some embodiments, the software test coordination module 201 is further configured to:
[0121] The number of test cases received as input, the number of business requirements, and the number of R&D test tasks are all considered.
[0122] The statistics include the number of test cases, the number of business requirements, or the number of R&D test tasks, the test time during execution, and the number of test defects.
[0123] For specific implementation methods, please refer to the content mentioned above, which will not be repeated here.
[0124] In some embodiments, the result display module 204 is further configured to:
[0125] Display the visual charts received from the software test management module 203.
[0126] The visualization charts can be displayed on the user interface corresponding to the software test management module 203, allowing administrators to filter and analyze the data. Specific implementation details are as mentioned above and will not be repeated here.
[0127] For example, the results display module 204 is also used for:
[0128] Receive search instructions, and retrieve the corresponding data from the software test management module 203 according to the search instructions and display it on the user interface.
[0129] Of course, the user interface also provides a search window. Users can search for a certain item in the search window, retrieve the corresponding record, and display the record on the user interface. This method can quickly locate the content that the user needs to query, which is extremely convenient.
[0130] It should be noted that the software test management system 200 provided in this application embodiment belongs to the same concept as the software test management method in the above embodiment. The software test management system 200 can implement any of the methods provided in the software test management method embodiment. For details of its implementation process, please refer to the software test management method embodiment, which will not be repeated here.
[0131] As can be seen from the above, the software testing management system 200 provided in this embodiment automatically collects test data and compares it with task evaluation rules. This enables efficient and high-quality review and analysis of test data, and quantifies the analysis results to obtain test work indicators. Simultaneously, it statistically analyzes various defects during the testing process to obtain task production indicators, and then matches the test work indicators with the task production indicators. When the two match, a report is generated for the manager and displayed on the user interface, facilitating manager interaction. When the two do not match, optimization prompts are pushed to the personnel who formulated the task evaluation rules, providing optimization suggestions so that they can optimize the rules. This achieves fully online, process-oriented management of software testing tasks, improving the manager's efficiency in managing software testing personnel. Furthermore, it enables multi-device operation without requiring specific personnel to operate corresponding modules within the software testing management system, facilitating collaborative work, simplifying management, and making the workflow more streamlined and intelligent. It also achieves the technical effects of the software testing management method mentioned in the above embodiment.
[0132] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be performed by instructions, or by instructions controlling related hardware. These instructions can be stored in a computer-readable storage medium and loaded and executed by a processor.
[0133] Therefore, this application provides a computer-readable storage medium. Those skilled in the art will understand that all or part of the steps in the methods of the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, it includes the following steps:
[0134] Acquire test data for software testing tasks, and configure task evaluation rules for software testing tasks;
[0135] The test data is reviewed and analyzed according to the task evaluation rules to obtain the analysis results of the test data.
[0136] The analysis results are quantified according to preset quantification rules to obtain the test work indicators of the analysis results;
[0137] The test work indicators are matched with the task production indicators to obtain the matching results, and the task evaluation rules are adjusted based on the matching results.
[0138] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.
[0139] The aforementioned storage medium can be ROM / RAM, magnetic disk, optical disk, etc. Since the computer program stored in this storage medium can execute the steps of any of the software test management methods provided in the embodiments of this application, it can achieve the beneficial effects that any of the software test management methods provided in the embodiments of this application can achieve, as detailed in the preceding embodiments, and will not be repeated here.
[0140] The software testing management method, storage medium, and system provided in the embodiments of this application have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this application. The description of the above embodiments is only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.
Claims
1. A software test management method, characterized in that, Applied to a software testing management system, the method includes: Acquire test data for software testing tasks, and configure task evaluation rules for the software testing tasks; The test data is reviewed and analyzed according to the task evaluation rules to obtain the analysis results of the test data. The analysis results are quantified according to preset quantification rules to obtain the test performance indicators of the analysis results; The test work indicators are matched with the task production indicators to obtain the matching results, and the task evaluation rules are adjusted based on the matching results. The test data includes: the number of test cases, the test time, and the number of test defects. The task evaluation rules include evaluation of test efficiency, test case output rate, and defect rate. The step of reviewing and analyzing the test data according to the task evaluation rules to obtain the analysis results of the test data includes: Based on the test efficiency, the number of test cases and the test time are reviewed and analyzed to obtain the test efficiency difference of the test data; and... Based on the test case output rate, the number of test cases and the number of test defects are reviewed and analyzed to obtain the test defect difference of the test data; and... Based on the defect rate, the number of test defects and the number of test cases are reviewed and analyzed to obtain the defect rate difference of the test data. The step of quantifying the analysis results according to preset quantification rules to obtain the test performance indicators of the analysis results includes: According to the weighting coefficients indicated by the preset quantization rules, the test efficiency difference, the test defect difference, and the defect rate difference are respectively assigned corresponding weighting coefficients; According to the statistical function indicated by the preset quantification rule, the test efficiency difference, the test defect difference, and the defect rate difference, which are assigned corresponding weight coefficients, are statistically analyzed to obtain the test work indicators of the analysis results.
2. The software test management method according to claim 1, characterized in that, The step of matching the test performance indicators with the task production indicators to obtain a matching result, and determining whether to adjust the task evaluation rules based on the matching result, includes: Determine whether the difference between the test work indicator and the task production indicator is greater than a preset threshold, wherein the task production indicator is used to measure the preset defects of the software test task; If so, it is determined that the test work indicators and the task production indicators do not match, and the task evaluation rules are adjusted according to the difference in indicators.
3. The software testing management method according to claim 2, characterized in that, The step of adjusting the task evaluation rules based on the difference in the indicators includes: Based on the difference in the indicators, optimization prompts are generated to optimize the task evaluation rules; In response to the optimization instructions generated based on the optimization prompts, the task evaluation rules are updated.
4. The software test management method according to claim 2 or 3, characterized in that, After determining whether the difference between the test work indicator and the task production indicator is greater than a preset threshold, the method further includes: If not, then it is determined that the test work indicators match the task production indicators; Visual charts are generated based on the test work indicators, the task production indicators, and the test data for display.
5. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is run on a computer, it causes the computer to perform the software test management method as described in any one of claims 1 to 4.
6. A software testing management system, characterized in that, The software testing management system includes: The software test coordination module is used to collect test data for software testing tasks. The rule maintenance module is used to configure task evaluation rules for the software testing task, and to update the task evaluation rules in response to optimization instructions; The software testing management module is used to review and analyze the test data according to the task evaluation rules to obtain the analysis results of the test data; and to quantify the analysis results according to preset quantification rules to obtain the test work indicators of the analysis results; and to match the test work indicators with the task production indicators to obtain the matching results, and to determine whether to adjust the task evaluation rules based on the matching results. The results display module is used to provide a user interface and display the data obtained through the software test management module on the user interface. The test data includes: the number of test cases, test time, and the number of test defects. The task evaluation rules include assessments of test efficiency, test case output rate, and defect rate. The software test management module is also used for: The number of test cases and test time are reviewed and analyzed based on test efficiency to obtain the test efficiency difference in the test data; and... The number of test cases and the number of test defects are reviewed and analyzed based on the test case output rate to obtain the test defect difference in the test data; and... The defect rate is used to review and analyze the number of test defects and the number of test cases to obtain the defect rate difference of the test data. The software test management module is also used for: According to the weight coefficients indicated by the preset quantification rules, the corresponding weight coefficients are assigned to the test efficiency difference, test defect difference, and defect rate difference, respectively. According to the statistical function indicated by the preset quantification rules, the test efficiency difference, test defect difference, and defect rate difference are statistically analyzed based on the corresponding weight coefficients to obtain the test work indicators of the analysis results.
7. The software testing management system according to claim 6, characterized in that, The software test management module is also used for: If it is determined that the test work indicators match the task production indicators, a visualization chart is generated based on the test work indicators, the task production indicators, and the test data, and the visualization chart is sent to the result display module for display. If it is determined that the test work indicators and the task production indicators do not match, then optimization prompt information is generated for the task evaluation rules based on the difference between the test work indicators and the task production indicators, and the optimization prompt information is pushed to the rule maintenance module for prompting.
8. The software testing management system according to claim 7, characterized in that, The rule maintenance module is used for: Receive rule setting instructions, and determine task evaluation rules for test efficiency, test case output rate, and defect rate based on the rule setting instructions; and, Receive optimization instructions generated based on the optimization prompts, and update the task evaluation rules for the test efficiency, the test case output rate, and the defect rate based on the optimization instructions.
9. The software testing management system according to claim 7, characterized in that, The software testing coordination module is also used for: The number of test cases received as input, the number of business requirements, and the number of R&D test tasks are all considered. The test time and number of test defects during the execution of the number of test cases, the number of required business processes, or the number of R&D test tasks are statistically analyzed.
Citation Information
Patent Citations
Mobile application crowdsourcing test report automatic evaluation method and computer storage medium
CN110928764A
Workload evaluation method and device, electronic equipment and readable storage medium
CN112486788A
