A software test scope determination method and device, electronic equipment and storage medium

Abstract

This invention discloses a method, apparatus, electronic device, and storage medium for determining the scope of software testing. The method includes: determining a correction coefficient based on the project attribute information and historical testing information of the software project under test; determining the evaluation value of at least one testing influencing factor within the project attribute information based on preset evaluation rules; and determining software test items in a preset test scope table based on the correction coefficient and the evaluation value. This invention enables the determination of software test items based on historical testing information and testing influencing factors. It uses measurable actual test data to compensate for the subjective uncertainty of manually determining the software testing scope, and combines the reference value of historical test data to improve the efficiency and accuracy of determining the software testing scope.

Description

Technical Field

[0001] This invention relates to the field of software testing technology, and in particular to a method, apparatus, electronic device, and storage medium for determining the scope of software testing. Background Technology

[0002] In the process of system development, performance testing serves as an important way to verify whether the system has met the preset performance indicators and to discover performance bottlenecks. It is of great guiding significance for developers to further optimize system performance.

[0003] System performance testing is generally implemented through two methods: performance testing and performance evaluation. The choice of method is primarily determined by project stakeholders through a comprehensive analysis of the project's performance testing requirements, which in turn defines the scope of the performance tests. However, this method of determining the software testing scope has the following drawbacks: First, the subjective nature of manually determining the software testing scope introduces significant uncertainty, and the performance testing requirements analysis process cannot be measured. Second, it ignores the reference value of previous system performance test results, leading to low accuracy in the determined software testing scope. Third, when the testing workload is large, this method of manually determining the software testing scope is inefficient. Summary of the Invention

[0004] This invention provides a method, apparatus, electronic device, and storage medium for determining the scope of software testing, enabling the determination of software test items based on historical test information and influencing factors. It uses measurable actual test data to compensate for the subjective uncertainty of manually determining the scope of software testing, and combines the reference value of historical test data to improve the efficiency and accuracy of determining the scope of software testing.

[0005] According to one aspect of the present invention, a method for determining the scope of software testing is provided, wherein the method includes:

[0006] The correction factor is determined based on the project attribute information and historical test information of the software project under test.

[0007] The evaluation value of at least one test influencing factor within the project attribute information is determined based on preset evaluation rules;

[0008] Software test items are determined in the preset test range table based on the correction coefficient and evaluation value.

[0009] According to another aspect of the present invention, a software testing scope determination apparatus is provided, comprising:

[0010] The correction factor module is used to determine the correction factor based on the project attribute information and historical test information of the software project under test.

[0011] The evaluation value module is used to determine the evaluation value of at least one test influencing factor within the project attribute information based on preset evaluation rules;

[0012] The test item determination module is used to determine software test items based on correction coefficients and evaluation values ​​in a preset test range table.

[0013] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:

[0014] At least one processor; and

[0015] A memory communicatively connected to the at least one processor; wherein,

[0016] The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the software test scope determination method according to any embodiment of the present invention.

[0017] According to another aspect of the present invention, a computer-readable storage medium is provided, the computer-readable storage medium storing computer instructions for causing a processor to execute and implement the software test range determination method according to any embodiment of the present invention.

[0018] The technical solution of this invention determines a correction coefficient based on the project attribute information and historical test information of the software project under test, determines the evaluation value of at least one test influencing factor within the project attribute information based on preset evaluation rules, and determines the software test items in a preset test range table based on the correction coefficient and the evaluation value. This invention achieves the determination of software test items based on historical test information and test influencing factors, using measurable actual test data to compensate for the subjective uncertainty of manually determining the software test range, and combining the reference value of historical test data to improve the efficiency and accuracy of determining the software test range.

[0019] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0020] To more clearly illustrate the technical solutions in the embodiments of the present invention, 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 the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0021] Figure 1This is a flowchart of a software testing scope determination method provided in Embodiment 1 of the present invention;

[0022] Figure 2 This is a flowchart of a method for determining the scope of software testing according to Embodiment 2 of the present invention;

[0023] Figure 3 This is a flowchart of a software testing scope determination method provided in Embodiment 3 of the present invention;

[0024] Figure 4 This is a schematic diagram of a software testing range determination device according to Embodiment 4 of the present invention;

[0025] Figure 5 This is a schematic diagram of the structure of an electronic device that implements the software testing scope determination method of this invention. Detailed Implementation

[0026] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0027] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0028] Example 1

[0029] Figure 1 This is a flowchart illustrating a method for determining the scope of software testing according to Embodiment 1 of the present invention. This embodiment is applicable to situations involving the determination of the scope of software testing. This method can be executed by a software testing scope determining device, which can be implemented in hardware and / or software and can be configured in an electronic device. Figure 1As shown in the figure, the method for determining the scope of software testing provided in this embodiment includes the following steps:

[0030] S110. Determine the correction coefficient based on the project attribute information and historical test information of the software project under test.

[0031] In this embodiment of the invention, project attribute information can be understood as the attribute information contained in the software project under test. Project attribute information may include system importance information (e.g., whether it is a core production system), transaction information (e.g., transaction complexity information, transaction customer type information, etc.), and system performance indicator requirements (e.g., concurrency requirements, response time requirements, and peak transactions per second (TPS) requirements, etc.). In some embodiments, project attribute information may include all of the above-mentioned dimensions, only some of the above-mentioned dimensions, or more dimensions; this embodiment of the invention does not impose any limitations on this. Historical test information can be understood as the actual test information obtained after previous performance tests of the software project under test. Historical test information may include information such as system importance involving a core production system, transaction customer type information indicating transactions only providing internal services, peak TPS of 50, and response time of 2 seconds, etc. In some embodiments, historical test information may include previous actual test information corresponding to the above-mentioned project attribute information. The correction coefficient can be understood as a coefficient introduced to reflect the authenticity of performance testing as much as possible when there is a deviation between ideal performance testing and actual performance testing, i.e., the difference between two performance test information.

[0032] Specifically, based on a pre-defined software project management system (which can be located locally or on a cloud server, etc.) or a software project data storage location such as a project task book, the project attribute information and historical test information of the software project under test can be obtained according to the project name, project number, and other information. For example, the project attribute information can include multi-dimensional attribute information such as system importance information, transaction information, and system performance indicator requirements information. The historical test information can include the actual test information of the project's previous performance tests. The difference between the historical test information and the current performance test information is used as a correction coefficient. Furthermore, the factors affecting the correction coefficient can include the time difference between the previous performance test and the current test, differences in the actual test environment scenario, and differences in the actual software and hardware configuration, etc.

[0033] S120. Determine the evaluation value of at least one test influencing factor within the project attribute information based on preset evaluation rules.

[0034] In this embodiment of the invention, test influencing factors can be understood as factors that may affect the performance testing of the software project under test. Test influencing factors may include system dimensions (e.g., system importance, whether a new technical architecture is adopted, etc.), transaction dimensions (e.g., transaction complexity, transaction customer type, and whether the transaction has been processed, etc.), data table dimensions (e.g., the amount of basic data in key tables, the number of data tables, etc.), and performance dimensions (e.g., peak TPS requirements, response time requirements, and success rate requirements, etc.). In some embodiments, due to different software projects under test, the corresponding test influencing factors may also differ. That is, test influencing factors may include all of the above-mentioned dimensions, or only some of the above-mentioned dimensions, or may include more dimensions. This embodiment of the invention does not impose any limitations on this. The evaluation value of a test influencing factor can be understood as a numerical value used to evaluate the importance of the test influencing factor. In some embodiments, the evaluation value of a test influencing factor is at least one, and the number of evaluation values ​​is related to the number of test influencing factors selected for the software project under test. For example, if the number of test influencing factors selected for the software project under test is 10, then the evaluation value of the test influencing factors corresponding to the software project under test is 10. Preset evaluation rules can be understood as the evaluation standards set for the influencing factors of the software project under test. These rules can include evaluation tiers for each influencing factor. For example: in the system dimension, if the software project under test involves core and important production systems, the corresponding evaluation value can be set to 2; otherwise, it can be set to 1. In the transaction dimension, if the transaction complexity of the software project under test is high, the corresponding evaluation value can be set to 10; if the transaction complexity is average, the corresponding evaluation value can be set to 8; if the transaction complexity is low, the corresponding evaluation value can be set to 5. In the data table dimension, if the number of data tables involved in the software project under test is greater than 5, the corresponding evaluation value can be set to 10; if it is less than 5, the corresponding evaluation value can be set to 5. In the performance dimension, if the peak TPS requirement of the software project under test is greater than or equal to 100, the corresponding evaluation value can be set to 10; if it is less than 100, the corresponding evaluation value can be set to 5.

[0035] Specifically, the test influencing factors included in the project attribute information can be obtained. For example, test influencing factors may include system dimensions (system importance, whether a new technical architecture is adopted, etc.), transaction dimensions (transaction complexity, transaction customer type, and whether the transaction has been processed, etc.), data table dimensions (basic data volume of key tables, number of data tables, etc.), and performance dimensions (peak TPS requirements, response time requirements, and success rate requirements, etc.). The evaluation values ​​corresponding to different influencing factors are then found according to preset evaluation rules, where the preset evaluation rules can be a tiered evaluation system for each test influencing factor. In some embodiments, test information from historical performance tests of multiple software projects under test can be summarized and analyzed to determine the test influencing factors included in the project attribute information. Based on the preset evaluation rules and using data matching algorithms (e.g., string matching, fuzzy matching, etc.), the evaluation values ​​corresponding to each influencing factor are then found.

[0036] S130. Determine the software test items in the preset test range table based on the correction coefficient and evaluation value.

[0037] In this embodiment of the invention, software test items can be understood as items that the software under test needs to be tested. Software test items are related to test influencing factors and may include system importance, transaction complexity, transaction customer type, basic data volume of key tables, number of data tables, peak TPS requirements, response time requirements, and success rate requirements. A preset test scope table can be understood as an information table used to determine the test scope of the software project. Different software test items can be set for different evaluation values ​​within the preset test scope table. Software test items in the preset test scope table may include, but are not limited to, the following: system importance, whether the system adopts new technologies, transaction complexity, transaction activity, transaction customer type, transaction growth in the next year, basic data volume of key tables, number of data tables, peak transactions per second requirement, response time requirements, and success rate requirements.

[0038] Specifically, based on the correction coefficients corresponding to this performance test and the evaluation values ​​corresponding to each test influencing factor, the corresponding software test items can be found in the preset test range table. For example, the correction coefficients and the evaluation values ​​corresponding to each test influencing factor can be compared one by one with the standard evaluation values ​​of the software test items in the preset test range table. If they are greater than or equal to the standard evaluation values, the software test items corresponding to the standard evaluation values ​​are included in the performance test range; otherwise, they are not included. Alternatively, the correction coefficients and the evaluation values ​​corresponding to each test influencing factor can be multiplied by different weighting coefficients, and the calculation results can be compared with the evaluation value thresholds in the preset test range table. If they are greater than or equal to the evaluation value thresholds, the software test items corresponding to the evaluation values ​​are included in the performance test range; otherwise, they are not included.

[0039] The technical solution of this invention determines a correction coefficient based on the project attribute information and historical test information of the software project under test, determines the evaluation value of at least one test influencing factor within the project attribute information based on preset evaluation rules, and determines the software test items in a preset test range table based on the correction coefficient and the evaluation value. This invention achieves the determination of software test items based on historical test information and test influencing factors, using measurable actual test data to compensate for the subjective uncertainty of manually determining the software test range, and combining the reference value of historical test data to improve the efficiency and accuracy of determining the software test range.

[0040] Example 2

[0041] Figure 2 This is a flowchart of a software testing scope determination method provided in Embodiment 2 of the present invention. It is further optimized and extended based on the above embodiments and can be combined with various optional technical solutions in the above embodiments. For example... Figure 2 As shown in the figure, the method for determining the scope of software testing provided in this embodiment includes the following steps:

[0042] S210. Locate the historical test information of the software project under test.

[0043] Specifically, historical test information for the software under test can be obtained based on information such as the project name, project number, or project version number. This historical test information can be information from previous tests of the software under test, and further, it can be stored in a historical test information database or table. In some embodiments, historical test information for the software under test can be queried from the historical test information database or table by information such as project name, project number, or project version number.

[0044] S220. Extract the previous correction coefficient and the time difference between the previous test and the current test from the historical test information.

[0045] In this embodiment of the invention, the previous correction coefficient can be understood as the correction coefficient corresponding to the last performance test of the software project under test. The time difference between the previous test and the current test can be understood as the time difference between the last performance test of the software project under test and the current test.

[0046] Specifically, after obtaining the historical test information of the software project under test, the previous correction coefficient and performance test time related to the software project under test can be extracted from it, and the time difference between the previous test and the current performance test can be used as the time difference between the previous test and the current test. Furthermore, the time difference between the previous test and the current test can be expressed in hours, days or years.

[0047] S230, Generate the cooling coefficient corresponding to the project attribute information.

[0048] In this embodiment of the invention, the cooling coefficient can be understood as a parameter associated with project attribute information. The cooling coefficient can be related to project attribute information such as the correction coefficient and the time difference between the previous and current times.

[0049] Specifically, the cooling coefficient corresponding to the project attribute information can be determined by analyzing and processing the correction coefficient and the time difference between the previous and current times. For example, the principle of Newton's law of cooling can be used, combined with information such as the previous correction coefficient in historical test information. For details regarding Newton's law of cooling, please refer to relevant descriptions in existing technologies; these will not be elaborated upon here in this embodiment of the invention.

[0050] S240. Determine the previous correction coefficient, the time difference between the previous and current times, and the correction coefficient corresponding to the cooling coefficient according to the preset Newtonian cooling formula.

[0051] In this embodiment of the invention, the preset Newton cooling formula can be understood as a formula for determining the correction coefficient set for the performance test of the software project under test based on Newton's law of cooling. The preset Newton cooling formula may include parameters such as the previous correction coefficient, the time difference between the previous and current times, and the cooling coefficient.

[0052] Specifically, the corresponding correction coefficient can be calculated based on the previous correction coefficient, the time difference between the previous and current times, and the cooling coefficient, according to the preset Newtonian cooling formula. Furthermore, the preset Newtonian cooling formula can be expressed as follows:

[0053] T = T0 * Math.exp(-K * Time)

[0054] Where T represents the correction coefficient, T0 represents the previous correction coefficient, Time represents the time difference between the previous correction and the current time, and K represents the cooling coefficient.

[0055] It should be noted that the cooling coefficient in S230 can also be determined using the aforementioned preset Newtonian cooling formula. That is, the values ​​of T, T0, and Time can be set as needed by referring to the historical data information of the software project under test, and then the appropriate cooling coefficient K can be calculated by the aforementioned preset Newtonian cooling formula. For example, when the correction coefficient T is 1, the previous correction coefficient T0 is 100, and the time difference from the previous time to the current time is 180 (days), the cooling coefficient K can be calculated to be approximately equal to 0.0252.

[0056] S250: Read the evaluation scores corresponding to the influencing factors of different standard tests within the preset evaluation rules.

[0057] In this embodiment of the invention, standard test influencing factors can be understood as standards set for the test influencing factors of the software project under test. Standard test influencing factors may include standard system dimensions (e.g., system importance, whether a new technical architecture is adopted, etc.), standard transaction dimensions (e.g., transaction complexity, transaction customer type, and whether the transaction has been processed, etc.), standard data table dimensions (e.g., basic data volume of key tables, number of data tables, etc.), and standard performance dimensions (peak TPS requirements, response time requirements, and success rate requirements, etc.). Evaluation grading can be understood as the grading of evaluation values ​​for standard test influencing factors. Evaluation grading may include the grading of evaluation values ​​for standard system dimensions, standard transaction dimensions, standard data table dimensions, and standard performance dimensions. For example, for the response time requirement in the standard performance dimension, the response time requirement can be evaluated and graded according to the following evaluation value grading: if the response time requirement is less than 0.5 seconds, the corresponding evaluation value can be set to 10; if it is less than 1 second, the corresponding evaluation value can be set to 8; if it is less than 3 seconds, the corresponding evaluation value can be set to 5. The above evaluation grading for response time requirements is only an example and does not constitute a limitation on the embodiments of the present invention.

[0058] Specifically, the standard testing influencing factors and their corresponding evaluation grades related to the software project under test can be obtained from the preset evaluation rules that include several standard testing influencing factors. Furthermore, the standard testing influencing factors can be divided into different evaluation grades according to actual needs. How the evaluation values ​​of each standard testing influencing factor are divided and how many grades are divided does not affect the implementation of the embodiments of the present invention. The evaluation grades corresponding to different standard testing influencing factors can also be saved in a standardized and structured form so that the corresponding information can be directly queried, or the corresponding information can be supplemented or modified when needed.

[0059] S260. Find and test standard influencing factors that match the influencing factors.

[0060] Specifically, common data matching algorithms, such as string matching, fuzzy matching, and template matching, can be used to find standard test influencing factors that match the test influencing factors in the preset evaluation rules.

[0061] S270. The evaluation grading of the standard test influencing factors shall be used as the evaluation value of the test influencing factors.

[0062] Specifically, standard test influencing factors that match the test influencing factors can be found in the preset evaluation rules through data matching methods, and the evaluation grades of the standard test influencing factors can be used as the evaluation values ​​of the corresponding test influencing factors.

[0063] S280. Determine the correction coefficient and the corresponding requirement factor for the evaluation value based on the preset test requirement analysis formula.

[0064] In this embodiment of the invention, the demand factor can be understood as a parameter used to characterize performance testing requirements. The demand factor may be related to the correction coefficient and the evaluation value of the testing influencing factors. The preset test demand analysis formula can be understood as a formula set to determine the demand factor. The preset test demand analysis formula can be determined by multiplying the evaluation values ​​of several testing influencing factors with the correction coefficient, or by first adding the evaluation values ​​of several testing influencing factors and then multiplying them with the change in the correction coefficient, etc. The preset test demand analysis formula can be set according to actual test requirements, and this invention does not impose any restrictions on this.

[0065] Specifically, the correction coefficient and the evaluation values ​​of each test influencing factor can be substituted into the preset test requirement analysis formula to obtain the requirement factor corresponding to the performance test. In some embodiments, the preset test requirement analysis formula can be expressed as follows:

[0066] Demand factor S = (A1 + A2 + ... + Ai) * B1 * ... * Bj * (100 - T)%;

[0067] Where A1, A2, ... Ai represent the evaluation values ​​of the transaction dimension, data table dimension, and performance dimension, B1, B2, ... Bj represent the evaluation values ​​of the system dimension, T represents the correction coefficient, and the values ​​of parameters i and j can be determined by the influence factor dimensions of each test influencing factor selected in the actual performance test.

[0068] S290. Find the software test items that meet the requirements factors in the preset test range table.

[0069] Specifically, based on the requirement factor calculated in S280 for this performance test, matching software test items can be found in the preset test scope table. For example, the requirement factor can be compared with a preset requirement factor threshold, and the software test items required for the performance test of the software project under test can be determined in the preset test scope based on the comparison result. In some embodiments, if a transaction in the implementation scope of the software project under test contains several software test items, the requirement factor of the transaction is calculated based on the preset test requirement analysis formula in S280. If the calculated requirement factor is greater than or equal to the preset requirement factor threshold (for example, it can be, but is not limited to, 60), the software test items contained in the transaction are included in the test scope of the software project under test; if it is less than the preset requirement factor threshold, the software test items contained in the transaction are not included in the test scope of the software project under test. Furthermore, transactions not included in the performance test scope can be used for the performance evaluation of the software project under test.

[0070] The technical solution of this invention involves searching historical test information of the software project under test, extracting the previous correction coefficient and the time difference between the previous test and the current test from the historical test information, generating a cooling coefficient corresponding to the project attribute information, determining the previous correction coefficient, the time difference between the previous test and the current test, and the correction coefficient corresponding to the cooling coefficient according to a preset Newton's cooling formula, reading the evaluation grades corresponding to different standard test influencing factors within preset evaluation rules, finding standard test influencing factors that match the test influencing factors, using the evaluation grade of the standard test influencing factors as the evaluation value of the test influencing factors, determining the requirement factors corresponding to the correction coefficient and the evaluation value in a preset test requirement analysis formula, and finding software test items that meet the requirement factors in a preset test scope table. This invention establishes a functional relationship between the correction coefficient and the time difference between the previous test and the current test by referencing Newton's law of cooling, using the time since the last system performance test as an important influencing factor in performance test requirement analysis. Measurable actual test data compensates for the subjective uncertainty of manually determining the software test scope, improving the efficiency and accuracy of determining the software test scope.

[0071] Example 3

[0072] Figure 3 This is a flowchart illustrating a method for determining the software testing scope according to Embodiment 3 of the present invention. Based on the above embodiments, this embodiment provides one implementation of a method for determining the software testing scope, which can quickly and accurately determine the performance testing scope of a software project. Figure 3 As shown, the software testing scope determination method provided in Embodiment 3 of the present invention specifically includes the following steps:

[0073] S310. Based on actual testing requirements and referring to test data from previous projects, set the value of the cooling coefficient K.

[0074] In this embodiment of the invention, the historical test information of the software project under test in previous performance tests can be referenced, and the values ​​of the correction coefficient T, the previous correction coefficient T0, and the time difference Time between the previous test and the current test can be set as needed. The value of the cooling coefficient K can be calculated by the following preset Newtonian cooling formula.

[0075] T = T0 * Math.exp(-K * Time)

[0076] S320. Based on the performance testing requirements of the software project under test, input or select the attributes of the corresponding influencing factors from the system dimension, transaction dimension, data table dimension, and performance dimension.

[0077] In this embodiment of the invention, the influencing factors at the system level include system importance, whether the system adopts new technologies, and correction coefficients; the influencing factors at the transaction level include transaction complexity, whether there is any account activity, customer type, and transaction growth in the coming year; the influencing factors at the data table level include the amount of basic data in key tables (including expected data) and the number of data tables (non-configuration tables); and the influencing factors at the performance level include peak TPS requirements, response time requirements, and success rate requirements.

[0078] S330. Use the performance testing requirements analysis model calculation tool to calculate the scores of transactions in each system within the implementation scope of the software project under test.

[0079] In this embodiment of the invention, the performance testing requirements analysis model can be as shown in the following table:

[0080]

[0081]

[0082] In some embodiments, a word processing system (WPS) or a spreadsheet in Microsoft Office can be used to implement a measurement tool based on the performance testing requirements analysis model.

[0083] S340. Analyze historical test data and set performance measurement thresholds for actual testing or performance evaluation based on the transaction scores of each system.

[0084] S350. Based on the calculated scores and measurement thresholds, complete the performance testing requirements analysis and determine the performance testing scope of the software project to be tested.

[0085] In some embodiments, the performance testing scope of the software project under test can be determined by calculating the demand factor S using the performance testing demand analysis model calculation formula, and then setting the measurement threshold for performance testing or performance evaluation based on historical test data. For example, the measurement threshold can be set to 60. If the implementation scope of a certain software project under test comprises 10 transactions, and the demand factor S value for transaction 1 is calculated to be 75, for transaction 5 it is 66, and for transaction 8 it is 82, while the demand factor S values ​​for the remaining 7 transactions are all less than 60, then transactions 1, 5, and 8 can be included in the performance testing scope of the software project under test and subjected to performance testing, while the remaining 7 transactions are used for performance evaluation.

[0086] Furthermore, this performance testing requirements analysis model can refer to historical test data from previous projects, assume the time elapsed since the last performance test of the system and the initial values ​​of each influencing factor attribute, and then iteratively update the cooling coefficient, measurement threshold and the values ​​of each influencing factor attribute through extensive verification of the effects of actual project applications, so as to guide the performance testing requirements analysis of the software project to be tested in the next period.

[0087] The technical solution of this invention sets the value of the cooling coefficient K based on actual testing needs and reference to test data from previous projects. According to the performance testing requirements of the software project under test, it inputs or selects the attributes of corresponding influencing factors from system, transaction, data table, and performance dimensions. Using a performance testing requirements analysis model calculation tool, it calculates the scores of transactions in each system within the implementation scope of the software project under test, analyzes historical test data, and sets performance measurement thresholds for actual performance testing or performance evaluation based on the transaction scores of each system. Based on the calculated scores and measurement thresholds, it completes the performance testing requirements analysis and determines the performance testing scope of the software project under test. This invention, through the performance testing requirements analysis model, uses the time elapsed since the last system performance test as an important influencing factor in the performance testing requirements analysis. It uses measurable actual test data to compensate for the subjective uncertainty of manually determining the software testing scope, improving the efficiency and accuracy of determining the software testing scope and reducing the probability of missed transactions due to insufficient performance testing requirements analysis.

[0088] Example 4

[0089] Figure 4 This is a schematic diagram of a software testing range determination device provided in Embodiment 4 of the present invention. Figure 4 As shown, the device includes:

[0090] The correction coefficient module 41 is used to determine the correction coefficient based on the project attribute information and historical test information of the software project under test.

[0091] Evaluation value module 42 is used to determine the evaluation value of at least one test influencing factor in the project attribute information based on preset evaluation rules.

[0092] The test item determination module 43 is used to determine software test items in a preset test range table based on correction coefficients and evaluation values.

[0093] The technical solution of this invention involves a correction coefficient module determining a correction coefficient based on the project attribute information and historical test information of the software project under test; an evaluation value module determining the evaluation value of at least one test influencing factor within the project attribute information based on preset evaluation rules; and a test item determination module determining software test items based on the correction coefficient and evaluation value in a preset test range table. This invention achieves software test item determination based on historical test information and test influencing factors, using measurable actual test data to compensate for the subjective uncertainty of manually determining the software test range. Combined with the reference value of historical test data, it improves the efficiency and accuracy of determining the software test range.

[0094] Furthermore, based on the above embodiments of the invention, the correction coefficient module 41 includes:

[0095] The historical test information search unit is used to search for historical test information of the software project under test.

[0096] The information extraction unit is used to extract the previous correction coefficient and the time difference between the previous and current times from the historical test information.

[0097] The cooling coefficient generation unit is used to generate the cooling coefficient corresponding to the project attribute information.

[0098] The correction coefficient determination unit is used to determine the previous correction coefficient, the time difference between the previous and current times, and the correction coefficient corresponding to the cooling coefficient according to the preset Newtonian cooling formula.

[0099] In some embodiments, the preset Newtonian cooling formula in the software test range determination method includes: T = T0 * Math.exp(-K * Time), where T represents the correction coefficient, T0 represents the previous correction coefficient, Time represents the time difference between the previous correction and the current correction, and K represents the cooling coefficient.

[0100] Furthermore, based on the above embodiments of the invention, the evaluation value module 42 includes:

[0101] The evaluation grading reading unit is used to read the evaluation grading corresponding to the influencing factors of different standard tests within the preset evaluation rules.

[0102] The Standard Test Influence Factor Search Unit is used to find standard test influence factors that match the test influence factors.

[0103] The evaluation value determination unit is used to use the evaluation grading of standard test influencing factors as the evaluation value of the test influencing factors.

[0104] Furthermore, based on the above embodiments of the invention, the test item determination module 43 includes:

[0105] The demand factor determination unit is used to determine the demand factors corresponding to the correction coefficients and evaluation values ​​in the preset test demand analysis formula.

[0106] The software test item search unit is used to search for software test items that meet the requirements factors in a preset test scope table.

[0107] In some embodiments, the test influencing factors in the software test scope determination method include: system dimension, transaction dimension, data table dimension, and performance dimension. The preset test requirement analysis formula includes: requirement factor S = (A1 + A2 + ... Ai) * B1 * ... Bj * (100 - T)%.

[0108] Where A1, A2, ... Ai represent the evaluation values ​​of the transaction dimension, data table dimension, and performance dimension, B1, B2, ... Bj represent the evaluation value of the system dimension, and T represents the correction coefficient.

[0109] In some embodiments, the software test items in the preset test scope table of the software test scope determination method include at least one of the following: system importance, whether the system adopts new technologies, transaction complexity, transaction activity, transaction customer type, future threshold time transaction growth, key table basic data volume, number of data tables, peak transaction count per second requirement, response time requirement, and success rate requirement.

[0110] The software testing range determination device provided in the embodiments of the present invention can execute the software testing range determination method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the method.

[0111] Example 5

[0112] Figure 5 A schematic diagram of an electronic device 50 that can be used to implement embodiments of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0113] like Figure 5As shown, the electronic device 50 includes at least one processor 51 and a memory, such as a read-only memory (ROM) 52 and a random access memory (RAM) 53, communicatively connected to the at least one processor 51. The memory stores computer programs executable by the at least one processor. The processor 51 can perform various appropriate actions and processes based on the computer program stored in the ROM 52 or loaded into the RAM 53 from storage unit 58. The RAM 53 can also store various programs and data required for the operation of the electronic device 50. The processor 51, ROM 52, and RAM 53 are interconnected via a bus 54. An input / output (I / O) interface 55 is also connected to the bus 54.

[0114] Multiple components in electronic device 50 are connected to I / O interface 55, including: input unit 56, such as keyboard, mouse, etc.; output unit 57, such as various types of monitors, speakers, etc.; storage unit 58, such as disk, optical disk, etc.; and communication unit 59, such as network card, modem, wireless transceiver, etc. Communication unit 59 allows electronic device 50 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0115] Processor 51 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 51 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 51 performs the various methods and processes described above, such as software test scope determination methods.

[0116] In some embodiments, the software test scope determination method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 58. In some embodiments, part or all of the computer program may be loaded and / or installed on electronic device 50 via ROM 52 and / or communication unit 59. When the computer program is loaded into RAM 53 and executed by processor 51, one or more steps of the software test scope determination method described above may be performed. Alternatively, in other embodiments, processor 51 may be configured to perform the software test scope determination method by any other suitable means (e.g., by means of firmware).

[0117] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0118] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0119] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0120] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0121] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or computing systems that include middleware components (e.g., application servers), or computing systems that include frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0122] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0123] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0124] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A software test scope determination method characterized by, include: The correction factor is determined based on the project attribute information and historical test information of the software project under test. The evaluation value of at least one test influencing factor within the project attribute information is determined based on preset evaluation rules; The software test items are determined in the preset test range table based on the correction coefficients and evaluation values. The step of determining the correction coefficient based on the project attribute information and historical test information of the software project under test includes: Locate the historical test information of the software project under test; Extract the previous correction coefficient and the time difference between the previous and current times from the historical test information; Generate the cooling coefficient corresponding to the project attribute information; The previous correction coefficient, the time difference between the previous and current times, and the correction coefficient corresponding to the cooling coefficient are determined according to the preset Newtonian cooling formula. The step of determining software test items in a preset test range table based on the correction coefficient and evaluation value includes: The correction coefficient and the corresponding demand factor for the evaluation value are determined using a preset test demand analysis formula. Find the software test item that satisfies the requirement factor in the preset test range table; The factors influencing the test include: system dimension, transaction dimension, data table dimension, and performance dimension. The preset test requirement analysis formula includes: Demand Factors ; Where A1, A2, ... Ai represent the evaluation values ​​of the transaction dimension, the data table dimension, and the performance dimension, B1, B2, ... Bj represent the evaluation value of the system dimension, and T represents the correction coefficient.

2. The method according to claim 1, characterized in that, The preset Newtonian cooling formula includes: Where T represents the correction coefficient, T0 represents the previous correction coefficient, Time represents the time difference between the previous correction and the current time, and K represents the cooling coefficient.

3. The method according to claim 1, characterized in that, The step of determining the evaluation value of at least one test influencing factor within the project attribute information based on preset evaluation rules includes: Read the evaluation scores corresponding to the influencing factors of different standard tests within the preset evaluation rules; Find the standard test influencing factors that match the test influencing factors; The evaluation grading of the standard test influencing factors is used as the evaluation value of the test influencing factors.

4. The method according to any one of claims 1-3, characterized in that, The software test items in the preset test scope table include at least one of the following: system importance, whether the system adopts new technologies, transaction complexity, transaction activity, transaction customer type, future threshold time transaction growth, key table basic data volume, number of data tables, peak transaction count per second requirement, response time requirement, and success rate requirement.

5. A software testing range determination device, characterized in that, include: The correction factor module is used to determine the correction factor based on the project attribute information and historical test information of the software project under test. The evaluation value module is used to determine the evaluation value of at least one test influencing factor within the project attribute information based on preset evaluation rules. The test item determination module is used to determine software test items in a preset test range table based on the correction coefficient and the evaluation value. The correction coefficient module includes: The historical test information lookup unit is used to look up the historical test information of the software project under test. The information extraction unit is used to extract the previous correction coefficient and the time difference between the previous and current times from the historical test information. A cooling coefficient generation unit is used to generate the cooling coefficient corresponding to the project attribute information; The correction coefficient determination unit is used to determine the previous correction coefficient, the time difference between the previous correction and the current time, and the correction coefficient corresponding to the cooling coefficient according to a preset Newtonian cooling formula. The test item determination module includes: The demand factor determination unit is used to determine the demand factors corresponding to the correction coefficient and the evaluation value based on a preset test demand analysis formula. The software test item search unit is used to search the preset test range table for the software test item that satisfies the requirement factor. The factors influencing the test include: system dimension, transaction dimension, data table dimension, and performance dimension. The preset test requirement analysis formula includes: Demand Factors ; Where A1, A2, ... Ai represent the evaluation values ​​of the transaction dimension, the data table dimension, and the performance dimension, B1, B2, ... Bj represent the evaluation value of the system dimension, and T represents the correction coefficient.

6. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the software test scope determination method according to any one of claims 1-4.

7. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that cause a processor to execute the software test range determination method according to any one of claims 1-4.

Images