Software defect repairing method and device, electronic equipment, storage medium and program product

By matching and correlating the current software defect information entered by the user and the historical information in the target defect library in software defect repair, the problem of difficulty in positioning of developers is solved and the efficiency of software defect repair is improved.

CN119003333APending Publication Date: 2024-11-22PICC INFORMATION TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410943058.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-12
Publication Date
2024-11-22

AI Technical Summary

Technical Problem

The existing software defect repair methods are ineffective in quickly locate defect problems due to changes in the development team, which leads to low efficiency in software defect repair.

Method used

By obtaining the current software defect information entered by the test user, matching it with the historical software defect information in the target defect library, displaying the matching historical software defect information, and after the user confirms it, it will be associated with the current software defect information and sending it to the development user terminal.

Benefits of technology

Improves the efficiency of development users in software defect repair, ensuring that developers can quickly locate and fix software defects.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119003333A_ABST
    Figure CN119003333A_ABST
Patent Text Reader

Abstract

The invention provides a software defect repairing method and device, electronic equipment, a storage medium and a program product, and relates to the technical field of software testing. The method comprises the following steps: acquiring current software defect information input by a test user through an input device; performing matching based on the current software defect information and historical software defect information in a target defect library; in response to the condition that the target historical software defect is matched with the current software defect information, displaying the target historical software defect information; in response to the received confirmation operation on the target historical software defect input by the test user through the input device, performing association processing on the target historical software defect and the current software defect information; and sending the current software defect information and the target historical software defect associated with the current software defect information to the development user terminal. By means of the method, the software defect repairing efficiency of a development user can be effectively improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of software testing technology, and in particular to a method, device, electronic device, storage medium and program product for repairing software defects. Background Art

[0002] At present, in the existing software defect repair method, when the tester finds a new defect, he fills in the basic information of the defect and transfers the basic information of the defect to the developer. The developer searches the defect library for historical defects that are similar or identical to the basic information of the defect based on the basic information of the defect filled in by the tester, and repairs the current defect based on the similar or identical historical defects. However, due to the large number of development teams, the developer responsible for repairing the software code defect may not be the original developer responsible for writing the software code. Therefore, the developer responsible for repairing the software code defect cannot quickly locate the defect problem based on the basic information of the defect, and further, cannot quickly search the defect library for historical defects that are similar or identical to the basic information of the defect, resulting in low efficiency of software defect repair. Summary of the invention

[0003] The present application provides a method, device, electronic device, storage medium and program product for repairing software defects, so as to solve the technical problem of low efficiency of existing software defect repairing.

[0004] In a first aspect, the present application provides a method for repairing a software defect, comprising:

[0005] Acquiring current software defect information input by a test user through an input device;

[0006] Matching the current software defect information with historical software defect information in a target defect library;

[0007] In response to a target historical software defect matching the current software defect information, displaying the target historical software defect information;

[0008] In response to receiving a confirmation operation of the target historical software defect input by the test user through the input device, associating the target historical software defect with the current software defect information;

[0009] The current software defect information and the target historical software defect associated with the current software defect information are sent to a development user terminal.

[0010] In one possible design, the current software defect information includes a current defect label;

[0011] The matching based on the current software defect information with the historical software defect information in the target defect library includes:

[0012] Matching the current defect tag with the historical defect tags of the historical software defect information;

[0013] In response to a matching value between the current defect tag and the historical defect tag being higher than a preset matching value, it is determined that the historical software defect information corresponding to the historical defect tag matches the current software defect information.

[0014] In a possible design, in response to a target historical software defect matching the current software defect information, displaying the target historical software defect information includes:

[0015] In response to N target historical software defect information all matching the current software defect information, the N target historical software defect information are displayed in descending order of matching degree, wherein N is a positive integer greater than 1.

[0016] In a possible design, the associating the target historical software defect with the current software defect information includes:

[0017] Generating a hyperlink pointing to the target historical software defect address;

[0018] The hyperlink is added to the current software defect information.

[0019] In one possible design, it also includes:

[0020] In response to the historical software defect information not matching the current software defect information, a target defect tag is generated in the target defect library based on the current software defect information.

[0021] In one possible design, it also includes:

[0022] In response to receiving a confirmation result of the target historical software defect information sent by the development user terminal, a target defect label of the current software defect information is generated, and the target defect label is the same as the defect label of the target historical software defect.

[0023] In one possible design, it also includes:

[0024] In response to receiving the defect repair information sent by the development user terminal, the target defect library is updated.

[0025] In a second aspect, the present application provides a software defect repair device, comprising:

[0026] An acquisition module, used to acquire current software defect information input by a test user through an input device;

[0027] A matching module, configured to match the current software defect information with the historical software defect information in the target defect library;

[0028] A display module, configured to display the target historical software defect information in response to a target historical software defect matching the current software defect information;

[0029] an associating module, configured to, in response to receiving a confirmation operation of the target historical software defect input by the test user through the input device, associate the target historical software defect with the current software defect information;

[0030] The sending module is used to send the current software defect information and the target historical software defect associated with the current software defect information to a development user terminal.

[0031] In a third aspect, the present application provides an electronic device, comprising: a processor, and a memory and an output device communicatively connected to the processor;

[0032] The memory stores computer-executable instructions; the output device is used to display target historical software defect information;

[0033] The processor executes the computer-executable instructions stored in the memory to implement the method as described in any one of the first aspects.

[0034] In a fourth aspect, the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, they are used to implement the method as described in any one of the first aspects.

[0035] In a fifth aspect, the present application provides a computer program product, including a computer program, which implements the method described in any one of the first aspects when executed by a processor.

[0036] The software defect repair method, device, electronic device, storage medium and program product provided by the present application obtain the current software defect information input by the test user through the input device; match the current software defect information with the historical software defect information in the target defect library; in response to the target historical software defect matching the current software defect information, display the target historical software defect information; in response to receiving the confirmation operation of the target historical software defect input by the test user through the input device, associate the target historical software defect with the current software defect information; send the current software defect information and the target historical software defect associated with the current software defect information to the development user terminal. The software defect repair method allows the test user who clearly knows the defect problem to confirm the historical software defect information associated with the current software defect information, and sends the current software defect information and the target historical software defect associated with the current software defect information to the development user terminal, so that the development user can quickly locate the problem of the current software defect through the historical software defect information, which can effectively improve the efficiency of the development user in repairing software defects. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0038] Figure 1 An application scenario diagram corresponding to the method for repairing software defects provided in an embodiment of the present application;

[0039] Figure 2 A flowchart of a method for repairing software defects provided in one embodiment of the present application;

[0040] Figure 3 A schematic diagram of an interactive process of a method for repairing software defects provided in an embodiment of the present application;

[0041] Figure 4 A schematic diagram of the structure of a software defect repair device provided in an embodiment of the present application;

[0042] Figure 5 This is a schematic diagram of the structure of an electronic device provided in a real-time example of the present application.

[0043] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0044] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0045] It should be noted that the software defect repair method, device, electronic device, storage medium and program product of the present application can be used in the field of software testing technology, and can also be used in any field other than software testing. The application field of the software defect repair method, device, electronic device, storage medium and program product of the present application is not limited.

[0046] In order to clearly understand the technical solution of the present application, the solution of the prior art is first introduced in detail.

[0047] A defect database is a database or information system that systematically collects, organizes and manages various defect information. It is mainly used to record, track, analyze and report problems or non-conformities in various products, systems, services or processes, such as programming errors, missing functions, performance bottlenecks and interface problems. In the existing software defect repair method, when the tester finds a new defect, he fills in the basic information of the defect and transfers the basic information of the defect to the developer. The developer searches the defect database for historical defects similar or identical to the basic information of the defect based on the basic information of the defect filled in by the tester, and repairs the current defect based on the similar or identical historical defects. However, due to the large number of development teams, the developer responsible for repairing the software code defect may not be the original developer responsible for writing the software code. Therefore, the developer responsible for repairing the software code defect cannot quickly locate the defect problem based on the basic information of the defect, and then cannot quickly query the defect database for historical defects similar or identical to the basic information of the defect, resulting in low efficiency of software defect repair.

[0048] Therefore, in order to improve the efficiency of repairing software defects when facing technical problems in the prior art, first, after the test user completes filling in the basic information of the defect, the basic information of the defect is matched with the existing historical defects in the defect library, so as to query whether there is a historical defect matching the basic information of the defect in the defect library. If there is a historical defect matching the basic information of the defect, the test user is asked to confirm whether the historical defect is the same or similar to the basic information of the defect. If they are the same or similar, the basic information of the defect is associated with the historical defect, and the basic information of the defect associated with the historical defect is transferred to the developer.

[0049] Figure 1An application scenario diagram corresponding to the method for repairing software defects provided in an embodiment of the present application, such as Figure 1 As shown, the software defect repairing system corresponding to the software defect repairing method in the application scenario provided by this embodiment includes: an input device 11 , a test user terminal 12 , a target defect library 13 and a development user terminal 14 . Specifically, the test user inputs the current software defect information through the input device 11, the test user terminal 12 obtains the current software defect information input by the input device 11, and sends the current software defect information to the target defect library 13 to match it with the historical software defect information in the target defect library 13. When there is historical software defect information matching the current software defect information, the target defect library 13 sends the historical software defect information to the test user terminal 12, and the test user terminal 12 displays the historical software defect information. After the test user confirms the displayed historical software defect information, the test user terminal 12 inputs a confirmation operation for the target historical software defect through the input device 11. After receiving the confirmation operation for the target historical software defect, the test user terminal 12 associates the target historical software defect with the current software defect information, and sends the associated current software defect information and the target historical software defect to the development user terminal 14, so that the development user can perform subsequent software defect repair work according to the current software defect information and the target historical software defect received by the development user terminal 14.

[0050] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0051] Figure 2 A flowchart of a method for repairing software defects provided by an embodiment of the present application is shown in FIG. Figure 2 As shown, the execution subject of this embodiment is a software defect repair device, which can be implemented by a computer program or a medium storing relevant computer programs, such as a USB flash drive and / or a CD, etc.; or, it can also be implemented by a physical device integrated or installed with relevant computer programs, such as a chip, an electronic device, etc. The electronic device can be a computer or a server, etc. The method for repairing software defects provided in this embodiment includes the following steps:

[0052] S201: Acquire current software defect information input by a test user through an input device.

[0053] Specifically, when the test user finds a new defect during the test process, the test user inputs the current software defect information corresponding to the new defect through the input device, and the test user terminal obtains the current software defect information input by the test user for subsequent work of repairing the software defect.

[0054] The current software defect information is defect information corresponding to new defects discovered by the test user during testing.

[0055] Optionally, when entering the current software defect information, the tester needs to fill in the defect information template so that the developer can fully understand the current software defect information. The defect information template includes the following contents:

[0056] (1) Title: Briefly summarize the core issue of the new defect.

[0057] (2) Detailed description: Detailed description of the new defect’s manifestation, triggering conditions (such as specific test environment, test equipment, operating system, browser, data status, etc.), scope of impact, steps to reproduce the defect, and comparison between expected results and actual results.

[0058] (3) Affected version: Indicates the software version or branch where the defect is located.

[0059] (4) Severity: Select the appropriate severity level and priority.

[0060] (5) Related attachments: upload screenshots, log files, video recordings and other supporting materials.

[0061] (6) Defect keywords and defect labels: Testers determine defect keywords that can summarize the defect problem based on the nature of the defect. Defect labels can be error type labels (such as crash, interface error, missing function, etc.), defect corresponding function module labels (such as login module and insurance module, etc.), and function labels.

[0062] Optionally, in this embodiment, the input device may be a keyboard, a mouse, a touch screen, or voice input, etc., and the type of the input device may be selected according to the actual application scenario.

[0063] Optionally, the acquired current software defect information is saved locally or in a defect library for subsequent reference in repairing other defects.

[0064] S202: Match the current software defect information with the historical software defect information in the target defect library.

[0065] Specifically, after obtaining the current software defect information, the current software defect information is matched with the historical software defect information in the target defect library to determine whether there is historical software defect information similar or identical to the current software defect information, thereby providing data reference for repairing the current software defect.

[0066] The target defect database is an existing database for storing software defect information; the historical software defect information is basic information of existing software defects stored in the target defect database.

[0067] Optionally, in this embodiment, when matching current software defect information with historical software defect information, first, obtain defect keywords and / or defect tags in the current software defect information, and then match them in the target defect library based on the defect keywords and / or defect tags to obtain historical software defect information that meets the matching requirements.

[0068] S203: In response to a target historical software defect matching the current software defect information, display the target historical software defect information.

[0069] Specifically, when it is determined that a target historical software defect matches the current software defect information, it indicates that there is defect information in the target defect library that is the same as or similar to the current software defect information, and then the target historical software defect information is displayed. Thus, the test user can confirm whether the displayed historical software defect information is the same as or similar to the current software defect information, so as to ensure that subsequent development users can effectively repair the current software defect based on the historical software defect information.

[0070] The target historical software defect is an existing defect that is the same as or similar to the current software defect information.

[0071] Optionally, in this embodiment, the target historical software defects that meet the matching requirements may be one or more. Further, when there are multiple target historical software defects that meet the matching requirements, they are sorted from high to low or from low to high according to the matching degree, so as to facilitate the test user to confirm.

[0072] Optionally, in this embodiment, the device for displaying the target historical software defect information can be a PC or a mobile terminal, which is communicatively connected to the test user terminal; wherein the PC can be a desktop computer and the mobile terminal can be a tablet computer.

[0073] S204 : in response to receiving a confirmation operation of the target historical software defect input by the test user through the input device, associating the target historical software defect with the current software defect information.

[0074] Specifically, when the test user confirms that the target historical software defect is the same as or similar to the current software defect, the test user terminal inputs a confirmation operation for the target historical software defect through the input device, so that the test user terminal can associate the target historical software defect with the current software defect information according to the received confirmation result.

[0075] Optionally, there are multiple ways to associate the target historical software defect with the current software defect information, for example, generating an "associated defect" field in the current software defect information and generating keywords or tags for the target historical software defect; or, generating address information for the target historical software defect in the current software defect information, etc. In this embodiment, the specific method of this association processing is not limited.

[0076] Optionally, an automated association tool is used to associate the keywords, tags or address information of the target historical software defect with the current software defect information. In this embodiment, the automated association tool is not limited as long as the above functions can be achieved.

[0077] S205: Send the current software defect information and the target historical software defect associated with the current software defect information to the development user terminal.

[0078] Specifically, after associating the target historical software defect with the current software defect information, the associated current software defect information is sent to the development user terminal, so that the development user can quickly locate the problem of the current software defect based on the target historical software defect associated with the current software defect information, thereby improving the efficiency of repairing the current software defect.

[0079] Optionally, the development user determines whether the current software defect information received by the development user terminal is a real defect. If so, the current software defect is repaired according to the target software defect information. If not, it indicates that the software defect raised by the test user is a false defect, and the result of the false defect is input into the development user terminal. The development user terminal sends the result of the false defect to the test user terminal, and the test user confirms the current software defect information. If the test user finds that there is no defect after confirmation, the software defect repair process ends. If the test user finds that there is still a defect after confirmation, the defect problem is re-entered into the test user terminal to carry out the software defect repair process.

[0080] Optionally, before the development user repairs the current software defect according to the target software defect information, a comparison analysis is performed based on the current software defect information and the target software defect information to confirm whether the two are the same or similar defects. If so, the current software defect information is filled with the same defect label as the target software defect information; if not, a new defect label can be filled based on the current software defect information.

[0081] The method for repairing software defects provided in this embodiment obtains the current software defect information input by the test user through the input device; matches the current software defect information with the historical software defect information in the target defect library; in response to the target historical software defect matching the current software defect information, displays the target historical software defect information; in response to receiving the confirmation operation of the target historical software defect input by the test user through the input device, associates the target historical software defect with the current software defect information; and sends the current software defect information and the target historical software defect associated with the current software defect information to the development user terminal. The method of this embodiment allows the test user who clearly knows the defect problem to confirm the historical software defect information associated with the current software defect information, and sends the current software defect information and the target historical software defect associated with the current software defect information to the development user terminal. Then, the development user can quickly locate the problem of the current software defect through the historical software defect information, which can effectively improve the efficiency of the development user in repairing software defects.

[0082] As an optional implementation manner, based on any of the above embodiments, the current software defect information includes a current defect label; matching the current software defect information with the historical software defect information in the target defect library includes:

[0083] Matching the current defect label with the historical defect label of the historical software defect information;

[0084] In response to a matching value between the current defect tag and the historical defect tag being higher than a preset matching value, it is determined that the historical software defect information corresponding to the historical defect tag matches the current software defect information.

[0085] Specifically, when matching the current software defect information with the historical software defect information in the target defect library, the current defect label in the current software defect information is matched with the historical defect label of the historical software defect information. When the matching value between the historical defect label and the current defect label is higher than the preset matching value, it is considered that the historical software defect information corresponding to the historical defect label matches the current software defect information.

[0086] Among them, the current defect label is a label determined by the test user based on information such as the defect error type and the functional module corresponding to the defect; the historical defect label is an existing label that can summarize information such as the historical software defect error type and the functional module corresponding to the defect; the preset matching value is a matching degree value set by the test user. In this embodiment, the preset matching value is not specifically limited and can be flexibly adjusted according to the actual matching effect.

[0087] Optionally, when there are multiple historical defect tags whose matching values ​​are all higher than the preset matching value, it is considered that the multiple historical software defect information corresponding to the multiple historical defect tags all match the current software defect information, and the multiple historical software defect information are arranged from high to low or from low to high according to the matching value.

[0088] Optionally, the current software information may include one or more current defect tags. When there are multiple current defect tags, the test user assigns different weights to the multiple current defect tags according to their importance. For example, the function description tag can more directly reflect the nature of the defect than the defect cause tag. Therefore, the setting weight of the function description tag is greater than the defect cause tag. Accordingly, when the matched historical software defects are sorted, the matching value of the historical software defects with only the function description tag will be higher than the historical software defects with only the defect cause tag.

[0089] Optionally, the current software defect information also includes current defect keywords, which are words summarized based on defect causes, defect descriptions, etc. Specifically, when the current defect keywords are used to match the historical software defect information, a semantic relevance tool is used to compare and analyze whether there are words in the historical software defect information that are the same or similar to the current defect keywords.

[0090] Further optionally, when analyzing the historical software defect information based on the semantic relevance tool and the current defect keywords, a relevance analysis is performed based on a weight allocation rule. The weight allocation rule includes the following:

[0091] (1) The weight of the historical defect sentence that is exactly the same as the current defect keyword is greater than the weight of the historical defect sentence that is semantically similar or close to the current defect keyword.

[0092] (2) The weight of the historical defect sentence located in the historical defect title is greater than the weight of the historical defect sentence located in the historical defect content description.

[0093] In the method for repairing software defects provided by this embodiment, the current software defect information includes a current defect label; matching is performed based on the current software defect information and the historical software defect information in the target defect library, including: matching the historical defect label based on the current defect label and the historical software defect information; in response to the matching value between the current defect label and the historical defect label being higher than a preset matching value, determining that the historical software defect information corresponding to the historical defect label matches the current software defect information. The method of this embodiment calculates the matching degree between the current defect label and the historical defect label, and sets a preset matching value to accurately determine the historical defect label that meets the matching requirements, thereby effectively determining the historical software defect information that matches the current software defect information.

[0094] As an optional implementation, based on any of the above embodiments, in response to a target historical software defect matching the current software defect information, the target historical software defect information is displayed, including:

[0095] In response to N target historical software defect information all matching the current software defect information, the N target historical software defect information are displayed in descending order of matching degree, where N is a positive integer greater than 1.

[0096] Specifically, in response to a target historical software defect matching the current software defect information, when the target historical software defect information is displayed, if there are N target historical software defects that all match the current software defect information, the N historical software defect information are sorted and displayed from high to low according to the matching degree.

[0097] Optionally, one of the N target historical software defect information with the highest matching degree is highlighted; or multiple target historical software defect information with high matching degrees are all highlighted. Thus, it is convenient for the test user to quickly know the matching degree between the current software defect information and the N target historical software defect information.

[0098] Optionally, when displaying the target historical software defect information, one or more of the historical defect label, historical defect title, and historical defect content description of the target historical software defect information may be selected for display, thereby facilitating the test user to quickly understand the target historical software defect information corresponding to the historical defect content according to the displayed historical defect content.

[0099] The software defect repair method provided in this embodiment, in response to a target historical software defect matching the current software defect information, displays the target historical software defect information, including: in response to N target historical software defect information all matching the current software defect information, displaying the N target historical software defect information from high to low according to the matching degree, wherein N is a positive integer greater than 1. In the method of this embodiment, when there are N target historical software defect information all matching the current software defect information, the N target historical software defect information are displayed from high to low according to the matching degree, so as to facilitate the user to quickly know the matching degree between the current software defect information and the N target historical software defect information.

[0100] As an optional implementation, based on any of the above embodiments, the target historical software defect is associated with the current software defect information, including:

[0101] Generate a hyperlink pointing to the target historical software defect address;

[0102] Add a hyperlink to the current software defect information.

[0103] Specifically, when associating the target historical software defect with the current software defect information, first, a hyperlink pointing to the target historical software defect address is generated, and the hyperlink is added to the current software defect information to facilitate rapid jumping to the target historical software defect information page according to the hyperlink.

[0104] Optionally, when it is necessary to associate multiple target historical software defects with current software defect information, multiple hyperlinks generated from the multiple target historical software defects are arranged from high to low or from low to high according to the matching degree between the multiple target historical software defects and the current software defect information.

[0105] Optionally, the historical defect code corresponding to the target historical software defect is obtained, and the historical defect number is added to the current software defect information. Thus, the development user can query the corresponding target historical software defect information according to the historical defect code. Of course, the target historical software defect can also be associated with the current software defect information in other ways.

[0106] The method for repairing software defects provided in this embodiment associates the target historical software defect with the current software defect information, including: generating a hyperlink pointing to the target historical software defect address; adding the hyperlink to the current software defect information. The method of this embodiment associates the target historical software defect address with the current software defect information by generating a hyperlink pointing to the target historical software defect address, so that the user can quickly jump to the page of the target historical software defect information by clicking the hyperlink.

[0107] As an optional implementation manner, based on any of the above embodiments, the method for repairing a software defect further includes:

[0108] In response to no historical software defect information matching the current software defect information, a target defect tag is generated in a target defect library based on the current software defect information.

[0109] Specifically, when there is no historical software defect information matching the current software defect information in the target defect library, it indicates that the current software defect information is a new defect, and thus a target defect label is generated in the target defect library based on the current software defect information.

[0110] Among them, the target defect label is a defect label that can summarize the current software defect information.

[0111] Optionally, the target defect label may be one or more, which is not limited in this embodiment.

[0112] Optionally, a current defect keyword and / or a current defect tag in the current software defect information is obtained, and the current defect keyword and / or the current defect tag is determined as a target defect tag.

[0113] The software defect repair method provided by this embodiment further includes: in response to no historical software defect information matching the current software defect information, generating a target defect label in the target defect library based on the current software defect information. In the method of this embodiment, when no historical software defect information is matched, a target defect label is generated in the target defect library, so as to facilitate the subsequent retrieval of the current software defect information through the target defect label, so as to serve as a reference for the subsequent repair of other software defects.

[0114] As an optional implementation manner, based on any of the above embodiments, the method for repairing a software defect further includes:

[0115] In response to receiving the confirmation result of the target historical software defect information sent by the development user terminal, a target defect label of the current software defect information is generated, and the target defect label is the same as the defect label of the target historical software defect.

[0116] Specifically, after the development user terminal receives the current software defect information and the associated target historical software defect, the development user compares and confirms the current software defect information with the target historical software defect information. When the development user confirms that the target historical software defect information is the same or similar to the current software defect information, the development user inputs the confirmation result of the target historical software defect information to the development user terminal through the input device. Thereafter, the development user terminal sends the confirmation result of the target historical software defect information to the test user terminal. After receiving the confirmation result, the test user terminal generates a target defect label for the current software defect information, and the target defect label is the same as the defect label of the target historical software defect.

[0117] Optionally, when the development user compares and confirms the current software defect information with the target historical software defect information, a comparative analysis is performed based on the defect label, defect description, software version corresponding to the defect, and defect severity in the current software defect information and the target historical software defect information.

[0118] Optionally, before comparing and confirming the current software defect information with the target historical software defect information, the development user confirms whether the current software defect information is a real defect. When the current software defect information is a false defect, the result of confirming it as a false defect is input into the development user terminal and sent to the test user terminal. The test user reconfirms the current software defect. When the test user still confirms that the current software defect is a real defect, the current software defect information is re-uploaded to the test user terminal to perform the software defect repair process. When the test user confirms that the current software defect is a false defect, the software defect repair process is terminated.

[0119] The method for repairing software defects provided by this embodiment also includes: in response to receiving the confirmation result of the target historical software defect information sent by the development user terminal, generating a target defect label of the current software defect information, and the target defect label is the same as the defect label of the target historical software defect. In the method of this embodiment, when the development user confirms that the target historical software defect information and the current software defect information are the same or similar defects, the target defect label of the current software defect information is set to be the same as the defect label of the target historical software defect. Thereby, it is convenient to classify and store the current software defect information in the target defect library.

[0120] As an optional implementation manner, based on any of the above embodiments, the method for repairing a software defect further includes:

[0121] In response to receiving the defect repair information sent by the development user terminal, the target defect library is updated.

[0122] Specifically, after the development user completes the repair of the current defect based on the current software defect information and the target historical software defect information, the defect repair information is supplemented in the current software defect information, and the current software defect information supplemented with the defect repair information is imported into the target defect library to update the target defect library.

[0123] Optionally, the defect repair information includes repair solutions and defect root causes, etc. The repair solution includes specific measures taken to repair the current defect, such as modified code, configuration changes, database operations, etc. The defect root causes include descriptions of programming errors, poor software code change management, incomplete test coverage, and missing documents.

[0124] Optionally, the number of historical defect information corresponding to the historical defect label in the target database is obtained, and the historical defect labels are sorted from high to low according to the number of corresponding historical defect information. Thus, the defect problems that often occur during software development and testing can be known based on the sorted historical defect labels, and then targeted training can be provided to test users and development users to reduce the probability of defects during software development and testing.

[0125] Optionally, the target defect library is cleaned, classified, and labeled regularly to ensure the accuracy and availability of the target defect library.

[0126] The method for repairing software defects provided by this embodiment further includes: updating the target defect library in response to receiving defect repair information sent by the development user terminal. After the current software defect is repaired, the method of this embodiment uses the defect repair information to update and improve the target defect library, thereby providing better data reference for subsequent other software defect repair work.

[0127] Figure 3 A schematic diagram of an interactive process of a method for repairing a software defect provided in an embodiment of the present application is shown in FIG. Figure 3 As shown, the execution subject of this embodiment is a software defect repair system, which includes: a development user terminal and a test user terminal. Specifically, the interactive process of the software defect repair method is as follows:

[0128] S301: The test user terminal obtains current software defect information input by the test user through an input device.

[0129] S302: The test user terminal matches the current software defect information with the historical software defect information in the target defect library.

[0130] S303: In response to the fact that no historical software defect information matches the current software defect information, the test user terminal generates a target defect label in a target defect library based on the current software defect information.

[0131] S304: In response to the target historical software defect matching the current software defect information, the test user terminal displays the target historical software defect information.

[0132] S305 . In response to receiving the confirmation operation of the target historical software defect input by the test user through the input device, the test user terminal associates the target historical software defect with the current software defect information.

[0133] S306: The testing user terminal sends the current software defect information and the target historical software defect associated with the current software defect information to the development user terminal.

[0134] S307: After receiving the current software defect information and the target historical software defect associated with the current software defect information, the development user terminal displays the current software defect information.

[0135] S308: The development user terminal receives the confirmation result of whether the current software defect information is a real defect input by the development user through the confirmation device.

[0136] Specifically, when a confirmation result that the current software defect information is not a real defect is received, the confirmation result that the current software defect information is not a real defect is sent to the test user terminal. The test user reconfirms whether the current software defect information is a real defect. If so, the defect information is re-entered through the input device; if not, the software defect repair process ends.

[0137] S309: In response to receiving the confirmation result that the current software defect information is a real defect, the development user terminal displays the target historical software defect information associated with the current software information.

[0138] S310: The development user terminal receives a matching judgment result of the target historical software defect and the current software defect information input by the development user through an input device.

[0139] S311. The development user terminal sends a matching judgment result of the target historical software defect and the current software defect information to the test user terminal.

[0140] S312: In response to receiving the judgment result of the confirmation match of the target historical software defect information sent by the development user terminal, the test user terminal generates a target defect label of the current software defect information, and the target defect label is the same as the defect label of the target historical software defect.

[0141] S313: In response to receiving the judgment result of mismatch of the target historical software defect information sent by the development user terminal, the test user terminal generates a target defect label based on the current software defect information.

[0142] S314: The development user terminal receives the defect repair information input by the development user through the input device.

[0143] S315: The development user terminal sends defect repair information to the test user terminal.

[0144] It should be noted that there is no particular order in which step S315 and step S311 are executed.

[0145] S316: The test user terminal receives the defect repair information, and updates the target defect library based on the defect repair information.

[0146] It should be noted that after the defect is fixed, the test user verifies the repaired software program. When the verification passes, the software defect repair process ends; when the verification fails, the developer continues to repair the software defect.

[0147] Figure 4 A schematic diagram of the structure of a software defect repair device provided in an embodiment of the present application is shown in FIG. Figure 4As shown, the apparatus for repairing software defects provided by this embodiment is located in an electronic device. The apparatus for repairing software defects provided by this embodiment 40 comprises: an acquisition module 41 , a matching module 42 , a display module 43 , an association module 44 , and a sending module 45 .

[0148] Among them, the acquisition module 41 is used to acquire the current software defect information input by the test user through the input device; the matching module 42 is used to match the historical software defect information in the target defect library based on the current software defect information; the display module 43 is used to display the target historical software defect information in response to the target historical software defect matching the current software defect information; the association module 44 is used to associate the target historical software defect with the current software defect information in response to receiving the confirmation operation of the target historical software defect input by the test user through the input device; the sending module 45 is used to send the current software defect information and the target historical software defect associated with the current software defect information to the development user terminal.

[0149] The software defect repairing device provided in this embodiment can execute Figure 2 and Figure 3 The specific implementation principle and technical effect of the method embodiment shown in are similar and will not be repeated here.

[0150] Optionally, the current software defect information includes a current defect label.

[0151] Accordingly, the matching module 42, when matching the current software defect information with the historical software defect information in the target defect library, is specifically used to: match the historical defect label based on the current defect label with the historical defect label of the historical software defect information; in response to the matching value between the current defect label and the historical defect label being higher than the preset matching value, determine that the historical software defect information corresponding to the historical defect label matches the current software defect information.

[0152] Optionally, the display module 43, when displaying the target historical software defect information in response to a target historical software defect matching the current software defect information, is specifically used for: in response to N target historical software defect information all matching the current software defect information, displaying the N target historical software defect information in descending order of matching degree, where N is a positive integer greater than 1.

[0153] Optionally, when associating the target historical software defect with the current software defect information, the association module 44 is specifically used to: generate a hyperlink pointing to the address of the target historical software defect; and add the hyperlink to the current software defect information.

[0154] Optionally, the software defect repairing device 40 provided in this embodiment further includes: a label generating module and a database updating module.

[0155] Optionally, the label generation module is used to generate a target defect label in the target defect library based on the current software defect information in response to no historical software defect information matching the current software defect information.

[0156] Optionally, the label generation module is used to generate a target defect label for the current software defect information in response to receiving a confirmation result of the target historical software defect information sent by the development user terminal, and the target defect label is the same as the defect label of the target historical software defect.

[0157] Optionally, the database updating module is used to update the target defect database in response to receiving defect repair information sent by the development user terminal.

[0158] Figure 5 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application is shown in FIG. Figure 5 As shown, the electronic device 50 provided in this embodiment includes: a processor 51, a memory 52 and an output device 53 which are communicatively connected to the processor.

[0159] The memory 52 stores computer-executable instructions, and the output device 53 is used to display target historical software defect information; the processor 51 executes the computer-executable instructions stored in the memory 52 to implement the software defect repair method provided in any one of the above embodiments.

[0160] The program may include program codes, and the program codes include computer-executable instructions. The memory 52 may include a high-speed RAM memory, and may also include a non-volatile memory, such as at least one disk memory.

[0161] In this embodiment, the memory 52 and the output device 53 are connected to the processor 51 via a bus 54. The bus 54 may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus. The bus 54 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 5 The fact that only one straight line is used in the diagram does not mean that there is only one bus or only one type of bus.

[0162] An embodiment of the present application also provides a computer-readable storage medium, including computer-executable instructions stored in the computer-readable storage medium, and the computer-executable instructions are used to implement the software defect repair method provided by any of the above embodiments when executed by a processor.

[0163] An embodiment of the present application also provides a computer program product, including a computer program, which implements the method for repairing software defects provided by any of the above embodiments when the computer program is executed by a processor.

[0164] It should be noted that, for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the present application is not limited by the described order of actions, because according to the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily required by the present application.

[0165] It should be further noted that, although the various steps in the flowchart are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless there is a clear description in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a portion of the steps in the flowchart may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these sub-steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

[0166] It should be understood that the above-mentioned device embodiments are only illustrative, and the device of the present application can also be implemented in other ways. For example, the division of units / modules in the above-mentioned embodiments is only a logical function division, and there may be other division methods in actual implementation. For example, multiple units, modules or components can be combined, or can be integrated into another system, or some features can be ignored or not executed.

[0167] In addition, unless otherwise specified, each functional unit / module in each embodiment of the present application may be integrated into one unit / module, each unit / module may exist physically separately, or two or more units / modules may be integrated together. The above-mentioned integrated unit / module may be implemented in the form of hardware or in the form of a software program module.

[0168] If the integrated unit / module is implemented in the form of hardware, the hardware may be a digital circuit, an analog circuit, etc. The physical implementation of the hardware structure includes but is not limited to transistors, memristors, etc. If not specifically stated, the processor may be any appropriate hardware processor, such as a CPU, a GPU, an FPGA, a DSP, an ASIC, etc. If not specifically stated, the storage unit may be any appropriate magnetic storage medium or magneto-optical storage medium, such as a resistive random access memory RRAM (Resistive Random Access Memory), a dynamic random access memory DRAM (Dynamic Random Access Memory), a static random access memory SRAM (Static Random-Access Memory), an enhanced dynamic random access memory EDRAM (Enhanced Dynamic Random Access Memory), a high-bandwidth memory HBM (High-Bandwidth Memory), a hybrid memory cube HMC (Hybrid Memory Cube), etc.

[0169] If the integrated unit / module is implemented in the form of a software program module and sold or used as an independent product, it can be stored in a computer-readable memory. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art or all or part of the technical solution, can be embodied in the form of a software product, which is stored in a memory and includes several instructions for a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the various embodiments of the present application. The aforementioned memory includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk and other media that can store program codes.

[0170] In the above embodiments, the description of each embodiment has its own emphasis. For parts not described in detail in a certain embodiment, please refer to the relevant description of other embodiments. The technical features of the above embodiments can be combined arbitrarily. In order to make the description concise, all possible combinations of the technical features in the above embodiments are not described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0171] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any modification, use or adaptation of the present application, which follows the general principles of the present application and includes common knowledge or customary techniques in the art that are not disclosed in the present application. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present application are indicated by the following claims.

[0172] It should be understood that the present application is not limited to the precise structures that have 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 application is limited only by the appended claims.

Claims

1. A method for repairing software defects, characterized in that: include: Acquiring current software defect information input by a test user through an input device; Matching the current software defect information with historical software defect information in a target defect library; In response to a target historical software defect matching the current software defect information, displaying the target historical software defect information; In response to receiving a confirmation operation of the target historical software defect input by the test user through the input device, associating the target historical software defect with the current software defect information; The current software defect information and the target historical software defect associated with the current software defect information are sent to a development user terminal.

2. The method according to claim 1, characterized in that: The current software defect information includes a current defect label; The matching based on the current software defect information with the historical software defect information in the target defect library includes: Matching the current defect tag with the historical defect tags of the historical software defect information; In response to a matching value between the current defect tag and the historical defect tag being higher than a preset matching value, it is determined that the historical software defect information corresponding to the historical defect tag matches the current software defect information.

3. The method according to claim 1, characterized in that: In response to a target historical software defect matching the current software defect information, displaying the target historical software defect information includes: In response to N target historical software defect information all matching the current software defect information, the N target historical software defect information are displayed in descending order of matching degree, wherein N is a positive integer greater than 1.

4. The method according to claim 1, characterized in that: The associating the target historical software defect with the current software defect information includes: Generating a hyperlink pointing to the target historical software defect address; The hyperlink is added to the current software defect information.

5. The method according to any one of claims 1 to 4, characterized in that Also includes: In response to the historical software defect information not matching the current software defect information, a target defect tag is generated in the target defect library based on the current software defect information.

6. The method according to any one of claims 1 to 4, characterized in that Also includes: In response to receiving a confirmation result of the target historical software defect information sent by the development user terminal, a target defect label of the current software defect information is generated, and the target defect label is the same as the defect label of the target historical software defect.

7. The method according to any one of claims 1 to 4, characterized in that Also includes: In response to receiving the defect repair information sent by the development user terminal, the target defect library is updated.

8. A device for repairing software defects, characterized in that: include: An acquisition module, used to acquire current software defect information input by a test user through an input device; A matching module, configured to match the current software defect information with the historical software defect information in the target defect library; A display module, configured to display the target historical software defect information in response to a target historical software defect matching the current software defect information; an associating module, configured to, in response to receiving a confirmation operation of the target historical software defect input by the test user through the input device, associate the target historical software defect with the current software defect information; The sending module is used to send the current software defect information and the target historical software defect associated with the current software defect information to a development user terminal.

9. An electronic device, characterized in that: include: A processor, and a memory and an output device communicatively connected to the processor; The memory stores computer-executable instructions; the output device is used to display target historical software defect information; The processor executes the computer-executable instructions stored in the memory to implement the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 7 when executed by a processor.

11. A computer program product, characterized in that The invention comprises a computer program, which implements the method according to any one of claims 1 to 7 when being executed by a processor.