Software testing method, software testing device and computer readable storage medium

By determining the scope of test cases based on the software function tree and function points, combining parameters such as defect resolution, functional point test coverage and test execution pass rate, the problem that the software test quality evaluation results cannot take into account accuracy and efficiency, and achieve high efficiency , accurate software testing and evaluation.

CN119046150APending Publication Date: 2024-11-29WUHAN UNITED IMAGING METAHEALTHCARE CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411103449.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-12
Publication Date
2024-11-29

AI Technical Summary

Technical Problem

In the prior art, the software test quality evaluation results cannot take into account both accuracy and efficiency, and it is difficult to quickly obtain accurate test cases and software test results.

Method used

Test quality is evaluated by determining the range of test cases based on the software function tree and function points, performing software tests to determine test scores, and using parameters such as defect resolution, functional point test coverage and test execution pass rate.

Benefits of technology

It improves the efficiency and accuracy of software testing, ensures the comprehensiveness and accuracy of test results, and solves the problem that quality evaluation results cannot take into account both accuracy and efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119046150A_ABST
    Figure CN119046150A_ABST
Patent Text Reader

Abstract

The invention relates to a software testing method, a software testing device and a computer readable storage medium, and the method comprises the steps: for target software, determining a test case range according to a software function tree and / or software function points; determining a plurality of test cases based on the test case range; and executing software testing on the plurality of test cases, and determining a test score. By adopting the method, the accuracy and efficiency of a software test quality evaluation result can be considered.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of software testing, and in particular to a software testing method, a software testing device, and a computer-readable storage medium. Background Art

[0002] Under the current software product function tree development model, it is necessary to speed up the release verification efficiency and ensure that the software test has clear test verification feedback. Therefore, it is necessary to conduct quality scoring and evaluation on each software test version, and archive the qualified versions into the product pool to provide a basis for subsequent product online delivery evaluation.

[0003] In the related technology, a test case scoring model is trained based on the feature information of historical test cases and the defect discovery rate of historical test cases, and the test quality scoring results are given with the help of the test daily work item association information. It is difficult to quickly obtain accurate test cases, and it is also impossible to obtain accurate software testing results based on the test cases.

[0004] There is currently no effective solution to the problem that software testing quality assessment results in related technologies cannot take into account both accuracy and efficiency. Summary of the invention

[0005] Based on this, it is necessary to provide a quality assessment method, device, equipment and storage medium that can solve the problem that software testing quality assessment results cannot take into account both accuracy and efficiency in response to the above technical problems.

[0006] In a first aspect, a software testing method is provided in this embodiment, the method comprising:

[0007] For the target software, determine the scope of test cases based on the software function tree and / or software function points;

[0008] Based on the test case scope, determining a plurality of test cases;

[0009] Software testing is performed on the multiple test cases to determine a test score.

[0010] In some of the embodiments, testing the plurality of test cases and determining the test scores includes:

[0011] Performing software testing on the plurality of test cases and determining one or more test evaluation parameters;

[0012] The test score is determined based on the one or more test evaluation parameters.

[0013] In some embodiments, the one or more test evaluation parameters include a defect resolution level of the target software, and the defect resolution level is determined by the following steps:

[0014] Determining a first defect generated by the target software within a first historical update cycle;

[0015] The defect resolution degree is determined according to a quantitative relationship between the number of first defects that are determined to have been resolved through testing and the total number of the first defects.

[0016] In some embodiments, the one or more test evaluation parameters include a defect resolution level of the target software, and the defect resolution level is determined by the following steps:

[0017] determining a second defect generated by the target software within a second historical update cycle;

[0018] The defect resolution degree is determined according to the number of second defects that are determined to be unresolved through testing and the weight of each of the second defects that are unresolved.

[0019] In some embodiments, the one or more test evaluation parameters include function point test coverage, and the function point test coverage is determined by the following steps:

[0020] determining a total number of test cases of the plurality of test cases;

[0021] The function point test coverage is determined according to a quantitative relationship between the number of test cases associated with the target function point of the target software in the multiple test cases and the total number of test cases.

[0022] In some of the embodiments, the one or more test evaluation parameters include a test execution pass rate, including:

[0023] The test execution pass rate is determined according to a quantitative relationship between the number of test cases that are determined to have passed the test and the total number of test cases that have been tested.

[0024] In some embodiments, the one or more test evaluation parameters are determined by the following steps:

[0025] Obtaining a correspondence between each test case in the plurality of test cases and a functional point of the target software, as well as software requirements and corresponding defects that can be realized by each functional point in the target software;

[0026] storing the function points in association with corresponding test cases, software requirements and defects;

[0027] According to the association between the function point and the test case, software requirements and defects and the test results of the multiple test cases, the degree of resolution of each defect, the number of first test cases whose test results meet the preset standard, and the number of second test cases associated with the target function point are determined, wherein the preset standard is used to indicate that the first test case can meet the software requirement associated with it.

[0028] In some of the embodiments, for the target software, determining the scope of the test cases according to the software function tree and / or function points includes:

[0029] According to the changed function points among the function points, the test case scope is determined to include at least the test cases associated with the changed function points.

[0030] In a second aspect, a software testing device is provided in this embodiment, the device comprising:

[0031] An execution module is used to determine the scope of test cases for the target software according to the software function tree and / or software function points;

[0032] An acquisition module, used for determining a plurality of test cases based on the test case range;

[0033] The scoring module is used to perform software testing on the multiple test cases and determine the test scores.

[0034] According to a third aspect, a computer-readable storage medium is provided in this embodiment, on which a computer program is stored. When the computer program is executed by a processor, the software testing method described in the first aspect is implemented.

[0035] The software testing method, software testing device and computer-readable storage medium can quickly obtain the test case scope of the target software based on the software function tree and / or software function points, thereby improving the software testing efficiency. Multiple test cases are obtained based on the test case scope to meet the test requirements and improve the test accuracy, thereby solving the problem that the software testing quality assessment results cannot take into account both accuracy and efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] Figure 1 An application environment diagram of a software testing method in an embodiment;

[0037] Figure 2 A flowchart of a software testing method in one embodiment;

[0038] Figure 3 A schematic diagram of the structure of a software function tree in one embodiment;

[0039] Figure 4is a flowchart of a software testing method in another embodiment;

[0040] Figure 5 A structural block diagram of a software test in an embodiment;

[0041] Figure 6 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0042] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0043] The software testing method provided in the embodiment of the present application can be applied to Figure 1 In the application environment shown. Among them, the terminal 102 communicates with the server 104 through the network. The data storage system can store the data that the server 104 needs to process. The data storage system can be integrated on the server 104, or it can be placed on the cloud or other network servers. Through the interaction of the terminal 102, the server 104, or the terminal 102 and the server 104, the execution results of the software testing method are evaluated to obtain the quality evaluation results of the target software. Among them, the software testing method and its execution results and quality evaluation results can all be stored in the data storage system. Among them, the terminal 102 can be but not limited to various personal computers, laptops, smart phones, and tablet computers. The server 104 can be implemented with an independent server or a server cluster consisting of multiple servers.

[0044] In one embodiment, Figure 2 As shown, a software testing method is provided, which is applied to Figure 1 The terminal 102 in the example is used as an example to illustrate, and the following steps are included:

[0045] Step S202: for the target software, determine the scope of the test cases according to the software function tree and / or software function points.

[0046] Among them, the software function tree clearly describes the various functions of the target software through a tree structure, and the test case scope is used to indicate the functional scope of the target software that needs to be tested. Each node in the software function tree represents a function, module or page of the target software. Optionally, the root node in the software function tree represents the entire target software, or the main page of the target software, or the main module in the target software; each branch node in the software function tree represents the subordinate sub-function of the upper node. For example, the software function tree can be divided and described based on the order of pages, modules, and sub-functions. Optionally, the root node in the software function tree represents or corresponds to the page of the software, and the branch node represents or corresponds to each module on the page, and the leaf node represents or corresponds to the sub-function in the module. The software function tree can also be divided based on other methods, which are not limited here. Different software function points are used to describe different software function requirements.

[0047] Optionally, one or more software functions that need to be tested in the target software can be quickly determined through a software function tree, a software function point, or a combination of software function points in a software function tree. Among them, the function that needs to be tested can be a function point specified by the user, a function point with defects, a function that has changed in the current version of the target software compared to the previous version, etc. Based on the selected software function, a corresponding test case range can be obtained. For example, the system automatically or the user manually determines that a specific sub-function (for example, a changed function point or a suspected problematic function point) needs to be tested and verified, and then the system automatically, semi-automatically or the user manually determines the association relationship with other nodes based on the position or level of the node corresponding to the sub-function in the software function tree, and then determines the nodes associated with it, and then determines the test case range based on the node corresponding to the specific sub-function and other nodes associated with it. For example, according to the position of the node corresponding to the changed function point in the software function tree, the nodes associated with it are determined, so as to determine the use case scope corresponding to the changed function point as the change use case scope. Then, according to the position of the node corresponding to the function point required for software operation in the software function tree, the nodes associated with it are determined, so as to determine the use case scope corresponding to the function point required for software operation as the regression use case scope. Then, the change use case scope and the regression use case scope are combined as the test case scope.

[0048] Step S204, determining multiple test cases based on the test case range.

[0049] The functions of the selected target software are different, and the corresponding test case scopes are different. Optionally, the creation of test cases is guided based on the test case scope, so that multiple test cases meet the test case scope. Alternatively, based on the test case scope, test cases are selected from pre-set test cases to obtain multiple test cases that meet the test case scope.

[0050] Step S206, executing software testing on multiple test cases to determine test scores.

[0051] Among them, a test case is a collection of test steps, which is used to verify whether the function to be tested in the target software can work as expected. Optionally, the software test results of multiple test cases can be combined to obtain the corresponding test score. Alternatively, software testing is performed based on multiple test cases respectively, and the score corresponding to each test case is obtained according to the test results of each test case, and the multiple scores corresponding to the multiple test cases are combined (for example, weighted addition, averaging after removing interference values ​​or unreasonable values, etc.) to determine the test score.

[0052] In the above software testing method, the test case scope of the target software is obtained quickly and accurately based on the software function tree and / or software function points, thereby improving the software testing efficiency. Based on the test case scope, multiple test cases that meet the test case scope can be obtained, ensuring that the test score of the target software function to be tested can be accurately obtained based on multiple test cases, ensuring the comprehensiveness of software testing, and improving test accuracy, thereby solving the problem that the software testing quality assessment results cannot take into account both accuracy and efficiency.

[0053] In one embodiment, testing multiple test cases to determine a test score includes: performing software testing on the multiple test cases to determine one or more test evaluation parameters; and determining a test score based on the one or more test evaluation parameters.

[0054] Among them, the test evaluation parameter is a parameter obtained according to the test case execution result, which is used to indicate whether the test case execution result meets the expected result of the software function execution. Optionally, the parameter value can be directly used as the evaluation score of the parameter and applied to the calculation of the test score. Alternatively, the test evaluation parameter value can be evaluated based on the specified standard to obtain the corresponding score. The test score can be obtained by combining the values ​​of each test evaluation parameter or the scores corresponding to each test evaluation parameter.

[0055] Furthermore, corresponding weights may be set for each test evaluation parameter, and each parameter determines the quality of the software testing method according to multiple scores and weights corresponding to each score. The weights corresponding to different scores may be the same or different. Optionally, a weighted sum is performed on multiple scores based on the weights corresponding to each score, and the software testing quality is determined according to the result of the weighted sum.

[0056] Additionally or alternatively, it is also possible to confirm whether each test evaluation parameter is an interference value or an unreasonable value and perform a weighted sum or average after removing the interference values ​​and unreasonable values. For example, values ​​in the test evaluation parameters that have little impact on the software function, do not change significantly, or are of no concern to the customer can be removed as interference values, and / or values ​​in the test evaluation parameters that are obviously too large or too small can be treated as unreasonable values. Then, after removing the interference values ​​and unreasonable values, the remaining test evaluation parameters are weightedly summed or averaged to determine the test score and evaluate the software testing quality.

[0057] In this embodiment, the target software is tested by using multiple test evaluation parameters, which increases the test dimension, thereby improving the accuracy of the software test quality evaluation results. At the same time, the software testing method is simple, which solves the problem that the software test quality evaluation results cannot take into account both accuracy and efficiency.

[0058] Furthermore, in some embodiments, the test evaluation parameters may include one or more of the following parameters: the degree to which the software testing method solves each defect in the target software, the coverage of the function point test, and the test execution pass rate. The following describes the method for obtaining each parameter.

[0059] In the execution result of the software testing method, the higher the degree of resolution of each defect in the target software, the better the quality of the target software test version. For example, the degree of resolution of each defect in the target software by the software testing method can be obtained based on the proportion of the number of resolved defects. For example, the higher the ratio of the number of resolved defects to the total number of defects, the higher the degree of resolution of the defects, where the total number of defects can be equal to the number of resolved defects plus the number of unresolved defects. For example, the degree of resolution of each defect in the target software by the software testing method can also be obtained based on the importance of the resolved defects. For example, the higher the importance of the resolved defects, the higher the degree of resolution of the defects. Alternatively, the degree of resolution of the defects can be determined by combining the number of defects resolved by the software testing method and the importance of the defects.

[0060] Based on this, in one embodiment, one or more test evaluation parameters include the degree of defect resolution of the target software, and the degree of defect resolution can be determined by the following steps: determining the first defect generated by the target software in the first historical update cycle; determining the degree of defect resolution based on the quantitative relationship between the number of first defects determined to have been resolved through testing and the total number of first defects.

[0061] The quantitative relationship between the number of resolved first defects and the total number of first defects includes, but is not limited to, the proportion of the number of resolved first defects in the total number of first defects, the difference relationship between the number of resolved first defects and the total number of first defects, the size relationship between the number of resolved first defects and the total number of first defects, etc. Functional points in the target software can be updated as the software version changes. The first historical update cycle is the time interval from the release of any specified historical version of the target software to the present.

[0062] Exemplarily, the time interval from the last historical version of the target software to the present is taken as the first historical update period. The defect resolution rate of the current version of the target software for historical defects is obtained by calculating the quotient of the number of first defects resolved in the first historical update period and the total number of first defects.

[0063] Furthermore, the test score of the software testing method is determined based on the degree of defect resolution. The degree of defect resolution can be directly used as the test score, or the defect resolution rate can be multiplied by a corresponding coefficient to calculate the test score. In this embodiment, the defect resolution rate of the target software is determined based on the quantitative relationship between the number of first defects that have been resolved and the total number of first defects, and the degree of defect results is obtained to achieve accurate testing of the target software.

[0064] In one embodiment, one or more test evaluation parameters include a defect resolution degree of the target software, and the defect resolution degree can be determined by the following steps: determining a second defect generated by the target software within a second historical update cycle; determining the defect resolution degree based on the number of second defects that have been determined to be unresolved through testing and the weight of each unresolved second defect.

[0065] Among them, the second historical update cycle is the time interval from the release of any specified historical version of the target software to the present. The second historical update cycle and the first historical update cycle may be the same or different. Exemplarily, the time interval from the release of the initial version of the target software to the present is taken as the second historical update cycle. The weight of the second defect is used to indicate the severity of the second defect. Optionally, the number of second defects can be weighted and summed with the weight of the second defect. Alternatively, the second defects can also be grouped according to the weights of each unresolved second defect, and the weights corresponding to the second defects in the same group are the same, and the weights corresponding to different groups are different. The number of second defects contained in each group is obtained respectively, and after the number of second defects in the current group is multiplied by the weight of the second defect of the current group, the results obtained by multiplying multiple groups are summed, and the result based on the weighted summation is used as the degree of defect resolution. Further, after determining the degree of defect resolution, the result of the weighted summation can be directly used as the test score, or the result of the weighted summation can be multiplied by the corresponding coefficient to calculate the test score.

[0066] In this embodiment, based on the number of unresolved second defects determined through testing and the weight of each unresolved second defect, it is evaluated whether the current version of the target software can resolve important defects, the degree of defect results is obtained, and accurate testing of the target software is achieved.

[0067] Furthermore, to improve the accuracy of the software test evaluation results, the first score of the software test can be obtained according to the quantitative relationship between the number of first defects solved by the software test method and the total number of first defects. At the same time, according to the number of second defects that the software test method fails to solve and the weight of each second defect that fails to solve, the second score of the software test method is obtained, and the degree of defect resolution is determined by combining the first score and the second score. Exemplarily, corresponding weights are set for the first score and the second score, and the test score is obtained by combining the two scores.

[0068] The higher the coverage of the target software to be tested functions by the test scopes corresponding to the multiple test cases, the more accurate the software test evaluation results are. Based on this, in one embodiment, the one or more test evaluation parameters include function point test coverage, and the function point test coverage is determined by the following steps: determining the total number of test cases of the multiple test cases; determining the function point test coverage according to the quantitative relationship between the number of test cases associated with the target function points of the target software in the multiple test cases and the total number of test cases.

[0069] Wherein, the target function point is the function point to be tested in the target software. When the number of the total number of test cases remains unchanged, the more test cases associated with the target function point of the target software in the multiple test cases, the higher the coverage of the function point; otherwise, the lower. The quantitative relationship between the number of test cases associated with the target function point of the target software in the multiple test cases and the total number of test cases includes but is not limited to the proportional relationship, difference relationship, size relationship, etc. between the two. The higher the test coverage indicated by the quantitative relationship, the more reliable the execution result of the software testing method. Exemplarily, the function point test coverage is obtained according to the quotient of the number of test cases associated with the target function point of the target software in the multiple test cases and the total number of test cases. The higher the quotient of the number of test cases associated with the target function point of the target software in the multiple test cases and the total number of test cases, the higher the coverage of the target function point by each test case, and the more reliable the execution result of the software testing method. Further, after determining the test coverage, the test coverage can be directly used as the test score, or the test coverage can be multiplied by the corresponding coefficient to calculate the test score. In this embodiment, the software test score is obtained according to the test coverage of the software testing method to obtain an accurate software test evaluation result.

[0070] In one embodiment, the one or more test evaluation parameters include a test execution pass rate, including: determining the test execution pass rate according to a quantitative relationship between the number of test cases determined to have passed the test and the total number of test cases tested.

[0071] Among them, when the total number of test cases remains unchanged, the higher the number of passed test cases, the higher the test execution pass rate, and the higher the software score; conversely, the target software quality score is low. The quantitative relationship between the number of test cases determined to have passed the test and the total number of test cases tested includes but is not limited to the proportional relationship, difference relationship, size relationship, etc. between the two. Optionally, the test execution pass rate is determined based on the quotient of the number of test cases determined to have passed and the total number of test cases tested. Further, after determining the test execution pass rate, the value of the test execution pass rate can be directly used as the test score, or the test execution pass rate can be multiplied by the corresponding coefficient to calculate the test score.

[0072] This embodiment determines whether the to-be-tested function points corresponding to the test cases can meet the expectations of the target software according to the test execution pass rate, so as to obtain accurate software test evaluation results.

[0073] Furthermore, the test score is obtained by combining two or three parameters of the degree of resolution of each defect in the target software, the function point test coverage, and the test execution pass rate. Optionally, the values ​​of the defect resolution degree, the function point test coverage, and the test execution pass rate are integrated, and the test score is obtained according to the integrated value and the preset evaluation criteria. Alternatively, multiple evaluation criteria are set for the defect resolution degree, the function point test coverage, and the test execution pass rate, and multiple scores are obtained based on each test evaluation parameter and the corresponding evaluation criteria, and the test score is obtained by the multiple scores and the corresponding weights.

[0074] In one embodiment, one or more test evaluation parameters are determined by the following steps: obtaining the correspondence between each test case in a plurality of test cases and a functional point of the target software, as well as the software requirements and corresponding defects that can be achieved by each functional point in the target software; associating and storing the functional points with the corresponding test cases, software requirements and defects; and determining the degree of resolution of each defect, the number of first test cases whose test results meet preset standards, and the number of second test cases associated with the target functional point based on the association between the functional points and test cases, software requirements and defects, and the test results of testing the plurality of test cases, wherein the preset standards are used to indicate that the first test case can meet the software requirements associated with it.

[0075] According to the correlation and execution results between function points and test cases, software requirements and defects, the degree to which the test cases in the software testing method solve each defect is obtained, including: obtaining defects corresponding to multiple test cases, and evaluating whether the corresponding defects are solved according to the execution results of the test cases, thereby obtaining the degree to which the test cases solve each defect.

[0076] According to the association and execution results between function points and test cases, software requirements and defects, the number of first test cases whose execution results meet preset standards includes: obtaining software requirements corresponding to multiple test cases, and if the execution results of the test case meet the corresponding software requirements, then the test case is used as the first test case, thereby obtaining the number of first test cases.

[0077] According to the association relationship and execution results between the function point and the test case, software requirements and defects, the number of second test cases associated with the target function point is obtained, including: obtaining the test cases corresponding to the target function point based on the association relationship, and using these test cases as second test cases, thereby obtaining the number of second test cases.

[0078] In this embodiment, by associating and storing function points with corresponding test cases, software requirements and defects, the user can quickly determine the scope of software test cases based on software requirements and defects, thereby establishing multiple test cases associated with the test case scope; by associating and storing function points with corresponding test cases, software requirements and defects, the values ​​required to implement test evaluation parameters such as the first test case number and the second test case number can also be quickly obtained, thereby improving the efficiency of software testing.

[0079] In one embodiment, for the target software, determining the scope of test cases according to the software function tree and / or function points includes: determining the scope of test cases to include at least test cases associated with the changed function points according to the changed function points in the function points. The changed function points refer to the function points that have changed in the current version of the target software compared with the previous historical version of the target software.

[0080] The test case associated with the changed function point may be the test case corresponding to the changed function point, or may be the sum of the test case corresponding to the changed function point and the test cases corresponding to other function points associated with the changed function point.

[0081] Optionally, for the target software, the scope of the test cases is determined according to the software function tree and / or function points, including: determining the function hierarchy association relationship according to the software function tree; determining the function points to be tested according to the changed function points in the function points and the function hierarchy association relationship, the function points to be tested include the changed function points, and function points related to the changed function points in the function hierarchy association relationship; determining the scope of the test cases to include at least the test cases associated with the function points to be tested.

[0082] Among them, the functional hierarchy association relationship refers to the relationship between nodes at different levels of the software function tree. Exemplarily, the functional hierarchy association relationship can be used to indicate that in nodes at different levels of the software function tree, from the upper node to the lower node, the software's pages, modules, and sub-functions are represented respectively. Exemplarily, if the changed function point corresponds to a module of the target software, then according to the functional hierarchy association relationship, the one or more other related function points obtained can be function points corresponding to multiple sub-functions under the module, or can be other modules closely related to the execution of the module. Based on the changed function points and the function points related to the changed function points in the functional hierarchy association relationship, the obtained test cases can cover the test requirements well, thereby improving the accuracy of software testing.

[0083] Furthermore, for the target software, the scope of the test cases is determined according to the software function tree and / or function points, including: determining the functional hierarchy association relationship according to the software function tree; determining the changed function points according to the functional hierarchy relationship and the changed function requirements; and determining the scope of the test cases to include at least the test cases associated with the changed function points according to the changed function points in the function points. Among them, based on the changed function requirements, the fast selection of the changed function points in the software function tree can be realized. Exemplarily, a module of the target software is determined based on the changed function requirements, and then according to the functional hierarchy association relationship, multiple sub-function points under the module are obtained, and the multiple sub-function points under the module are used as the changed function points, thereby realizing the fast acquisition of the changed function points and improving the efficiency of software testing.

[0084] In one embodiment, the target software includes at least one software page, each software page includes at least one software module, and each software module includes at least one software function point. A software function tree can be established according to the target software, and the software function tree of the target software is divided into three levels according to software pages, software modules and software function points. The software function points are subjected to detailed requirement disassembly to obtain the requirement tasks of the software function points; the software function points are subjected to detailed test analysis to obtain the test cases of the software function points; the software function points are subjected to detailed test execution to obtain the defects of the software function points. The software function points, software requirements, test cases and defects are stored in association in the software function tree. Figure 3 Schematic diagram of the structure of a software function tree in this embodiment. Figure 3As shown, the software function tree and the test case are in a verification and verification relationship, the software requirements and defects are used to verify the quality of the software function tree, and the software function tree and the software requirements and defects are in a parent-child relationship (for example, the relationship between the parent node and the child node in the software function tree, where the parent node and the child node generally refer to the adjacent upper and lower levels in the software function tree, which are relative concepts, and a node can be used as the parent node of some nodes or as the child node of some nodes). In this embodiment, the software function tree stores the association information between the software function points, software requirements, test cases, and defects in the target software, providing a basic basis for automatic software testing quality assessment.

[0085] based on Figure 3 The software function tree of this embodiment provides another software testing method flow chart, such as Figure 4 As shown, the following steps are included:

[0086] Step S401, obtain the changed function points by changing the requirement scope. The changed requirement scope is the changed scope of the software requirements in the target software of the test version compared with the target software of the previous historical version. According to the association relationship stored in the software function tree, the changed function points corresponding to the changed requirement scope can be obtained.

[0087] Step S402, establish a software testing method by changing the function point. In addition to establishing test cases according to the changed function point, the software testing method also needs to establish regression cases according to the regression function point. The regression function point is the function point required for the target software to run. The software testing method is obtained based on the test case and the regression case.

[0088] Step S403: executing a software testing method in a specific version environment to discover defects.

[0089] Step S404: According to the software defect situation, the DI (Defect Index, defect rate) value of the remaining defects is counted.

[0090] Optionally, software defects can be obtained from the software function tree according to the function point name. Different weights are assigned to the severity of each defect, and the DI value of the residual defect is calculated according to the defect situation of the target software after executing the software testing method.

[0091] Step S405, performing multi-dimensional and multi-parameter calculations on the execution results to obtain software quality.

[0092] Optionally, a test scoring parameter value calculation model is established. The test scoring parameter value calculation model is used to infer the scope of test cases based on the changed function points, and calculate the test coverage of the changed function points. Among them, the test coverage is the quotient of the total number of test cases and the number of function points. The test execution pass rate is calculated according to the execution of the changed function case scope, wherein the test execution pass rate is the quotient of the number of passed test cases and the total number of executed test cases. The defect resolution rate of the version is calculated according to the version number associated with the test plan execution. Among them, the defect resolution rate is the quotient of the number of resolved defects and the total number of defects. Test coverage, test execution pass rate, defect resolution rate and legacy defect DI value are used as indicator judgment criteria for evaluating software quality. According to the test coverage, test execution pass rate, defect resolution rate and legacy defect DI value and the corresponding weights, the test score is calculated, and the software quality is evaluated based on the test score.

[0093] In this embodiment, after the test verification of each released software is completed, the quality of the target software can be evaluated based on multiple dimensions including function point coverage, test pass rate, defect resolution rate, and DI value of residual defects, and a test quality score can be automatically given to reduce the workload of manual statistical analysis and calculation, improve the overall release efficiency, and ensure the accuracy of version test evaluation.

[0094] Based on the same inventive concept, the embodiment of the present application also provides a quality assessment device for implementing the software testing method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in the quality assessment device embodiment of one or more software testing methods provided below can refer to the limitations on the software testing method above, and will not be repeated here.

[0095] In one embodiment, Figure 5 As shown, a quality assessment device for a software testing method is provided, comprising: an execution module, an acquisition module and a scoring module, wherein:

[0096] An execution module is used to determine the scope of test cases for the target software according to the software function tree and / or software function points;

[0097] An acquisition module is used to determine multiple test cases based on the test case range;

[0098] The scoring module is used to perform software testing on multiple test cases and determine the test scores.

[0099] In one embodiment, testing multiple test cases to determine a test score includes: performing software testing on the multiple test cases to determine one or more test evaluation parameters; and determining a test score based on the one or more test evaluation parameters.

[0100] Optionally, one or more test evaluation parameters include a degree of defect resolution of the target software, and the degree of defect resolution is determined by the following steps: determining the first defect generated by the target software within the first historical update cycle; determining the degree of defect resolution based on a quantitative relationship between the number of first defects determined to have been resolved through testing and the total number of first defects.

[0101] Optionally, one or more test evaluation parameters include a degree of defect resolution of the target software, and the degree of defect resolution is determined by the following steps: determining a second defect generated by the target software within a second historical update cycle; and determining the degree of defect resolution based on the number of second defects that have been determined to be unresolved through testing and the weight of each unresolved second defect.

[0102] Optionally, one or more test evaluation parameters include function point test coverage, and the function point test coverage is determined by the following steps: determining the total number of test cases of multiple test cases; determining the function point test coverage based on the quantitative relationship between the number of test cases associated with the target function points of the target software in the multiple test cases and the total number of test cases.

[0103] Optionally, the one or more test evaluation parameters include a test execution pass rate, including: determining the test execution pass rate according to a quantitative relationship between the number of test cases determined to have passed the test and the total number of test cases tested.

[0104] In one embodiment, one or more test evaluation parameters are determined by the following steps: obtaining the correspondence between each test case in a plurality of test cases and a functional point of the target software, as well as the software requirements and corresponding defects that can be achieved by each functional point in the target software; associating and storing the functional points with the corresponding test cases, software requirements and defects; and determining the degree of resolution of each defect, the number of first test cases whose test results meet preset standards, and the number of second test cases associated with the target functional point based on the association between the functional points and test cases, software requirements and defects, and the test results of testing the plurality of test cases, wherein the preset standards are used to indicate that the first test case can meet the software requirements associated with it.

[0105] In one embodiment, for the target software, determining the test case scope according to the software function tree and / or function points includes: according to the changed function points in the function points, determining the test case scope to include at least the test cases associated with the changed function points.

[0106] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Figure 6As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store data related to the software testing method and the target software. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a software testing method is implemented.

[0107] Those skilled in the art will understand that Figure 6 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0108] In one embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the computer program is executed by the processor, the steps in the above-mentioned microcirculation resistance value acquisition method embodiments are implemented.

[0109] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned microcirculation resistance value acquisition method embodiments are implemented.

[0110] In one embodiment, a computer program product is provided, including a computer program, which, when executed by a processor, implements the steps in the above-mentioned microcirculation resistance value acquisition method embodiments.

[0111] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited to this.

[0112] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0113] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A software testing method, characterized in that: include: For the target software, determine the scope of test cases based on the software function tree and / or software function points; Based on the test case scope, determining a plurality of test cases; Software testing is performed on the multiple test cases to determine a test score.

2. The method according to claim 1, characterized in that: Testing the multiple test cases and determining test scores, including: Performing software testing on the plurality of test cases and determining one or more test evaluation parameters; The test score is determined based on the one or more test evaluation parameters.

3. The method according to claim 2, characterized in that The one or more test evaluation parameters include a defect resolution degree of the target software, and the defect resolution degree is determined by the following steps: Determining a first defect generated by the target software within a first historical update cycle; The defect resolution degree is determined according to a quantitative relationship between the number of first defects that are determined to have been resolved through testing and the total number of the first defects.

4. The method according to claim 2, characterized in that: The one or more test evaluation parameters include a defect resolution degree of the target software, and the defect resolution degree is determined by the following steps: determining a second defect generated by the target software within a second historical update cycle; The defect resolution degree is determined according to the number of second defects that are determined to be unresolved through testing and the weight of each of the second defects that are unresolved.

5. The method according to claim 2, characterized in that: The one or more test evaluation parameters include function point test coverage, and the function point test coverage is determined by the following steps: determining a total number of test cases of the plurality of test cases; The function point test coverage is determined according to a quantitative relationship between the number of test cases associated with the target function point of the target software in the multiple test cases and the total number of test cases.

6. The method according to claim 2, characterized in that The one or more test evaluation parameters include a test execution pass rate, including: The test execution pass rate is determined according to a quantitative relationship between the number of test cases that are determined to have passed the test and the total number of test cases that have been tested.

7. The method according to claim 2, characterized in that The one or more test evaluation parameters are determined by the following steps: Obtaining a correspondence between each test case in the plurality of test cases and a functional point of the target software, as well as software requirements and corresponding defects that can be realized by each functional point in the target software; storing the function points in association with corresponding test cases, software requirements and defects; According to the association between the function point and the test case, software requirements and defects and the test results of the multiple test cases, the degree of resolution of each defect, the number of first test cases whose test results meet the preset standard, and the number of second test cases associated with the target function point are determined, wherein the preset standard is used to indicate that the first test case can meet the software requirement associated with it.

8. The software testing method according to claim 1, characterized in that: For the target software, determine the scope of test cases based on the software function tree and / or function points, including: According to the changed function points among the function points, the test case scope is determined to include at least the test cases associated with the changed function points.

9. A software testing device, characterized in that: The device comprises: An execution module is used to determine the scope of test cases for the target software according to the software function tree and / or software function points; An acquisition module, used for determining a plurality of test cases based on the test case range; The scoring module is used to perform software testing on the multiple test cases and determine the test scores.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 8 are implemented.