Software defect analysis method and device, equipment and storage medium

Abstract

The embodiment of the invention discloses a software defect analysis method and device, equipment and a storage medium. The method comprises the following steps: acquiring a plurality of target software defects generated in a test process of target software and defect description information of each target software defect; according to the influence description information of the multiple influence types and the defect description information of each target software defect, a target influence type corresponding to each target software defect is determined, and different influence types are used for representing different influence dimensions caused by the software defects; and performing defect influence analysis according to the target influence type corresponding to each target software defect, determining development optimization information corresponding to the target software, and performing subsequent development optimization on the target software based on the development optimization information. Through the technical scheme of the embodiment of the invention, the influence classification and the influence analysis can be carried out on the software defects, so that the software development is optimized, and the generation of the software defects is reduced.

Description

Technical Field

[0001] The embodiments of the present invention relate to computer technology, and in particular to a software defect analysis method, apparatus, device and storage medium. Background Art

[0002] After software development, it is usually necessary to test the developed software. During the software testing process, some software defects often occur. Software defects refer to some problems, errors, or hidden functional defects in the software that destroy the normal operation ability, resulting in the software failing to meet the user's needs to some extent.

[0003] At present, after a software defect is generated, people usually only focus on repairing the software defect and repeating the test, but do not conduct an overall analysis of all the generated software defects in order to reduce the subsequent software defects. It can be seen that there is an urgent need for a method that can effectively analyze software defects. Summary of the invention

[0004] The embodiments of the present invention provide a software defect analysis method, apparatus, device and storage medium to classify and analyze the impact of software defects, thereby optimizing software development and reducing the generation of software defects.

[0005] In a first aspect, an embodiment of the present invention provides a software defect analysis method, comprising:

[0006] Acquire multiple target software defects generated during the testing process of the target software and defect description information of each of the target software defects;

[0007] Determine, according to the impact description information of the multiple impact types and the defect description information of each of the target software defects, a target impact type corresponding to each of the target software defects, wherein different impact types are used to characterize different impact dimensions caused by the software defects;

[0008] Defect impact analysis is performed according to the target impact type corresponding to each of the target software defects, and development optimization information corresponding to the target software is determined, so as to perform subsequent development optimization on the target software based on the development optimization information.

[0009] In a second aspect, an embodiment of the present invention further provides a software defect analysis device, comprising:

[0010] A target software defect acquisition module is used to acquire multiple target software defects generated during the test of the target software and defect description information of each target software defect;

[0011] A target impact type determination module, used to determine the target impact type corresponding to each target software defect according to the impact description information of multiple impact types and the defect description information of each target software defect, wherein different impact types are used to characterize different impact dimensions caused by software defects;

[0012] The development optimization information determination module is used to perform defect impact analysis according to the target impact type corresponding to each target software defect, determine the development optimization information corresponding to the target software, and perform subsequent development optimization on the target software based on the development optimization information.

[0013] In a third aspect, an embodiment of the present invention further provides an electronic device, the electronic device comprising:

[0014] one or more processors;

[0015] A memory for storing one or more programs;

[0016] When the one or more programs are executed by the one or more processors, the one or more processors implement the software defect analysis method provided by any embodiment of the present invention.

[0017] In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements a software defect analysis method as provided in any embodiment of the present invention.

[0018] One embodiment of the above invention has the following advantages or beneficial effects:

[0019] By obtaining multiple target software defects generated by the target software during the test process and the defect description information of each target software defect, the impact of each target software defect is classified according to the impact description information of multiple impact types and the defect description information of each target software defect, and the target impact type corresponding to each target software defect is determined, wherein different impact types are used to characterize different impact dimensions caused by software defects, thereby realizing the impact classification of software defects. According to the target impact types corresponding to all target software defects, an effective analysis of the defect impact is performed, and the development optimization information that needs to be improved in the target software development process is determined, so that the target software is subsequently optimized based on the development optimization information, so that the target software developed after optimization generates fewer software defects, thereby reducing the generation of software defects and improving software development efficiency.

[0020] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0022] Figure 1 is a flow chart of a software defect analysis method provided by an embodiment of the present invention;

[0023] Figure 2 is a flow chart of another software defect analysis method provided by an embodiment of the present invention;

[0024] Figure 3 It is a structural schematic diagram of a software defect analysis device provided by an embodiment of the present invention;

[0025] Figure 4 It is a structural schematic diagram of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0026] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0027] Figure 1 This is a flowchart of a software defect analysis method provided by an embodiment of the present invention. This embodiment is applicable to the situation of performing impact analysis on software defects generated during software testing. The method can be executed by a software defect analysis device, which can be implemented by software and / or hardware and integrated in an electronic device. Figure 1 As shown, the method specifically comprises the following steps:

[0028] S110: Acquire multiple target software defects generated during the test of the target software and defect description information of each target software defect.

[0029] The target software may refer to any software product currently under development. The target software defect refers to the functional defect generated by the target software during the testing process, that is, the problems and errors existing in the target software. There are multiple target software defects. The defect description information of each target software defect is used to describe the detailed information of the target software defect. The defect description information may include the specific manifestation information and impact information of the target software defect, such as when and under what circumstances the target software defect is generated, and the consequences caused by the target software defect.

[0030] Specifically, the target software can be developed multiple times iteratively based on business requirements to optimize the functions of the target software. The target software needs to be tested after each development, and some target software defects will be generated during the testing process. After the target software test is completed, all target software defects generated by the target software and the defect description information of each target software defect are obtained.

[0031] S120. Determine a target impact type corresponding to each target software defect according to the impact description information of the multiple impact types and the defect description information of each target software defect, wherein different impact types are used to characterize different impact dimensions caused by the software defect.

[0032] Among them, different software defects may cause different impacts, such as functional impact, user impact, and operation and maintenance impact, so as to classify all the impacts that may be caused by software defects and obtain multiple different impact types. Each impact type is used to characterize an impact dimension caused by software defects. The impact description information of each impact type refers to the detailed information describing the impact type. The impact description information of the impact type may include the specific manifestation information of the software defect under the impact type, such as the impact information caused by the software defect under the impact type, etc. The target impact type refers to the impact type to which the target software defect belongs.

[0033] Exemplarily, the impact type may include, but is not limited to: software function cannot be used normally type, software function main process cannot be executed type, software performance abnormal type, software transaction unsafe type, user experience abnormal type and software operation and maintenance abnormal type. Among them, the software function cannot be used normally type refers to the user being unable to use the software function normally due to software defects. The software function main process cannot be executed type refers to the main process of the software function being unable to be executed due to software defects. The software performance abnormal type refers to the abnormal software performance caused by software defects. The software transaction unsafe type refers to the situation where there are loopholes and errors in software transactions caused by software defects. The user experience abnormal type refers to the poor user experience caused by software defects. The software operation and maintenance abnormal type refers to the operation and maintenance problems caused by software defects.

[0034] Specifically, for each target software defect, the impact description information of each impact type is matched with the defect description information of the target software defect, the target impact description information that successfully matches the defect description information is determined, and the impact type corresponding to the target impact description information is determined as the target impact type corresponding to the target software defect. Information matching can refer to text matching of the entire information, information keyword matching, or semantic matching, etc.

[0035] Exemplarily, step S120 may include: inputting the defect description information of each target software defect into a target classification model, the target classification model is pre-trained based on the defect description information of historical software defects and the actual impact types corresponding to the historical software defects, and the actual impact types are obtained by labeling the impact description information based on multiple impact types; based on the output of the target classification model, determining the target impact type corresponding to each target software defect.

[0036] Among them, the target classification model can be a deep learning network model for impact classification of software defects. For example, the target classification model can be a multi-classification network model of any network architecture. Specifically, based on the impact description information of multiple impact types and the defect description information of each historical software defect, each historical software defect is marked in advance to obtain the actual impact type corresponding to each historical software defect. The actual impact type corresponding to the historical software defect is used as the training label, and the classification model to be trained is supervised based on the defect description information of the historical software defect to obtain the target classification model after the training, thereby ensuring the classification accuracy of the target classification model. In actual application, for each target software defect, the defect description information of the target software defect is input into the target classification model for impact classification. The target classification model can directly output the target impact type corresponding to the target software defect, or it can output the probability value of the target software defect belonging to each impact type, and then the impact type with the largest probability value output by the target classification model is determined as the target impact type corresponding to the target software defect. By using the target classification model, the target impact type corresponding to the target software defect can be determined more quickly, thereby improving the efficiency of the impact classification of software defects.

[0037] S130 , performing defect impact analysis according to the target impact type corresponding to each target software defect, determining development optimization information corresponding to the target software, and performing subsequent development optimization on the target software based on the development optimization information.

[0038] Among them, the development optimization information can be used to characterize the target development technology that needs to be optimized in the subsequent development of the target software. Different development technologies in the target software can lead to impacts in different dimensions. For example, technologies related to operation and maintenance in the target software can lead to abnormal operation and maintenance. The development optimization information can refer to the improvement reference information when the target software is developed.

[0039] Specifically, based on the target impact types corresponding to all target software defects, it is possible to analyze which type of impact has more target software defects, so that it is necessary to optimize the target development technology associated with this type of impact, and then generate development optimization information containing the target development technology. In the subsequent development stage of the target software, developers can optimize and improve the target development technology of the target software based on the development optimization information, so that the optimized target software produces fewer software defects, thereby effectively reducing the generation of software defects and improving the development and testing efficiency of the target software.

[0040] Exemplarily, step S130 may include: determining the number of target software defects corresponding to each target impact type according to the target impact type corresponding to each target software defect; determining the development optimization information corresponding to the target software according to the target impact type in which the number of target software defects is greater than the preset number of defects, or the target impact type with the largest number of target software defects, so as to perform subsequent development optimization of the target software based on the development optimization information.

[0041] Specifically, based on the target impact types corresponding to all target software defects, the impact classification statistics are performed to determine the number of target software defects under the same target impact type. The more target software defects under a certain target impact type, the greater the impact of the target impact type. The number of target software defects corresponding to each target impact type is compared with the preset defect number, and the target impact type greater than the preset defect number is determined, thereby obtaining a target impact type with a higher impact. Based on the target impact type with a higher impact, the target development technology associated with it is determined, and then the development optimization information for reminding the developer that technical improvement is needed is generated, so that the target software optimizes the target development technology during subsequent development to avoid the same software defects, thereby reducing the generation of software defects. Alternatively, the number of target software defects corresponding to all target impact types is compared, and the target impact type with the largest number of target software defects is determined, thereby obtaining the target impact type with the highest impact. Based on the target impact type with the highest impact, the target development technology associated with it is determined, and then the development optimization information for reminding the developer that technical improvement is needed is generated, so that the target software optimizes the target development technology during subsequent development to avoid the same software defects, thereby reducing the generation of software defects and improving the development and testing efficiency.

[0042] The technical solution of this embodiment obtains multiple target software defects generated by the target software during the test process and the defect description information of each target software defect, and classifies the impact of each target software defect according to the impact description information of multiple impact types and the defect description information of each target software defect, and determines the target impact type corresponding to each target software defect, wherein different impact types are used to characterize different impact dimensions caused by software defects, thereby realizing the impact classification of software defects. According to the target impact types corresponding to all target software defects, an effective analysis of the defect impact is performed, and the development optimization information that needs to be improved in the target software development process is determined, so that the target software is subsequently optimized based on the development optimization information, so that the target software developed after optimization generates a smaller number of software defects, thereby reducing the generation of software defects and improving software development efficiency.

[0043] On the basis of the above technical solution, each impact type may include multiple impact manifestations. Among them, the impact manifestation refers to the behavioral manifestation caused by the software defect, and different impact types correspond to different impact manifestations. Each impact type can be described from multiple impact manifestations. The impact description information of each impact type may include: multiple impact manifestation description information corresponding to multiple impact manifestations. It should be noted that when a software defect causes any impact manifestation under a certain impact type, the impact type is determined to be the impact type corresponding to the software defect.

[0044] Exemplarily, the impact types may include: software function cannot be used normally type, software function main process cannot be executed type, software performance abnormal type, software transaction unsafe type, user experience abnormal type and software operation and maintenance abnormal type.

[0045] Among them, the multiple impact performance description information corresponding to the type of software function cannot be used normally may include: cannot enter the software function normally, cannot open the software function entrance, and the use effect of the software function cannot achieve the expected effect. For example, when the software defect causes the user to be unable to enter the software function normally, cannot open the software function entrance, or the use effect of the software function cannot achieve the expected effect, it is determined that the impact type corresponding to the software defect is the type of software function cannot be used normally.

[0046] The multiple impact performance description information corresponding to the software function main process cannot be executed type may include: the software function transaction cannot be connected, and the software function cannot enter the final success page. For example, when a software defect causes the software function transaction to be unable to connect or unable to enter the final success page, it is determined that the impact type corresponding to the software defect is the software function main process cannot be executed type.

[0047] The multiple impact performance description information corresponding to the software performance anomaly type may include: the software defect is a defect generated during the performance test, the software function response time is greater than the preset time, the memory usage is greater than the preset usage, and the disk usage is greater than the preset usage. For example, when the software defect is a defect generated during the performance test, the software defect causes the software function response time to be greater than the preset time, the memory usage is greater than the preset usage, or the disk usage is greater than the preset usage, it is determined that the impact type corresponding to the software defect is the software performance anomaly type.

[0048] The multiple impact performance description information corresponding to the software transaction unsafe type may include: accounting errors, delayed account arrival, account tampering, and prompting that the transaction is successful but the transaction is not actually successful; for example, when a software defect causes accounting errors, delayed account arrival, account tampering, or prompting that the transaction is successful but the transaction is not actually successful, the impact type corresponding to the software defect is determined to be the type of inability to execute the main process of the software function.

[0049] The multiple impact performance description information corresponding to the user experience abnormality type may include: poor software function usage experience, users cannot understand the software function, poor information prompt method, and unclear information display method; for example, when a software defect causes poor software function usage experience, users cannot understand the software function, poor information prompt method or unclear information display method, the impact type corresponding to the software defect is determined to be the user experience abnormality type.

[0050] The multiple impact performance description information corresponding to the software operation and maintenance abnormality type may include: software defects caused by software environment configuration and software defects caused by characteristic scenarios. For example, when the software defect is caused by software environment configuration or by characteristic scenarios, the impact type corresponding to the software defect is determined to be the software operation and maintenance abnormality type.

[0051] Figure 2 This is a flowchart of another software defect analysis method provided by an embodiment of the present invention. Based on the above embodiments, this embodiment describes in detail the impact classification process of software defects when the impact description information of each impact type includes multiple impact manifestation description information. The explanations of the terms that are the same or corresponding to the above embodiments are not repeated here.

[0052] See also Figure 2 Another software defect analysis method provided in this embodiment specifically includes the following steps:

[0053] S210: Acquire multiple target software defects generated during the test of the target software and defect description information of each target software defect.

[0054] S220: For each target software defect, match each impact manifestation description information corresponding to each impact type with the defect description information of the target software defect to obtain successfully matched target impact manifestation description information.

[0055] Specifically, for each target software defect, each impact manifestation description information corresponding to each impact type can be matched with the defect description information of the target software defect in turn according to the order of the impact types, and the target impact manifestation description information that successfully matches the defect description information can be determined. If the defect description information of the target software defect successfully matches a certain impact manifestation description information under a certain impact type, the impact manifestation description information is directly determined as the target impact manifestation description information caused by the target software defect, and there is no need to continue the subsequent information matching of the impact type. Among them, information matching can refer to text matching of the entire information, information keyword matching, or semantic matching, etc.

[0056] Exemplarily, step S220 may include: inputting each impact performance description information corresponding to each impact type and the defect description information of the target software defect into the target semantic matching model to perform semantic matching of the description information, and obtain the information similarity between each impact performance description information and the defect description information; based on the information similarity between each impact performance description information and the defect description information, determining the target impact performance description information that has been successfully matched.

[0057] The target semantic matching model may be a deep learning model for matching the semantic similarity between the impact performance description information and the defect description information. The target semantic matching model may be a text semantic matching model of any network architecture.

[0058] Specifically, for each target software defect, each impact manifestation description information corresponding to each impact type and the defect description information of the target software defect are input into the target semantic matching model. The target semantic matching model analyzes and calculates the semantic similarity between each impact manifestation description information and the defect description information, and determines and outputs the information similarity between each impact manifestation description information and the defect description information. The higher the information similarity, the higher the probability that the impact manifestation description information and the defect description information describe the same content. The impact manifestation description information with the highest information similarity to the defect description information is determined as the target impact manifestation description information that has been successfully matched. By using the target semantic matching model to perform semantic matching of description information, the accuracy of impact classification can be further improved.

[0059] S230: Determine the impact type corresponding to the target impact performance description information as the target impact type corresponding to the target software defect.

[0060] Specifically, based on the correspondence between the impact type and the impact manifestation description information, the impact type corresponding to the target impact manifestation description information is determined as the target impact type corresponding to the target software defect. By using multiple impact manifestation description information corresponding to each impact type to perform impact classification, the accuracy of impact classification can be further improved, thereby improving the accuracy of defect impact analysis.

[0061] S240: Perform defect impact analysis according to the target impact type corresponding to each target software defect, determine development optimization information corresponding to the target software, and perform subsequent development optimization on the target software based on the development optimization information.

[0062] The technical solution of this embodiment obtains successfully matched target impact performance description information by matching each impact performance description information corresponding to each impact type with the defect description information of the target software defect, and determines the impact type corresponding to the target impact performance description information as the target impact type corresponding to the target software defect, thereby using multiple impact performance description information corresponding to each impact type to perform impact classification, which can further improve the accuracy of impact classification and thereby improve the accuracy of defect impact analysis.

[0063] The following is an embodiment of a software defect analysis device provided in an embodiment of the present invention. The device and the software defect analysis methods of the above-mentioned embodiments belong to the same inventive concept. For details not described in detail in the embodiment of the software defect analysis device, reference can be made to the embodiment of the above-mentioned software defect analysis method.

[0064] Figure 3 This is a schematic diagram of the structure of a software defect analysis device provided by an embodiment of the present invention. This embodiment is applicable to the situation where the impact analysis of software defects generated during software testing is performed. Figure 3 As shown, the device specifically includes: a target software defect acquisition module 310, a target impact type determination module 320 and a development optimization information determination module 330.

[0065] Among them, the target software defect acquisition module 310 is used to obtain multiple target software defects generated by the target software during the testing process and the defect description information of each target software defect; the target impact type determination module 320 is used to determine the target impact type corresponding to each target software defect based on the impact description information of multiple impact types and the defect description information of each target software defect, wherein different impact types are used to characterize different impact dimensions caused by software defects; the development optimization information determination module 330 is used to perform defect impact analysis according to the target impact type corresponding to each target software defect, determine the development optimization information corresponding to the target software, so as to perform subsequent development optimization on the target software based on the development optimization information.

[0066] The technical solution of this embodiment obtains multiple target software defects generated by the target software during the test process and the defect description information of each target software defect, and classifies the impact of each target software defect according to the impact description information of multiple impact types and the defect description information of each target software defect, and determines the target impact type corresponding to each target software defect, wherein different impact types are used to characterize different impact dimensions caused by software defects, thereby realizing the impact classification of software defects. According to the target impact types corresponding to all target software defects, an effective analysis of the defect impact is performed, and the development optimization information that needs to be improved in the target software development process is determined, so that the target software is subsequently optimized based on the development optimization information, so that the target software developed after optimization generates a smaller number of software defects, thereby reducing the generation of software defects and improving software development efficiency.

[0067] Optionally, the target impact type determination module 320 is specifically configured to:

[0068] The defect description information of each target software defect is input into a target classification model, wherein the target classification model is pre-trained based on the defect description information of historical software defects and the actual impact types corresponding to the historical software defects, and the actual impact types are obtained by labeling the impact description information of multiple impact types; based on the output of the target classification model, the target impact type corresponding to each target software defect is determined.

[0069] Optionally, each impact type includes multiple impact manifestations, wherein the impact manifestation refers to a behavioral manifestation caused by a software defect, and different impact types correspond to different impact manifestations;

[0070] The impact description information of each impact type includes: multiple impact manifestation description information corresponding to multiple impact manifestations.

[0071] Optionally, the impact type includes: software function cannot be used normally, software function main process cannot be executed, software performance abnormality, software transaction insecurity, user experience abnormality, and software operation and maintenance abnormality;

[0072] The multiple impact performance description information corresponding to the type of the software function being unable to be used normally includes: being unable to enter the software function normally, being unable to open the software function entrance, and the use effect of the software function being unable to achieve the expected effect;

[0073] The multiple impact performance description information corresponding to the software function main process execution failure type includes: the software function transaction cannot be connected, and the software function cannot enter the final success page;

[0074] The multiple performance impact description information corresponding to the software performance anomaly type includes: the software defect is a defect generated during the performance test, the software function response time is greater than the preset time, the memory usage is greater than the preset usage, and the disk usage is greater than the preset usage.

[0075] The multiple impact performance description information corresponding to the software transaction insecurity type includes: account error, delayed account arrival, account tampering, and prompt transaction success but actual failure of the transaction;

[0076] The multiple impact performance description information corresponding to the user experience abnormality type includes: poor software function usage experience, user inability to understand software functions, poor information prompt method, and unclear information display method;

[0077] The multiple impact performance description information corresponding to the software operation and maintenance exception type includes: software defects caused by software environment configuration, and software defects caused by characteristic scenarios.

[0078] Optionally, the target impact type determination module 320 includes:

[0079] a target impact performance description information determination unit, configured to match, for each target software defect, each impact performance description information corresponding to each impact type with the defect description information of the target software defect, to obtain successfully matched target impact performance description information;

[0080] The target impact type determination unit is used to determine the impact type corresponding to the target impact performance description information as the target impact type corresponding to the target software defect.

[0081] Optionally, the target impact performance description information determination unit is specifically configured to:

[0082] Each impact manifestation description information corresponding to each impact type and the defect description information of the target software defect are input into the target semantic matching model to perform semantic matching of the description information, and obtain the information similarity between each impact manifestation description information and the defect description information; based on the information similarity between each impact manifestation description information and the defect description information, determine the target impact manifestation description information that has been successfully matched.

[0083] Optionally, an optimization information determination module 330 is developed, specifically for:

[0084] According to the target impact type corresponding to each of the target software defects, the number of target software defects corresponding to each of the target impact types is determined; according to the target impact type in which the number of target software defects is greater than the preset number of defects, or the target impact type in which the number of target software defects is the largest, the development optimization information corresponding to the target software is determined, so as to perform subsequent development optimization on the target software based on the development optimization information.

[0085] The software defect analysis device provided in the embodiment of the present invention can execute the software defect analysis method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects for executing the software defect analysis method.

[0086] It is worth noting that in the embodiment of the above-mentioned software defect analysis device, the various units and modules included are only divided according to functional logic, but are not limited to the above-mentioned division, as long as the corresponding functions can be achieved; in addition, the specific names of the functional units are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of the present invention.

[0087] Figure 4 A schematic diagram of the structure of an electronic device provided by an embodiment of the present invention. Figure 4 A block diagram of an exemplary electronic device 12 suitable for use in implementing embodiments of the present invention is shown. Figure 4 The electronic device 12 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.

[0088] like Figure 4 As shown, the electronic device 12 is in the form of a general purpose computing device. The components of the electronic device 12 may include, but are not limited to: one or more processors or processing units 16, a system memory 28, and a bus 18 that connects various system components (including the system memory 28 and the processing unit 16).

[0089] Bus 18 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor or a local bus using any of a variety of bus architectures. By way of example, these architectures include, but are not limited to, an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MAC) bus, an Enhanced ISA bus, a Video Electronics Standards Association (VESA) local bus, and a Peripheral Component Interconnect (PCI) bus.

[0090] The electronic device 12 typically includes a variety of computer system readable media. These media can be any available media that can be accessed by the electronic device 12, including volatile and non-volatile media, removable and non-removable media.

[0091] The system memory 28 may include computer system readable media in the form of volatile memory, such as random access memory 30 (RAM) and / or cache memory 32. The electronic device 12 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, the storage system 34 may be used to read and write non-removable, non-volatile magnetic media ( Figure 4 not shown, usually called a "hard drive"). Although Figure 4 Not shown in the figure, a disk drive for reading and writing to a removable non-volatile disk (e.g., a "floppy disk"), and an optical disk drive for reading and writing to a removable non-volatile optical disk (e.g., a CD-ROM, a DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to the bus 18 via one or more data medium interfaces. The system memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to perform the functions of the various embodiments of the present invention.

[0092] A program / utility 40 having a set (at least one) of program modules 42 may be stored, for example, in system memory 28, such program modules 42 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment. Program modules 42 generally perform the functions and / or methods of the embodiments described herein.

[0093] The electronic device 12 may also communicate with one or more external devices 14 (e.g., keyboards, pointing devices, displays 24, etc.), may communicate with one or more devices that enable a user to interact with the electronic device 12, and / or may communicate with any device that enables the electronic device 12 to communicate with one or more other computing devices (e.g., network cards, modems, etc.). Such communication may be performed via an input / output (I / O) interface 22. Furthermore, the electronic device 12 may also communicate with one or more networks (e.g., local area networks (LANs), wide area networks (WANs), and / or public networks, such as the Internet) via a network adapter 20. As shown, the network adapter 20 communicates with other modules of the electronic device 12 via a bus 18. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with the electronic device 12, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0094] The processing unit 16 executes various functional applications and data processing by running the program stored in the system memory 28, for example, implementing a software defect analysis method provided by any embodiment of the present invention, the method comprising:

[0095] Acquire multiple target software defects generated during the testing process of the target software and defect description information of each of the target software defects;

[0096] Determine, according to the impact description information of the multiple impact types and the defect description information of each of the target software defects, a target impact type corresponding to each of the target software defects, wherein different impact types are used to characterize different impact dimensions caused by the software defects;

[0097] Defect impact analysis is performed according to the target impact type corresponding to each of the target software defects, and development optimization information corresponding to the target software is determined, so as to perform subsequent development optimization on the target software based on the development optimization information.

[0098] Of course, those skilled in the art can understand that the processor can also implement the technical solution of the software defect analysis method provided by any embodiment of the present invention.

[0099] This embodiment provides a computer-readable storage medium having a computer program stored thereon. When the program is executed by a processor, the steps of the software defect analysis method provided in any embodiment of the present invention are implemented. The method includes:

[0100] Acquire multiple target software defects generated during the testing process of the target software and defect description information of each of the target software defects;

[0101] Determine, according to the impact description information of the multiple impact types and the defect description information of each of the target software defects, a target impact type corresponding to each of the target software defects, wherein different impact types are used to characterize different impact dimensions caused by the software defects;

[0102] Defect impact analysis is performed according to the target impact type corresponding to each of the target software defects, and development optimization information corresponding to the target software is determined, so as to perform subsequent development optimization on the target software based on the development optimization information.

[0103] The computer storage medium of the embodiment of the present invention can adopt any combination of one or more computer-readable media. The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium can 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 (non-exhaustive list) of computer-readable storage media include: 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 or 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 this document, a computer-readable storage medium can be any tangible medium containing or storing a program, which can be used by an instruction execution system, device or device or used in combination with it.

[0104] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, which carry computer-readable program code. 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 a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0105] The program code embodied on the computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[0106] Computer program code for performing the operations of the present invention may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0107] It should be understood by those skilled in the art that the modules or steps of the present invention described above can be implemented by a general-purpose computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, optionally, they can be implemented by a program code executable by a computer device, so that they can be stored in a storage device and executed by the computing device, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. Thus, the present invention is not limited to any specific combination of hardware and software.

[0108] Note that the above are only preferred embodiments of the present invention and the technical principles used. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in more detail through the above embodiments, the present invention is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. A software defect analysis method, characterized in that: include: Acquire multiple target software defects generated during the testing process of the target software and defect description information of each of the target software defects; Determine, according to the impact description information of the multiple impact types and the defect description information of each of the target software defects, a target impact type corresponding to each of the target software defects, wherein different impact types are used to characterize different impact dimensions caused by the software defects; Defect impact analysis is performed according to the target impact type corresponding to each of the target software defects, and development optimization information corresponding to the target software is determined, so as to perform subsequent development optimization on the target software based on the development optimization information.

2. The method according to claim 1, characterized in that The determining, according to the impact description information of the multiple impact types and the defect description information of each target software defect, a target impact type corresponding to each target software defect comprises: Inputting the defect description information of each target software defect into a target classification model, wherein the target classification model is pre-trained based on the defect description information of historical software defects and the actual impact type corresponding to the historical software defects, wherein the actual impact type is obtained by labeling the impact description information of multiple impact types; Based on the output of the target classification model, a target impact type corresponding to each target software defect is determined.

3. The method according to claim 2, characterized in that Each impact type includes multiple impact manifestations, wherein the impact manifestation refers to the behavior manifestation caused by the software defect, and different impact types correspond to different impact manifestations; The impact description information of each impact type includes: multiple impact manifestation description information corresponding to multiple impact manifestations.

4. The method according to claim 3, characterized in that The impact types include: software function cannot be used normally, software function main process cannot be executed, software performance abnormality, software transaction insecurity, user experience abnormality, and software operation and maintenance abnormality; The multiple impact performance description information corresponding to the type of the software function being unable to be used normally includes: being unable to enter the software function normally, being unable to open the software function entrance, and the use effect of the software function being unable to achieve the expected effect; The multiple impact performance description information corresponding to the software function main process execution failure type includes: the software function transaction cannot be connected, and the software function cannot enter the final success page; The multiple performance-affecting description information corresponding to the software performance anomaly type includes: the software defect is a defect generated during the performance test, the software function response time is greater than the preset time, the memory usage is greater than the preset usage, and the disk usage is greater than the preset usage; The multiple impact performance description information corresponding to the software transaction insecurity type includes: account error, delayed account arrival, account tampering, and prompt transaction success but actual failure of transaction; The multiple impact performance description information corresponding to the user experience abnormality type includes: poor software function usage experience, user inability to understand software functions, poor information prompt method, and unclear information display method; The multiple impact performance description information corresponding to the software operation and maintenance exception type includes: software defects caused by software environment configuration, and software defects caused by characteristic scenarios.

5. The method according to claim 3, characterized in that: The determining, according to the impact description information of the multiple impact types and the defect description information of each target software defect, a target impact type corresponding to each target software defect comprises: For each of the target software defects, each impact performance description information corresponding to each impact type is matched with the defect description information of the target software defect to obtain successfully matched target impact performance description information; The impact type corresponding to the target impact performance description information is determined as the target impact type corresponding to the target software defect.

6. The method according to claim 5, characterized in that The step of matching each impact manifestation description information corresponding to each impact type with the defect description information of the target software defect to obtain the successfully matched target impact manifestation description information includes: Input each impact manifestation description information corresponding to each impact type and the defect description information of the target software defect into the target semantic matching model to perform semantic matching of the description information, and obtain the information similarity between each impact manifestation description information and the defect description information; Based on the information similarity between each impact performance description information and the defect description information, the successfully matched target impact performance description information is determined.

7. The method according to any one of claims 1 to 6, characterized in that: The defect impact analysis is performed according to the target impact type corresponding to each of the target software defects, and the development optimization information corresponding to the target software is determined, so as to perform subsequent development optimization on the target software based on the development optimization information, including: Determine the number of target software defects corresponding to each target impact type according to the target impact type corresponding to each target software defect; According to the target impact type in which the number of defects of the target software is greater than the preset number of defects, or the target impact type in which the number of defects of the target software is the largest, development optimization information corresponding to the target software is determined, so as to perform subsequent development optimization on the target software based on the development optimization information.

8. A software defect analysis device, characterized in that: include: A target software defect acquisition module is used to acquire multiple target software defects generated during the test of the target software and defect description information of each target software defect; A target impact type determination module, used to determine the target impact type corresponding to each target software defect according to the impact description information of multiple impact types and the defect description information of each target software defect, wherein different impact types are used to characterize different impact dimensions caused by software defects; The development optimization information determination module is used to perform defect impact analysis according to the target impact type corresponding to each target software defect, determine the development optimization information corresponding to the target software, and perform subsequent development optimization on the target software based on the development optimization information.

9. An electronic device, characterized in that: The electronic device comprises: one or more processors; A memory for storing one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the software defect analysis method as described in any one of claims 1-7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the software defect analysis method as described in any one of claims 1 to 7 is implemented.

Images