Software system test requirements assessment method, device, electronic device and storage medium

Abstract

The present invention discloses a method, device, electronic device and storage medium for evaluating software system test requirements. The method comprises: obtaining personnel description information of developers related to the software system to be evaluated, and fusing the personnel description information to obtain personnel fusion characteristic values; obtaining system description information of the software system to be evaluated, and fusing the system description information to obtain system fusion characteristic values; obtaining environment description information of the application environment corresponding to the software to be evaluated, and fusing the environment description information to obtain environment fusion characteristic values; obtaining a comprehensive score value according to the personnel fusion characteristic values, the system fusion characteristic values ​​and the environment fusion characteristic values; determining whether the software system to be evaluated needs to be tested according to the comprehensive score value. The present invention can make a more accurate evaluation of the test requirements of the software system and reduce the risk of evaluation errors.

Description

Technical Field

[0001] The present invention relates to the field of computer software technology, and in particular to a method, device, electronic equipment and storage medium for evaluating software system test requirements. Background Art

[0002] Software systems are widely used in the business of financial institutions such as banks and insurance companies. In order to ensure the normal operation of the developed software system, it is generally necessary to conduct reliability testing on the software system before the software system goes online. However, in actual applications, due to various reasons, such as time constraints and high R&D costs, it is necessary to comprehensively consider various factors such as the importance of a software system, development quality, and self-testing conditions to determine whether the software system needs to be tested.

[0003] At present, the evaluation of whether a software system needs reliability testing mainly relies on the subjective opinions of developers or testers, and human subjective judgment has a greater risk of misjudgment. Summary of the invention

[0004] In order to overcome the above problems and defects, the present invention provides a software system test requirement evaluation method, device, electronic device and storage medium to make a more accurate evaluation of the test requirements of the software system and reduce the risk of evaluation errors.

[0005] To achieve the above object, the present invention provides a software system test requirements assessment method in a first aspect, comprising:

[0006] Obtaining personnel description information of developers related to the software system to be evaluated, and fusing the personnel description information to obtain personnel fusion feature values; the personnel description information includes the reliability information and contribution information of the developers;

[0007] Obtain the system description information of the software system to be evaluated, and fuse the system description information to obtain the system fusion characteristic value; the system description information includes system importance information and online priority information;

[0008] Obtaining environmental description information of the application environment corresponding to the software to be evaluated, and fusing the environmental description information to obtain environmental fusion feature values; the environmental description information includes environmental stability information and environmental correlation information;

[0009] According to the personnel fusion characteristic value, the system fusion characteristic value and the environment fusion characteristic value, a comprehensive score value is obtained;

[0010] Determine whether the software system to be evaluated needs to be tested based on the comprehensive score.

[0011] A second aspect of the present invention provides a software system test requirements assessment device, comprising:

[0012] The first acquisition module is used to obtain the personnel description information of the developers related to the software system to be evaluated, and fuse the personnel description information to obtain the personnel fusion feature value; the personnel description information includes the reliability information and contribution information of the developers;

[0013] The second acquisition module is used to obtain the system description information of the software system to be evaluated, and fuse the system description information to obtain the system fusion characteristic value; the system description information includes system importance information and online priority information;

[0014] The third acquisition module is used to obtain the environment description information of the application environment corresponding to the software to be evaluated, and fuse the environment description information to obtain the environment fusion feature value; the environment description information includes environment stability information and environment correlation information;

[0015] A scoring module is used to obtain a comprehensive scoring value based on the personnel fusion feature value, the system fusion feature value and the environment fusion feature value;

[0016] The evaluation module is used to determine whether the software system to be evaluated needs to be tested based on the comprehensive score value.

[0017] A third aspect of the present invention provides an electronic device, including a processor and a memory, wherein a computer program is stored in the memory, and when the computer program is executed by the processor, the above-mentioned software system test requirement assessment method is implemented.

[0018] The fourth invention of the present invention provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the above-mentioned software system test requirement assessment method is implemented.

[0019] Compared with the prior art, the beneficial effects of the present invention include: the present invention first obtains the personnel description information of the developers related to the software system to be evaluated, and fuses the personnel description information to obtain the personnel fusion characteristic value; obtains the system description information of the software system to be evaluated, and fuses the system description information to obtain the system fusion characteristic value; obtains the environment description information of the application environment corresponding to the software to be evaluated, and fuses the environment description information to obtain the environment fusion characteristic value. Then, according to the personnel fusion characteristic value, the system fusion characteristic value and the environment fusion characteristic value, a comprehensive scoring value is obtained. Finally, according to the comprehensive scoring value, it is determined whether the software system to be evaluated needs to be tested. It can be seen that the present invention combines the three dimensions of personnel description information, system description information and environment description information to comprehensively evaluate whether the software system needs to be tested, without relying on the subjective experience of developers and testers to judge, avoiding the risk of human judgment errors, and compared with human evaluation, the present invention is more objective and accurate, and effectively improves the accuracy of test demand evaluation. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The drawings herein are incorporated into and constitute a part of the specification, showing embodiments consistent with the present invention, and together with the specification, are used to explain the principles of the present invention. Obviously, the drawings described below are only some embodiments of the present invention, and for those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative work. In the drawings:

[0021] Figure 1 A schematic diagram of an exemplary system architecture of the technical solution of an embodiment of the present invention;

[0022] Figure 2 The process of the software system test requirements assessment method according to the embodiment of the present invention is as follows Figure 1 ;

[0023] Figure 3 The process of the software system test requirements assessment method according to the embodiment of the present invention is as follows Figure 2 ;

[0024] Figure 4 The process of the software system test requirements assessment method according to the embodiment of the present invention is as follows Figure 3 ;

[0025] Figure 5 The process of the software system test requirements assessment method according to the embodiment of the present invention is as follows Figure 4 ;

[0026] Figure 6 The process of the software system test requirements assessment method according to the embodiment of the present invention is as follows Figure 5 ;

[0027] Figure 7 A framework diagram of a software system test requirement evaluation device according to an embodiment of the present invention;

[0028] Figure 8 FIG. 1 is a schematic diagram of the architecture of a computer system of an electronic device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0029] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that the present invention will be more comprehensive and complete and fully convey the concept of the example embodiments to those skilled in the art.

[0030] In addition, the described features, structures or characteristics may be combined in one or more embodiments in any suitable manner. In the following description, many specific details are provided to provide a full understanding of the embodiments of the present invention. However, those skilled in the art will appreciate that the technical solution of the present invention can be practiced without one or more of the specific details, or other methods, components, devices, steps, etc. may be adopted. In other cases, known methods, devices, implementations or operations are not shown or described in detail to avoid blurring various aspects of the present invention.

[0031] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities may be implemented in software form, or in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.

[0032] The flowcharts shown in the accompanying drawings are only exemplary and do not necessarily include all the contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps can be decomposed, and some operations / steps can be combined or partially combined, so the actual execution order may change according to actual conditions.

[0033] Figure 1 A schematic diagram showing an exemplary system architecture to which the technical solution of an embodiment of the present invention can be applied.

[0034] like Figure 1 As shown, the system architecture may include terminal devices (such as Figure 1 The embodiment of the present invention is a schematic diagram of a mobile phone 101, a tablet computer 102, a portable computer 103, a desktop computer, etc., a network 104, and a server 105. The network 104 is used to provide a medium for a communication link between the terminal device and the server 105. The network 104 may include various connection types, such as a wired communication link, a wireless communication link, etc.

[0035] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is only for illustration. According to the implementation requirements, there may be any number of terminal devices, networks and servers. For example, the server 105 may be a server cluster composed of multiple servers.

[0036] It should be noted that the software system test requirement evaluation method provided in the embodiment of the present invention is generally executed by the server 105, and accordingly, the software system test requirement evaluation device is generally arranged in the server 105. However, in other embodiments of the present invention, the terminal device may also have similar functions as the server, so as to execute the technical solution of the software system test requirement evaluation provided in the embodiment of the present invention.

[0037] The implementation details of the technical solution of the embodiment of the present invention are described in detail below.

[0038] The embodiment of the present invention provides a method for evaluating software system test requirements. The software system may include but is not limited to a customer management system, a financial management system, an employee management system, and other software systems of a financial institution. Figure 2 As shown, the software system test requirement assessment method may include step 210, step 220, step 230, step 240 and step 250. Specifically as follows:

[0039] Step 210, obtaining personnel description information of developers related to the software system to be evaluated, and fusing the personnel description information to obtain personnel fusion feature values; the personnel description information includes the reliability information and contribution information of the developers.

[0040] Specifically, reliability information includes the developer's code quantity, code quality, and historical development failure rate. Code quantity refers to the developer's historical code output, code quality refers to the developer's code error rate (for example, the number of errors per thousand lines of code), and historical development failure rate refers to the probability of software failure in the history of the developer's participation in development. Contribution information refers to the amount of work each developer has put in the development of the software system, or the importance of the work they are responsible for in the development of the software system.

[0041] In step 210, the personnel description information is fused to obtain personnel fusion feature values, such as Figure 3 As shown, specifically including:

[0042] Step 211, determine the code quantity score value according to the code quantity, determine the code quality score value according to the code quality, and determine the failure rate score value according to the historical development failure rate. Assume that there are developers A and B, developer A's code quantity score value is A1, code quality score value is A2, and failure rate score value is A3; developer B's code quantity score value is B1, code quality score value is B2, and failure rate score value is B3.

[0043] Step 212: Determine a contribution score value based on the contribution information. Assume that the contribution score value of developer A is A4, and the contribution score value of developer B is B4.

[0044] Step 213, weight the code quantity score, code quality score, failure rate score and contribution score respectively, and then sum them up to obtain the personnel fusion characteristic value. The weight coefficients can be assigned according to the importance of the code quantity score, code quality score, failure rate score and contribution score to the final personnel fusion characteristic value m1. Let the coefficient of the code quantity score be P1, the code quality score be P2, the failure rate score be P3 and the contribution score be P4. Then the personnel fusion characteristic value m1 of developer A = P1*A1+P2*A2+P3*A3+P4*A4, and the personnel fusion characteristic value m2 of developer B = P1*B1+P2*B2+P3*B3+P4*B4. Taking into account the different work experience and abilities of each developer, as well as the different importance to the development of the software system, the personnel fusion characteristic value of each person can also be assigned a weight coefficient. Let the weight coefficient of developer A be P5, and the weight coefficient of developer B be P6;

[0045] Then the final personnel fusion characteristic value M1=P5*m1+P6*m2.

[0046] Step 220, obtain the system description information of the software system to be evaluated, and fuse the system description information to obtain the system fusion characteristic value; the system description information includes system importance information and online priority information. Among them, the system importance information refers to the importance of the software system to the user unit, and the online priority information refers to the priority of the software system to be put into use online or the urgency of going online.

[0047] In step 220, the system description information is fused to obtain the system fusion feature value, such as Figure 4 As shown, specifically including:

[0048] Step 221, determining an importance score value according to the system importance information, and determining a priority score value according to the online priority information.

[0049] Step 222: weight the importance score value and the priority score value respectively and then sum them up to obtain the system fusion feature value.

[0050] For example, let the system importance score be C, the weight coefficient be Q1, and the priority score be D, the weight coefficient be Q2. Then the system fusion characteristic value M2 = Q1*C+Q2*D.

[0051] Furthermore, the system description information may also include testability information. Among them, the testability information includes the estimated test time and the estimated test resource consumption. The estimated test time indicates the estimated time required to test the reliability of the software system. The estimated test resource consumption indicates the estimated personnel working time and equipment resources required to test the reliability of the software system. Determining the testability score value based on the testability information may specifically include: determining the testability score value based on the estimated test time and the estimated test resource consumption.

[0052] In step 220, the system description information is fused to obtain the system fusion feature value, such as Figure 5 As shown, specifically including:

[0053] Step 223, determining an importance score value according to the system importance information, determining a priority score value according to the online priority information, and determining a testability score value according to the testability information.

[0054] Step 224 , weight the importance score value, the priority score value, and the testability score value, respectively, and then sum them up to obtain a system fusion feature value.

[0055] For example, let the system importance score be C, the weight coefficient be Q1, the priority score be D, the weight coefficient be Q2, the testability score be E, the weight coefficient be Q3. Then the system fusion characteristic value M2 = Q1*C+Q2*D+Q3*E.

[0056] Step 230, obtain the environment description information of the application environment corresponding to the software to be evaluated, and fuse the environment description information to obtain the environment fusion feature value; the environment description information includes environment stability information and environment correlation information. Among them, the application environment refers to the hardware configuration and operating system version information when the software system is running. The environment stability information refers to the working stability or failure probability of all software in the application environment. The environment correlation information refers to the number of other application modules that need to be associated when the software system to be evaluated runs in the application environment.

[0057] In step 230, the environment description information is fused to obtain the environment fusion feature value, such as Figure 6 As shown, specifically including:

[0058] Step 231, determining a stability score value according to the stability information, and determining a relevance score value according to the relevance information.

[0059] Step 232: weight the stability score and the association score respectively and then sum them up to obtain the environment fusion feature value.

[0060] For example, assuming that the system stability score is F, the weight coefficient is R1, and the priority score is G, the weight coefficient is R2, then the system fusion feature value M3 = R1*F+R2*G.

[0061] Step 240, obtaining a comprehensive score value according to the personnel fusion feature value, the system fusion feature value and the environment fusion feature value, specifically including respectively weighting the personnel fusion feature value, the system fusion feature value and the environment fusion feature value and summing them up to obtain the comprehensive score value.

[0062] Exemplarily, the weight coefficient of the personnel fusion feature value is ρ1, the weight coefficient of the system fusion feature value is ρ2, and the weight coefficient of the environment fusion feature value is ρ3.

[0063] Then, the comprehensive score value M=ρ1*M1+=ρ2*M2+ρ3*M3.

[0064] Step 250: Determine whether the software system to be evaluated needs to be tested according to the comprehensive score.

[0065] Exemplarily, the test requirement threshold is L. When M≥L, the software system needs to be evaluated for reliability testing. Otherwise, no testing is required and the system can be directly put into formal online application.

[0066] This embodiment combines the three dimensions of personnel description information, system description information and environment description information to comprehensively evaluate whether the software system needs to be tested. It does not rely on the subjective experience of developers and testers to make judgments, thus avoiding the risk of human misjudgment. Compared with manual evaluation, the present invention is more objective and accurate, and effectively improves the accuracy of test requirements evaluation.

[0067] It should be noted that the order of obtaining the personnel description information, the system description information and the environment description information in this embodiment can be adjusted arbitrarily without any special limitation. That is, the order of step 210, step 220 and step 230 can be adjusted arbitrarily, and the technical effects finally achieved are equivalent.

[0068] The embodiment of the present invention provides a software system test requirement evaluation device, which applies the software system test requirement evaluation method provided in the above embodiment, such as Figure 7 As shown, it includes a first acquisition module 301, a second acquisition module 302, a third acquisition module 303, a scoring module 304 and an evaluation module 305. Among them:

[0069] The first acquisition module is used to obtain the personnel description information of the developers related to the software system to be evaluated, and fuse the personnel description information to obtain the personnel fusion feature value; the personnel description information includes the reliability information and contribution information of the developers.

[0070] The second acquisition module is used to obtain the system description information of the software system to be evaluated, and fuse the system description information to obtain the system fusion characteristic value; the system description information includes system importance information and online priority information;

[0071] The third acquisition module is used to obtain the environment description information of the application environment corresponding to the software to be evaluated, and fuse the environment description information to obtain the environment fusion feature value; the environment description information includes environment stability information and environment correlation information;

[0072] The scoring module is used to obtain a comprehensive scoring value based on the personnel fusion feature value, the system fusion feature value and the environment fusion feature value;

[0073] The evaluation module is used to determine whether the software system to be evaluated needs to be tested based on the comprehensive score value.

[0074] The software system test requirement assessment device of this embodiment combines the three dimensions of personnel description information, system description information and environment description information to comprehensively assess whether the software system needs to be tested. It does not rely on the subjective experience of developers and testers to make judgments, thus avoiding the risk of human misjudgment. Compared with manual evaluation, the present invention is more objective and accurate, and effectively improves the accuracy of test requirement assessment.

[0075] An embodiment of the present invention further provides an electronic device, including a processor and a memory, wherein a computer program is stored in the memory, and when the computer program is executed by the processor, the software system test requirement assessment method provided in the above embodiment is implemented.

[0076] Figure 8 A schematic diagram of the structure of a computer system suitable for implementing an electronic device of an embodiment of the present invention is shown.

[0077] It should be noted that Figure 8 The computer system of the electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0078] like Figure 8As shown, the computer system includes a central processing unit (CPU) 1801, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 1802 or the program loaded from the storage part 1808 to the random access memory (RAM) 1803, such as executing the method described in the above embodiment. In RAM 1803, various programs and data required for system operation are also stored. CPU 1801, ROM 1802 and RAM 1803 are connected to each other through bus 1804. Input / output (I / O) interface 1805 is also connected to bus 1804.

[0079] The following components are connected to the I / O interface 1805: an input section 1806 including a keyboard, a mouse, etc.; an output section 1807 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 1808 including a hard disk, etc.; and a communication section 1809 including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication section 1809 performs communication processing via a network such as the Internet. A drive 1810 is also connected to the I / O interface 1805 as needed. A removable medium 1811, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 1810 as needed so that a computer program read therefrom is installed into the storage section 1808 as needed.

[0080] In particular, according to an embodiment of the present invention, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present invention includes a computer program product, which includes a computer program carried on a computer readable medium, and the computer program includes a computer program for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication section 1809, and / or installed from a removable medium 1811. When the computer program is executed by a central processing unit (CPU) 1801, various functions defined in the system of the present invention are executed.

[0081] It should be noted that the computer-readable medium shown in the embodiment of the present invention may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present invention, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, device or device. In the present invention, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable computer program. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which may send, propagate, or transmit programs for use by or in conjunction with an instruction execution system, apparatus, or device. The computer program contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0082] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present invention. Among them, each box in the flowchart or block diagram can represent a module, a program segment, or a part of the code, and the above-mentioned module, program segment, or a part of the code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart, can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0083] The units involved in the embodiments of the present invention may be implemented by software or hardware, and the units described may also be arranged in a processor. The names of these units do not, in some cases, limit the units themselves.

[0084] Specifically, through the electronic device of this embodiment, first obtain the personnel description information of the developer related to the software system to be evaluated, and fuse the personnel description information to obtain the personnel fusion feature value; obtain the system description information of the software system to be evaluated, and fuse the system description information to obtain the system fusion feature value; obtain the environment description information of the application environment corresponding to the software to be evaluated, and fuse the environment description information to obtain the environment fusion feature value. Then, according to the personnel fusion feature value, the system fusion feature value and the environment fusion feature value, a comprehensive score value is obtained. Finally, according to the comprehensive score value, it is determined whether the software system to be evaluated needs to be tested. It can be seen that the present invention combines the three dimensions of personnel description information, system description information and environment description information to comprehensively evaluate whether the software system needs to be tested, without relying on the subjective experience of developers and testers to judge, avoiding the risk of human judgment errors, and compared with human evaluation, the present invention is more objective and accurate, and effectively improves the accuracy of test demand evaluation.

[0085] As another aspect, the present invention further provides a computer-readable storage medium, which may be included in the electronic device described in the above embodiment; or may exist independently without being assembled into the electronic device. The above storage medium carries one or more programs, and when the above one or more programs are executed by an electronic device, the electronic device implements the method described in the above embodiment.

[0086] It should be noted that, although several modules or units of the equipment for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to an embodiment of the present invention, the features and functions of two or more modules or units described above can be embodied in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into being embodied by multiple modules or units.

[0087] Through the description of the above implementation, it is easy for those skilled in the art to understand that the example implementation described here can be implemented by software, or by software combined with necessary hardware. Therefore, the technical solution according to the implementation of the present invention can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, including several instructions to enable a computing device (which can be a personal computer, a server, a touch terminal, or a network device, etc.) to execute the method according to the implementation of the present invention.

[0088] Specifically, through the storage medium of this embodiment, the personnel description information of the developers related to the software system to be evaluated can be first obtained, and the personnel description information can be integrated to obtain the personnel integration characteristic value; the system description information of the software system to be evaluated can be obtained, and the system description information can be integrated to obtain the system integration characteristic value; the environment description information of the application environment corresponding to the software to be evaluated can be obtained, and the environment description information can be integrated to obtain the environment integration characteristic value. Then, according to the personnel integration characteristic value, the system integration characteristic value and the environment integration characteristic value, a comprehensive scoring value is obtained. Finally, according to the comprehensive scoring value, it is determined whether the software system to be evaluated needs to be tested. It can be seen that the present invention combines the three dimensions of personnel description information, system description information and environment description information to comprehensively evaluate whether the software system needs to be tested, without relying on the subjective experience of developers and testers to judge, avoiding the risk of human judgment errors, and compared with human evaluation, the present invention is more objective and accurate, and effectively improves the accuracy of test demand evaluation.

[0089] Those skilled in the art will readily appreciate other embodiments of the present invention after considering the specification and practicing the embodiments disclosed herein. The present invention is intended to cover any variations, uses or adaptations of the present invention that follow the general principles of the present invention and include common knowledge or customary technical means in the art that are not disclosed in the present invention.

[0090] It should be understood that the present invention is not limited to the exact construction that has been described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present invention is limited only by the appended claims.

Claims

1. A software system test requirements assessment method, characterized in that: include: Obtain information on the code quantity, code quality, historical development failure rate, and contribution of developers related to the software system to be evaluated; Determine a code quantity score value according to the code quantity, determine a code quality score value according to the code quality, determine a failure rate score value according to the historical development failure rate, and determine a contribution score value according to the contribution information; The code quantity score value, the code quality score value, the failure rate score value and the contribution score value are weighted and summed up to obtain a personnel fusion feature value; Obtaining system importance information, online priority information and testability information of the software system to be evaluated; Determine an importance score value according to the system importance information, determine a priority score value according to the online priority information, and determine a testability score value according to the testability information; The importance score value, the priority score value and the testability score value are weighted and summed to obtain a system fusion feature value; Obtaining environment description information of the application environment corresponding to the software to be evaluated, and fusing the environment description information to obtain an environment fusion feature value; the environment description information includes environment stability information and environment correlation information; Obtaining a comprehensive score value according to the personnel fusion feature value, the system fusion feature value and the environment fusion feature value; Determine whether the software system to be evaluated needs to be tested according to the comprehensive score.

2. The software system test requirements assessment method according to claim 1, characterized in that: The testability information includes an estimated test time and an estimated test resource consumption. The step of determining a testability score value according to the testability information includes: The testability score is determined according to the estimated test time and the estimated test resource consumption.

3. The software system test requirements assessment method according to claim 1, characterized in that: The step of fusing the environment description information to obtain an environment fusion feature value comprises: Determine a stability score value according to the stability information, and determine a relevance score value according to the relevance information; The stability score value and the association score value are weighted respectively and then summed to obtain the environment fusion feature value.

4. The software system test requirements assessment method according to claim 1, characterized in that: The step of obtaining a comprehensive score value according to the personnel fusion feature value, the system fusion feature value and the environment fusion feature value comprises: The personnel fusion feature value, the system fusion feature value and the environment fusion feature value are weighted respectively and then summed to obtain the comprehensive score value.

5. A software system test requirements assessment device, characterized in that: include: The first acquisition module is used to obtain the code quantity, code quality, historical development failure rate and contribution information of developers related to the software system to be evaluated; Determine a code quantity score value according to the code quantity, determine a code quality score value according to the code quality, determine a failure rate score value according to the historical development failure rate, and determine a contribution score value according to the contribution information; weight the code quantity score value, the code quality score value, the failure rate score value, and the contribution score value, respectively, and sum them up to obtain a personnel fusion feature value; The second acquisition module is used to obtain the system importance information, online priority information and testability information of the software system to be evaluated; Determine an importance score value according to the system importance information, determine a priority score value according to the online priority information, and determine a testability score value according to the testability information; The importance score value, the priority score value and the testability score value are weighted and summed to obtain a system fusion feature value; The third acquisition module is used to acquire the environment description information of the application environment corresponding to the software to be evaluated, and fuse the environment description information to obtain the environment fusion feature value; the environment description information includes environment stability information and environment correlation information; A scoring module, used for obtaining a comprehensive scoring value according to the personnel fusion feature value, the system fusion feature value and the environment fusion feature value; The evaluation module is used to determine whether the software system to be evaluated needs to be tested according to the comprehensive score value.

6. An electronic device, characterized in that: The method comprises a processor and a memory, wherein a computer program is stored in the memory, and when the computer program is executed by the processor, the method for evaluating software system test requirements according to any one of claims 1 to 4 is implemented.

7. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the software system test requirement assessment method according to any one of claims 1 to 4 is implemented.

Images