Defect management method and device of system, computer equipment and storage medium

Abstract

The invention discloses a system defect management method and device, computer equipment and a storage medium, and the method comprises the steps: obtaining defect data of a target system, the defect data comprising interface information and defect information; determining a target application of the defect data based on the interface information; carrying out breakpoint debugging on the defect information by utilizing a debugging module of the target application, and generating a debugging branch link, a defect reason and a correct parameter; on the basis of the preset defect management rule base, the debugging branch links, the defect reasons and the correct parameters are managed, and the debugging branch links, the defect reasons and the correct parameters are generated by performing breakpoint debugging on the defect information by using the debugging module of the target application, so that multi-dimensional analysis on the defect data is realized; the comprehensive integrity of defect analysis information is improved, management is carried out according to debugging branch links, defect reasons and correct parameters, automatic management of system defects is achieved, and diversity and flexibility of defect management are improved.

Description

Technical Field

[0001] The present application relates to the field of data processing, and in particular to a method, device, computer equipment and storage medium for systematic defect management. Background Art

[0002] With the development of the Internet, more and more companies are pursuing agile iterations while ensuring software quality, avoiding production failures, reducing unnecessary losses, and improving customer satisfaction.

[0003] In related technologies, for system defect management, a large amount of manpower is usually invested in handling production fault reporting events and production problem analysis. This manual processing method has many similar problems or repeated problems that are repeatedly checked and processed, which is not conducive to the agile iteration and performance tuning of the system. Summary of the invention

[0004] The embodiments of the present application provide a systematic defect management method, apparatus, computer equipment and storage medium to solve the technical problem that similar problems or repeated problems are repeatedly checked and processed in manual defect processing, resulting in cumbersome and inefficient defect management.

[0005] In one aspect, the present application provides a system defect management method, the system defect management method comprising:

[0006] Acquire defect data of a target system, wherein the defect data includes interface information and defect information of the target system, wherein the interface information includes a method name and / or a class name of the defect data, and the defect information is data related to the defect in the target system;

[0007] Determine the target application to which the defect data belongs based on the interface information;

[0008] Perform breakpoint debugging on the defect information using the debugging module of the target application to generate a debugging branch link, a defect cause, and a correct parameter, wherein the debugging branch link includes multiple stage links where the defect data is located in the software development program;

[0009] Based on a preset defect management rule base, the debugging branch link, the defect cause and the correct parameter are managed.

[0010] In some implementation schemes of the present application, the preset defect management rule base includes at least one of defect track rules, defect attribute field rules, problem responsibility attribution rules and defect repair rules, and each rule corresponds to at least one rule indicator;

[0011] The managing the debugging branch link, the defect cause and the correct parameter based on the preset defect management rule includes:

[0012] Based on the defect management rule base, extracting rule indicators from the debugging branch link, the defect cause and the correct parameter to obtain defect indicator data;

[0013] A defect management report is generated based on the defect indicator data.

[0014] In some implementation schemes of the present application, the defect management rule base is the defect track rule; the rule indicators of the defect track rule include status indicators and flow indicators; the defect management report includes at least one of a defect track map, a defect distribution map, a defect detail list, a defect warning list, a defect responsibility attribution list, a defect viewing authority list, and a defect repair result list;

[0015] The defect management rule base is the defect track rule; based on the defect management rule base, rule indicator extraction is performed on the debugging branch link, the defect cause and the correct parameter to obtain defect indicator data, including:

[0016] According to the flow indicator, extracting the process sequence of the defect information in the software development process from the debugging branch link;

[0017] Extracting a status identifier of the defect information from the debugging branch link according to the status indicator;

[0018] The generating of the defect management report based on the defect indicator data comprises:

[0019] The state identifier and the process sequence are filled into a preset defect trajectory map template to generate a defect trajectory map.

[0020] In some embodiments of the present application, the defect management rule base is the defect attribute field rule; the rule indicator of the defect attribute field rule includes a problem attribute field indicator;

[0021] The step of extracting rule indicators from the debugging branch link, the defect cause and the correct parameter based on the defect management rule base to obtain defect indicator data includes:

[0022] According to the problem attribute field indicator, extract multiple problem data of the defect information from the debugging branch link, extract the problem cause of the defect information from the defect cause, and extract the improvement measures of the defect information from the correct parameters;

[0023] The generating of the defect management report based on the defect indicator data comprises:

[0024] Generate the defect detail list based on the multiple problem data, the problem causes and the problem measures; and / or generate the defect distribution map based on the multiple problem data, the problem causes and the problem measures; and / or generate the defect warning list based on the multiple problem data, the problem causes and the problem measures.

[0025] In some implementation schemes of the present application, the defect management rule base is the problem responsibility attribution rule; the rule indicators of the problem responsibility attribution rule include defect link indicators and responsibility role indicators;

[0026] The step of extracting rule indicators from the debugging branch link, the defect cause and the correct parameter based on the defect management rule base to obtain defect indicator data includes:

[0027] Extracting a defect link identifier of the defect information from the debugging branch link and the defect cause according to the defect link indicator;

[0028] Extracting a responsible role identifier of the defect information from the debugging branch link and the defect cause according to the responsible role indicator;

[0029] The generating of the defect management report based on the defect indicator data comprises:

[0030] The defect responsibility attribution list is generated according to the defect link identifier and the responsible role identifier; and / or, the defect viewing permission list is generated according to the defect link identifier and the responsible role identifier.

[0031] In some implementation schemes of the present application, the defect management rule base is the defect repair rule; the rule indicator of the defect repair rule includes a repair data indicator;

[0032] The step of extracting rule indicators from the debugging branch link, the defect cause and the correct parameter based on the defect management rule base to obtain defect indicator data includes:

[0033] Extracting repair data of the defect information from the error cause and the correct parameter according to the repair data indicator;

[0034] The generating of the defect management report based on the defect indicator data comprises:

[0035] Perform regression testing according to the repair data to generate the test result;

[0036] The defect information and test results are filled into a preset defect repair result table to obtain the defect repair result list.

[0037] In some embodiments of the present application, after generating a defect management report based on the defect indicator data, the method further includes:

[0038] Performing system tuning on the target system based on the defect management report; and / or, iteratively updating the target system based on the defect management report.

[0039] On the other hand, the present application provides a defect management device for a system, the defect management device for the system comprising:

[0040] An acquisition module, used to acquire defect data of a target system, wherein the defect data includes interface information and defect information of the target system, wherein the interface information includes a method name and / or a class name of the defect data, and the defect information is information related to defects in the target system;

[0041] A determination module, configured to determine a target application to which the defect data belongs based on the interface information;

[0042] A generation module, used to perform breakpoint debugging on the defect information by using the debugging module of the target application, and generate a debugging branch link, a defect cause and a correct parameter, wherein the debugging branch link includes multiple stage links where the defect data is located in the software development program;

[0043] The management module is used to manage the debugging branch link, the defect cause and the correct parameter based on a preset defect management rule base.

[0044] In some implementation schemes of the present application, the preset defect management rule base includes at least one of defect track rules, defect attribute field rules, problem responsibility attribution rules and defect repair rules, and each rule corresponds to at least one rule indicator; the management module is specifically used to:

[0045] Based on the defect management rule base, extracting rule indicators from the debugging branch link, the defect cause and the correct parameter to obtain defect indicator data;

[0046] A defect management report is generated based on the defect indicator data.

[0047] In some implementation schemes of the present application, the defect management rule base is the defect track rule; the rule indicators of the defect track rule include status indicators and flow indicators; the defect management report includes at least one of a defect track map, a defect distribution map, a defect detail list, a defect warning list, a defect responsibility attribution list, a defect viewing authority list, and a defect repair result list;

[0048] The management module is also specifically used for:

[0049] According to the flow indicator, extracting the process sequence of the defect information in the software development process from the debugging branch link;

[0050] Extracting a status identifier of the defect information from the debugging branch link according to the status indicator;

[0051] The state identifier and the process sequence are filled into a preset defect trajectory map template to generate a defect trajectory map.

[0052] In some implementation schemes of the present application, the defect management rule base is the defect attribute field rule; the rule indicator of the defect attribute field rule includes a problem attribute field indicator; the management module is specifically further used for:

[0053] According to the problem attribute field indicator, extract multiple problem data of the defect information from the debugging branch link, extract the problem cause of the defect information from the defect cause, and extract the improvement measures of the defect information from the correct parameters;

[0054] Generate the defect detail list based on the multiple problem data, the problem causes and the problem measures; and / or generate the defect distribution map based on the multiple problem data, the problem causes and the problem measures; and / or generate the defect warning list based on the multiple problem data, the problem causes and the problem measures.

[0055] In some implementation schemes of the present application, the defect management rule base is the problem responsibility attribution rule; the rule indicators of the problem responsibility attribution rule include defect link indicators and responsibility role indicators; the management module is also specifically used for:

[0056] Extracting a defect link identifier of the defect information from the debugging branch link and the defect cause according to the defect link indicator;

[0057] Extracting a responsible role identifier of the defect information from the debugging branch link and the defect cause according to the responsible role indicator;

[0058] The defect responsibility attribution list is generated according to the defect link identifier and the responsible role identifier; and / or, the defect viewing permission list is generated according to the defect link identifier and the responsible role identifier.

[0059] In some implementation schemes of the present application, the defect management rule base is the defect repair rule; the rule indicator of the defect repair rule includes a repair data indicator; and the management module is specifically further used for:

[0060] Extracting repair data of the defect information from the error cause and the correct parameter according to the repair data indicator;

[0061] Perform regression testing according to the repair data to generate the test result;

[0062] The defect information and test results are filled into a preset defect repair result table to obtain the defect repair result list.

[0063] In some embodiments of the present application, the defect management device of the system further includes:

[0064] A tuning module is used to perform system tuning on the target system based on the defect management report; and / or an iteration module is used to iteratively update the target system based on the defect management report.

[0065] On the other hand, the present application also provides a computer device, the computer device comprising:

[0066] one or more processors;

[0067] Memory; and

[0068] One or more applications, wherein the one or more applications are stored in the memory and are configured to be executed by the processor to implement the steps in the defect management method of the system according to any one of the first aspects.

[0069] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program is loaded by a processor to execute the steps in the defect management method of the system as described in any one of the first aspects.

[0070] The present application obtains defect data of a target system, wherein the defect data includes interface information and defect information of the target system, wherein the interface information includes a method name and / or a class name of the defect data, and the defect information is defect-related data in the target system; determines a target application to which the defect data belongs based on the interface information; uses a debugging module of the target application to perform breakpoint debugging on the defect information, and generates a debugging branch link, a defect cause, and a correct parameter, wherein the debugging branch link includes multiple stage links of the defect data in a software development program; manages the debugging branch link, the defect cause, and the correct parameter based on a preset defect management rule base; since the debugging module of the target application is used to perform breakpoint debugging on the defect information, and generates a debugging branch link, a defect cause, and a correct parameter, wherein the debugging branch link includes multiple stage links of the defect data in a software development program, a multi-dimensional analysis of the defect data is realized, the comprehensive integrity of the defect analysis information is improved, and management is performed based on the debugging branch link, the defect cause, and the correct parameter, thereby realizing automated management of system defects and improving the diversity and flexibility of defect management. BRIEF DESCRIPTION OF THE DRAWINGS

[0071] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.

[0072] Figure 1 This is a schematic diagram of an application scenario of a defect management device of a system provided in an embodiment of the present application;

[0073] Figure 2 It is a schematic diagram of an embodiment of a defect management method of a system provided in an embodiment of the present application;

[0074] Figure 3 It is a schematic diagram of the structure of an embodiment of a defect management device of the system provided in an embodiment of the present application;

[0075] Figure 4 It is a schematic diagram of the structure of an embodiment of a computer device provided in the embodiments of the present application. DETAILED DESCRIPTION

[0076] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of this application.

[0077] In the description of the present application, it should be understood that the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features. In the description of the present application, "plurality" means two or more, unless otherwise clearly and specifically defined.

[0078] In this application, the word "exemplary" is used to mean "used as an example, illustration, or description." Any embodiment described in this application as "exemplary" is not necessarily to be construed as being preferred or advantageous over other embodiments. The following description is given to enable any technician in the field to implement and use the present application. In the following description, details are listed for the purpose of explanation. It should be understood that a person of ordinary skill in the art can recognize that the present application can be implemented without using these specific details. In other instances, well-known structures and processes will not be elaborated in detail to avoid obscuring the description of the present application with unnecessary details. Therefore, the present application is not intended to be limited to the embodiments shown, but is consistent with the widest scope consistent with the principles and features disclosed in the present application.

[0079] It should be noted that since the method of the embodiment of the present application is executed in a computer device, the processing objects of each computer device exist in the form of data or information. For example, the time described in this article is actually time information, which is used to characterize the information of time. It can be understood that if the size, quantity, position, etc. are mentioned in the subsequent embodiments, they all exist in the corresponding data form to facilitate the computer device to process, and the details will not be repeated here.

[0080] The embodiments of the present application provide a system defect management method, apparatus, computer equipment, and storage medium, which are described in detail below.

[0081] See also Figure 1 , Figure 1 Schematic diagram of a defect management device of the system provided in an embodiment of the present application. The defect management device of the system may include a computer device 100. The computer device 100 is integrated with the defect management device of the system. Figure 1 Computer equipment in.

[0082] In the embodiment of the present application, the computer device 100 is mainly used to obtain defect data of a target system, wherein the defect data includes interface information and defect information of the target system, wherein the interface information includes a method name and / or a class name of the defect data, and the defect information is information related to defects in the target system; based on the interface information, a target application to which the defect data belongs is determined; a debugging module of the target application is used to perform breakpoint debugging on the defect information, and a debugging branch link, a defect cause, and correct parameters are generated, wherein the debugging branch link includes multiple stage links of the defect data in the software development program; based on a preset defect management rule base, the debugging branch link, the defect cause, and the correct parameters are managed. Since the debugging module of the target application is used to perform breakpoint debugging on the defect information, and a debugging branch link, a defect cause, and correct parameters are generated, a multi-dimensional analysis of the defect data is realized, and the comprehensive integrity of the defect analysis information is improved. Moreover, management is performed based on the debugging branch link, the defect cause, and the correct parameters, thereby realizing automated management of system defects and improving the diversity and flexibility of defect management.

[0083] In the embodiment of the present application, the computer device 100 may be an independent server, or a server network or server cluster composed of servers. For example, the computer device 100 described in the embodiment of the present application includes but is not limited to a computer, a network host, a single network server, a plurality of network server sets or a cloud server composed of a plurality of servers. The cloud server is composed of a large number of computers or network servers based on cloud computing.

[0084] It is understandable that the computer device 100 used in the embodiments of the present application may be a device including both receiving and transmitting hardware, that is, a device having receiving and transmitting hardware capable of performing two-way communication on a two-way communication link. Such a device may include: a cellular or other communication device having a single-line display or a multi-line display or a cellular or other communication device without a multi-line display. The specific computer device 100 may be a desktop terminal or a mobile terminal, and the computer device 100 may also be one of a mobile phone, a tablet computer, a laptop computer, etc.

[0085] Those skilled in the art will understand that Figure 1 The application scenario shown in the figure is only one application scenario of the present application solution and does not constitute a limitation on the application scenario of the present application solution. Other application scenarios may also include Figure 1 More or less computer equipment as shown in Figure 1 Only one computer device is shown in the figure. It can be understood that the defect management device of the system can also include one or more other services, which are not specifically limited here.

[0086] In addition, if Figure 1 As shown, the defect management device of the system may further include a storage module 200 for storing data, and the data may include information of the target system, defect data, interface information of the defect data, and the like.

[0087] It should be noted that Figure 1 The scenario diagram of the defect management device of the system shown is only an example. The defect management device of the system and the scenario described in the embodiment of the present application are intended to more clearly illustrate the technical solution of the embodiment of the present application, and do not constitute a limitation on the technical solution provided in the embodiment of the present application. Ordinary technicians in this field can know that with the evolution of the defect management device of the system and the emergence of new business scenarios, the technical solution provided in the embodiment of the present application is also applicable to similar technical problems.

[0088] First, a defect management method for a system is provided in an embodiment of the present application. The execution subject of the defect management method for the system is a defect management device for the system. The defect management device for the system is applied to a computer device. The defect management method for the system includes: obtaining defect data of a target system, wherein the defect data includes interface information and defect information of the target system, wherein the interface information includes a method name and / or a class name of the defect data, and the defect information is information related to defects in the target system; determining a target application to which the defect data belongs based on the interface information; performing breakpoint debugging on the defect information using a debugging module of the target application, generating a debugging branch link, a defect cause, and a correct parameter, wherein the debugging branch link includes multiple stage links of the defect data in a software development program; managing the debugging branch link, the defect cause, and the correct parameter based on a preset defect management rule base. Since the debug module of the target application is used to perform breakpoint debugging on the defect data, generating the debugging branch link, the defect cause, and the correct parameter, a multi-dimensional analysis of the defect data is realized, and the comprehensive integrity of the defect analysis information is improved. Moreover, management is performed based on the debugging branch link, the defect cause, and the correct parameter, thereby realizing automatic management of system defects and improving the diversity and flexibility of defect management.

[0089] like Figure 2 FIG. 1 is a flow chart of an embodiment of a defect management method of a system in an embodiment of the present application. The defect management method of the system may include the following steps 301 to 304, which are as follows:

[0090] 301. Obtain defect data of a target system, where the defect data includes interface information and defect data of the target system, where the interface information includes a method name and / or a class name of the defect data, and the defect data is information related to defects in the target system.

[0091] The target system refers to a software system that has defect data and needs defect management. Defect data refers to defect data on the target system, and its source can be production failure events of ITSM (ITSM management object), automated test conditions on TCMP (Transportation Control and Mobility Plan), data on monitoring software monitoring failures, recorded production problems, and operational failure events.

[0092] The defect data includes interface information and defect information in the target system, wherein the interface information in the target system includes the method name and / or class name of the defect data, and the interface information configuration of the defect data can be performed, wherein the method name refers to the name of the method function involved in the calling interface in the defect data to implement a certain application function, and the class name refers to the name of the class file involved in the calling interface in the defect data to implement a certain application function. In this embodiment, the method name and class name contained in the defect data can be used as interface information separately, or a method name and a class name can be used as interface information at the same time.

[0093] Defect information is information related to the defect, for example, it may be one or more test data of failed tests, or one or more problem data entered by users, or a combination of test data of failed tests and problem data, which is not limited here.

[0094] Specifically, defect data may be obtained from a defect management platform of the target system for subsequent defect analysis and management of the target system.

[0095] 302. Determine a target application to which the defect data belongs based on the interface information.

[0096] The target application refers to the application of defect data on the target system. Since multiple applications are usually deployed on a target system, for example, a monitoring system may be deployed with monitoring applications, collection applications, summary and analysis applications, etc.

[0097] Specifically, since the method names and class names of the software programs applied on the target system are different, the software program that is consistent with the interface information is determined as the target application by querying the method name and type from the software program library in the target system based on the method name and / or class name in the interface information.

[0098] 303. Perform breakpoint debugging on the defect information using the debugging module of the target application to generate debugging branch links, defect causes, and correct parameters, wherein the debugging branch links include multiple stage links where the defect data is located in the software development program.

[0099] Among them, the debugging module refers to a tool for debugging the application data. The debugging module in this embodiment is a breakpoint debugging module, which is used to perform breakpoint debugging on multiple logical branches, and each logical branch corresponds to a judgment condition. When the condition is met, the debugging of the next logical branch will continue. If the condition is not met, it will switch to a new logical branch or end. Each logical branch pre-sets an available range, that is, the correct parameters that the defective data should repair, so as to determine the defect location of each defective data and the path where the defect occurs, that is, the branch link.

[0100] The debugging branch link is a link of multiple stages where the defective data is located in the software development program. Exemplarily, the debugging branch link can be the software requirements stage-architecture stage-R&D stage-testing stage-deployment and launch stage-operation and maintenance stage-operation stage-closed loop stage. The stage link is a plurality of process stages involved in the software development program of the target application, for example, the R&D stage-testing stage-deployment and launch stage. The defect cause is the cause that leads to the generation of defective data. Exemplarily, the defect cause of the data (defective data) that the monitoring software fails to monitor may be power outage, poor network, etc. Correct parameters refer to correct data that can repair defective data, such as the number of iterations being less than 1000.

[0101] Specifically, corresponding test cases can be set for different defect data for each application in the target system in advance, so as to obtain the debugging module of each application, and the debugging module of the target application can be used to perform breakpoint debugging on the defect information to generate debugging branch links, defect causes and correct parameters. In this embodiment, the defect information is debugged by the debugging module to sort out the defect causes of the target system and realize the automatic processing of defect data. At the same time, the generation of debugging branch links, defect causes and correct parameters through breakpoint debugging realizes the multi-dimensional analysis of defect data and improves the comprehensive integrity of defect analysis information.

[0102] 304. Based on a preset defect management rule base, manage the debugging branch link, the defect cause and the correct parameter.

[0103] Among them, the management of defects includes but is not limited to defect display, defect summary, defect warning, defect repair, etc., which can be managed specifically according to actual applications.

[0104] The preset defect management rule base is a pre-set database containing at least one defect management rule. For example, it can be a management rule for analyzing and summarizing the debugging branch links, defect causes and correct parameters, and drawing a trajectory map. It can also be a rule for generating a list of defect details. It can also be a management rule for defect warning, defect repair, etc. based on the debugging branch links, defect causes and correct parameters. It can be configured according to the actual application scenario to support secondary development of defect management.

[0105] Specifically, according to the preset defect management rule base, the debugging branch links, defect causes and correct parameters are analyzed and processed from multiple dimensions, which improves the efficient and comprehensive processing of defect data. Then, the analysis and processing results are managed, realizing comprehensive and efficient management of system defects. The management method is configurable and improves the flexibility of system defect management.

[0106] In this embodiment, the debugging module of the target application is used to perform breakpoint debugging on the defect information, generate debugging branch links, defect causes and correct parameters, realize multi-dimensional analysis of defect data, improve the comprehensive integrity of defect analysis information, and manage according to the debugging branch links, defect causes and correct parameters, realize automated management of system defects, and improve the diversity and flexibility of defect management.

[0107] In a specific implementation, the preset defect management rule base includes at least one of a defect track rule, a defect attribute field rule, a problem responsibility attribution rule, and a defect repair rule, and each rule corresponds to at least one rule indicator; the management of the debugging branch link, the defect cause, and the correct parameter based on the preset defect management rule base in step 302 may include the following steps 304A-304B, which are specifically as follows:

[0108] 304A, based on the defect management rule base, extract rule indicators for the debugging branch link, the defect cause and the correct parameter to obtain defect indicator data;

[0109] 304B. Generate a defect management report based on the defect indicator data.

[0110] Among them, the defect trajectory rule is used to display the trajectory of the defect trajectory, and its corresponding rule indicators can be the flow of defect data and the status of defect information, such as close status or open status. The defect attribute field rule refers to the rules related to defect attributes, and its corresponding rule indicators can be defect attributes, such as problem phenomenon, (testing / R&D) problem cause, (testing / R&D) improvement measures, problem source, belonging system, belonging functional module, responsibility attribution, problem level, scope of impact, whether there is use case coverage, etc. The problem responsibility attribution rule refers to the stage where the defect is located, the user who is responsible for the defect, etc., and its corresponding rule indicators can be the defect stage, the person responsible for the defect, etc. The defect repair rule is applicable to the rules for repairing defect data, and its corresponding rule indicators can be the correct parameters.

[0111] Defect index data refers to data used to reflect fine-grained defect information obtained by multi-dimensionally analyzing the debugging branch link, the defect cause and the correct parameters according to the defect management rule base. Defect management report is a report used to display the defect management results, which can be in the form of pictures, tables or text.

[0112] Specifically, according to the defect management rule base, rule indicators are extracted for the debugging branch links, defect causes and correct parameters to obtain defect indicator data, thereby achieving a more fine-grained analysis of the debugging branch links, defect causes and correct parameters on the defect management rule base. Then, the defect indicator data is presented according to certain presentation rules to generate a defect management report.

[0113] In a specific implementation, the defect management rule base is the defect track rule; the rule indicators of the defect track rule include a state indicator and a flow indicator; the defect management report includes at least one of a defect track map, a defect distribution map, a defect detail list, a defect warning list, a defect responsibility attribution list, a defect viewing authority list, and a defect repair result list;

[0114] In step 304A, based on the defect management rule base, extracting rule indicators from the debugging branch link, the defect cause and the correct parameter to obtain defect indicator data may include the following steps 304A1 to 304A2, specifically:

[0115] 304A1. Extracting, from the debugging branch link, a process sequence in which the defect information is located in the software development process according to the flow indicator;

[0116] 304A2. Extracting the state identifier of the defect information from the debugging branch link according to the state indicator;

[0117] Generating a defect management report based on the defect indicator data in step 304B may include the following step 304B1, specifically:

[0118] 304B1. Fill the state identifier and the process sequence into a preset defect trajectory map template to generate a defect trajectory map.

[0119] The process sequence refers to the flow of defect information in each stage of the target application, for example, the testing stage - the deployment and launch stage - the maintenance stage - the operation stage - the closed-loop stage.

[0120] Specifically, according to the flow indicators, the process sequence of the defect data in the software development process is extracted from the debugging branch link, and according to the status indicators, the state identifier of the defect data is extracted from the debugging branch link. Then, the trajectory of each stage is drawn according to the process sequence, and the state identifier is marked at each stage position in the trajectory to generate a defect trajectory map, which realizes the display of the data status of the defect data at each stage, and facilitates the positioning analysis of the defect stage of the target application in the target system.

[0121] In a specific implementation manner, the defect management rule base is the defect attribute field rule; the rule indicator of the defect attribute field rule includes a problem attribute field indicator; step 304A extracts the rule indicator of the debugging branch link, the defect cause and the correct parameter based on the defect management rule base to obtain the defect indicator data, which may include the following step 304A3, specifically:

[0122] 304A3. Extract multiple problem data of the defect information from the debugging branch link according to the problem attribute field indicator, extract the problem cause of the defect information from the defect cause, and extract the improvement measures of the defect information from the correct parameters;

[0123] Generating a defect management report based on the defect indicator data in step 304B may include the following step 304B2, specifically:

[0124] 304B2. Generate the defect detail list based on the multiple problem data, the problem causes and the problem measures; and / or generate the defect distribution map based on the multiple problem data, the problem causes and the problem measures; and / or generate the defect warning list based on the multiple problem data, the problem causes and the problem measures.

[0125] Specifically, multiple problem data of defect information are extracted from the debugging branch link, the problem cause of the defect information is extracted from the defect cause, and improvement measures of the defect information are extracted from the correct parameters. Then, the multiple problem data, problem causes and problem measures are analyzed and summarized to generate a defect detail list, and / or the problem cause is analyzed to determine the problem severity level, and the problem data, problem causes and problem measures with higher severity levels are filled into a preset defect warning list template to generate a defect warning list, and / or, based on multiple problem data, the amount of defect data under different business modules is counted, and the defect information of different business modules is presented in the form of a distribution map to generate a defect distribution map, thereby realizing the display of further detailed information of the defect data, and facilitating the accurate analysis of the defect details of the target application in the target system.

[0126] In an example, for the defect distribution map, the amount of defect data in different business modules can be counted, and the size of the defect data can be used to detect potential risk items. For example, based on the method name or class name of the software implementation, it can be counted which methods in which specific functional modules are the hardest hit areas and which are the safe areas, etc., to provide data basis for subsequent system tuning, testing strategies, and risk assessments.

[0127] In a specific implementation manner, the defect management rule base is the problem responsibility attribution rule; the rule indicators of the problem responsibility attribution rule include defect link indicators and responsibility role indicators; step 304A extracts rule indicators from the debugging branch link, the defect cause and the correct parameter based on the defect management rule base to obtain defect indicator data, which may include the following steps 304A4 to 304A5, specifically:

[0128] 304A4. Extracting a defect link identifier of the defect information from the debugging branch link and the defect cause according to the defect link indicator;

[0129] 304A5. Extracting the responsible role identifier of the defect information from the debugging branch link and the defect cause according to the responsible role indicator;

[0130] Generating a defect management report based on the defect indicator data in step 304B may include the following step 304B3, specifically:

[0131] 304B3. Generate the defect responsibility attribution list according to the defect link identifier and the responsible role identifier; and / or generate the defect viewing permission list according to the defect link identifier and the responsible role identifier.

[0132] Among them, defective links may be R&D, chassis, third-party, test-free, non-problem, architecture design, process operation, network security, environmental data, whether use cases are covered, etc.

[0133] Specifically, the defect link identifier and responsible role identifier of the defect data are extracted from the debugging branch link and the defect cause, and then, multiple problem data, problem causes and problem measures are analyzed and summarized to generate a defect detail list, and / or, the defect information, defect link identifier and responsible role identifier are associated to generate a defect responsibility attribution list, and / or, different functional permissions and menu permissions are configured according to the responsible role identifier to generate a defect viewing permission list, thereby realizing the analysis of the responsibility attribution of the defect data, facilitating the positioning of the defect link and defect processing object of the target application in the target system, and thereby improving the efficiency of subsequent defect processing objects in handling defects.

[0134] In a specific implementation manner, the defect management rule base is the defect repair rule; the rule indicator of the defect repair rule includes a repair data indicator; and step 304A extracts the rule indicator of the debugging branch link, the defect cause and the correct parameter based on the defect management rule base to obtain the defect indicator data, which may include the following step 304A6, specifically:

[0135] 304A6. Extracting repair data of the defect information from the error cause and the correct parameter according to the repair data indicator;

[0136] Generating a defect management report based on the defect index data in step 304B may include the following steps 304B4 to 304B5, specifically:

[0137] 304B4. Perform regression testing according to the repair data to generate the test result;

[0138] 304B5. Fill the defect information and test results into a preset defect repair result table to obtain the defect repair result list.

[0139] Specifically, the repair data of the defect information is extracted from the error cause and the correct parameters, and then the repair data is used to perform regression testing to generate test results. The defect information and test results are filled into a preset defect repair result table to obtain a defect repair result list, thereby achieving the repair of the defect data of the target application in the target system and forming a defect repair result list, which can serve as an experience library for subsequent defect data processing and provide valuable reference for subsequent defect data processing.

[0140] In a specific implementation, after the defect management report is generated based on the defect indicator data in step 304, the following step 305 may also be included, specifically as follows:

[0141] 305. Perform system tuning on the target system based on the defect management report; and / or perform iterative updating on the target system based on the defect management report.

[0142] Specifically, system tuning of the target system can be achieved based on the defect management report, and / or iterative updating of the target system can be achieved based on the defect management report, thereby further improving the quality of the target system.

[0143] In order to better implement the defect management method of the system in the embodiment of the present application, based on the defect management method of the system, the embodiment of the present application also provides a defect management device of the system, such as Figure 3 As shown, the defect management device 400 of the system includes:

[0144] An acquisition module 401 is used to acquire defect data of a target system, wherein the defect data includes interface information and defect data in the target system;

[0145] A determination module 402, configured to determine the target application to which the defect data belongs based on the interface information;

[0146] A generation module 403 is used to perform breakpoint debugging on the defect data by using the debugging module of the target application, and generate a debugging branch link, a defect cause and a correct parameter, wherein the debugging branch link includes multiple stage links where the defect data is located in the software development program;

[0147] The management module 404 is used to manage the debugging branch link, the defect cause and the correct parameter based on a preset defect management rule base.

[0148] In the embodiment of the present application, the preset defect management rule base includes at least one of defect trajectory rules, defect attribute field rules, problem responsibility attribution rules and defect repair rules, and each rule corresponds to at least one rule indicator; the management module 404 is specifically used to:

[0149] Based on the defect management rule base, extracting rule indicators from the debugging branch link, the defect cause and the correct parameter to obtain defect indicator data;

[0150] A defect management report is generated based on the defect indicator data.

[0151] In the embodiment of the present application, the defect management rule base is the defect trajectory rule; the rule indicators of the defect trajectory rule include status indicators and flow indicators; the defect management report includes at least one of a defect trajectory map, a defect distribution map, a defect detail list, a defect warning list, a defect responsibility attribution list, a defect viewing authority list, and a defect repair result list;

[0152] The management module 404 is also used for:

[0153] According to the flow indicator, extracting the process sequence of the defect information in the software development process from the debugging branch link;

[0154] Extracting a status identifier of the defect information from the debugging branch link according to the status indicator;

[0155] The state identifier and the process sequence are filled into a preset defect trajectory map template to generate a defect trajectory map.

[0156] In the embodiment of the present application, the defect management rule base is the defect attribute field rule; the rule indicator of the defect attribute field rule includes the problem attribute field indicator; the management module 404 is further specifically used for:

[0157] According to the problem attribute field indicator, extract multiple problem data of the defect information from the debugging branch link, extract the problem cause of the defect information from the defect cause, and extract the improvement measures of the defect information from the correct parameters;

[0158] Generate the defect detail list based on the multiple problem data, the problem causes and the problem measures; and / or generate the defect distribution map based on the multiple problem data, the problem causes and the problem measures; and / or generate the defect warning list based on the multiple problem data, the problem causes and the problem measures.

[0159] In the embodiment of the present application, the defect management rule base is the problem responsibility attribution rule; the rule indicators of the problem responsibility attribution rule include defect link indicators and responsibility role indicators; the management module 404 is also used to:

[0160] Extracting a defect link identifier of the defect information from the debugging branch link and the defect cause according to the defect link indicator;

[0161] Extracting a responsible role identifier of the defect information from the debugging branch link and the defect cause according to the responsible role indicator;

[0162] The defect responsibility attribution list is generated according to the defect link identifier and the responsible role identifier; and / or, the defect viewing permission list is generated according to the defect link identifier and the responsible role identifier.

[0163] In the embodiment of the present application, the defect management rule base is the defect repair rule; the rule indicator of the defect repair rule includes a repair data indicator; the management module 404 is further specifically used for:

[0164] Extracting repair data of the defect information from the error cause and the correct parameter according to the repair data indicator;

[0165] Perform regression testing according to the repair data to generate the test result;

[0166] The defect information and test results are filled into a preset defect repair result table to obtain the defect repair result list.

[0167] In the embodiment of the present application, the defect management device 400 of the system further includes:

[0168] A tuning module is used to perform system tuning on the target system based on the defect management report; and / or an iteration module is used to iteratively update the target system based on the defect management report.

[0169] The embodiment of the present application further provides a computer device, which integrates a defect management device of any system provided in the embodiment of the present application, and the computer device includes:

[0170] one or more processors;

[0171] Memory; and

[0172] One or more applications, wherein the one or more applications are stored in the memory and are configured to be executed by the processor to execute the steps of the system defect management method described in any of the embodiments of the system defect management method.

[0173] The present application also provides a computer device that integrates a defect management device of any system provided in the present application. Figure 4 As shown, it shows a schematic diagram of the structure of the computer device involved in the embodiment of the present application, specifically:

[0174] The computer device may include one or more processing core processors 701, one or more computer readable storage media memories 702, a power supply 703, an input unit 704 and other components. Those skilled in the art will appreciate that Figure 4 The computer device structure shown in the figure does not constitute a limitation on the computer device, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently. Among them:

[0175] The processor 701 is the control center of the computer device. It uses various interfaces and lines to connect various parts of the entire computer device. By running or executing software programs and / or modules stored in the memory 702 and calling data stored in the memory 702, it executes various functions of the computer device and processes data, thereby monitoring the computer device as a whole. Optionally, the processor 701 may include one or more processing cores; preferably, the processor 701 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application programs, and the modem processor mainly processes wireless communications. It is understandable that the above-mentioned modem processor may not be integrated into the processor 701.

[0176] The memory 702 can be used to store software programs and modules. The processor 701 executes various functional applications and data processing by running the software programs and modules stored in the memory 702. The memory 702 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc.; the data storage area may store data created according to the use of the computer device, etc. In addition, the memory 702 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage devices. Accordingly, the memory 702 may also include a memory controller to provide the processor 701 with access to the memory 702.

[0177] The computer device also includes a power supply 703 for supplying power to various components. Preferably, the power supply 703 can be logically connected to the processor 701 through a power management system, so as to manage charging, discharging, and power consumption through the power management system. The power supply 703 can also include any combination of one or more DC or AC power supplies, recharging systems, power failure detection circuits, power converters or inverters, power status indicators, etc.

[0178] The computer device may further include an input unit 704, which may be used to receive input digital or character information and generate keyboard, mouse, joystick, optical or trackball signal input related to user settings and function control.

[0179] Although not shown, the computer device may further include a display unit, etc., which will not be described in detail herein. Specifically in this embodiment, the processor 701 in the computer device will load the executable files corresponding to the processes of one or more application programs into the memory 702 according to the following instructions, and the processor 701 will run the application programs stored in the memory 702, thereby realizing various functions, as follows:

[0180] Acquire defect data of a target system, wherein the defect data includes interface information and defect data in the target system;

[0181] Determine the target application to which the defect data belongs based on the interface information;

[0182] Perform breakpoint debugging on the defective data using the debugging module of the target application to generate a debugging branch link, a defect cause and a correct parameter, wherein the debugging branch link includes multiple stage links where the defective data is located in the software development program;

[0183] Based on a preset defect management rule base, the debugging branch link, the defect cause and the correct parameter are managed.

[0184] A person of ordinary skill in the art will appreciate that all or part of the steps in the various methods of the above embodiments may be completed by instructions, or by controlling related hardware through instructions. The instructions may be stored in a computer-readable storage medium and loaded and executed by a processor.

[0185] To this end, an embodiment of the present application provides a computer-readable storage medium, which may include: a read-only memory (ROM), a random access memory (RAM), a disk or an optical disk, etc. A computer program is stored thereon, and the computer program is loaded by a processor to execute the steps in any of the defect management methods of the system provided in the embodiment of the present application. For example, the computer program may be loaded by a processor to execute the following steps:

[0186] Acquire defect data of a target system, wherein the defect data includes interface information and defect information in the target system;

[0187] Determine the target application to which the defect data belongs based on the interface information;

[0188] Perform breakpoint debugging on the defective data using the debugging module of the target application to generate a debugging branch link, a defect cause and a correct parameter, wherein the debugging branch link includes multiple stage links where the defective data is located in the software development program;

[0189] Based on a preset defect management rule base, the debugging branch link, the defect cause and the correct parameter are managed.

[0190] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the detailed description of other embodiments above, and will not be repeated here.

[0191] In specific implementation, the above units or structures can be implemented as independent entities, or can be arbitrarily combined to be implemented as the same or several entities. The specific implementation of the above units or structures can refer to the previous method embodiments, which will not be repeated here.

[0192] The specific implementation of the above operations can be found in the previous embodiments, which will not be described in detail here.

[0193] The above is a detailed introduction to a system defect management method, device and storage medium provided in an embodiment of the present application. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea; at the same time, for technical personnel in this field, according to the idea of ​​the present application, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims

1. A systematic defect management method, characterized in that: The defect management method of the system includes: Acquire defect data of a target system, wherein the defect data includes interface information and defect information of the target system, wherein the interface information includes a method name and / or a class name of the defect data, and the defect information is information related to the defect in the target system; Determine the target application to which the defect data belongs based on the interface information; Perform breakpoint debugging on the defect information using the debugging module of the target application to generate a debugging branch link, a defect cause, and a correct parameter, wherein the debugging branch link includes multiple stage links where the defect data is located in the software development program; Based on a preset defect management rule base, the debugging branch link, the defect cause and the correct parameter are managed.

2. The defect management method of the system according to claim 1, characterized in that: The preset defect management rule base includes at least one of defect track rules, defect attribute field rules, problem responsibility attribution rules and defect repair rules, and each rule corresponds to at least one rule indicator; The managing the debugging branch link, the defect cause and the correct parameter based on the preset defect management rule includes: Based on the defect management rule base, extracting rule indicators from the debugging branch link, the defect cause and the correct parameter to obtain defect indicator data; A defect management report is generated based on the defect indicator data.

3. The defect management method of the system according to claim 2, characterized in that: The defect management rule base is the defect track rule; the rule indicators of the defect track rule include status indicators and flow indicators; the defect management report includes at least one of a defect track map, a defect distribution map, a defect detail list, a defect warning list, a defect responsibility attribution list, a defect viewing authority list, and a defect repair result list; The step of extracting rule indicators from the debugging branch link, the defect cause and the correct parameter based on the defect management rule base to obtain defect indicator data includes: According to the flow indicator, extracting the process sequence of the defect information in the software development process from the debugging branch link; According to the status indicator, extracting the status identifier of the defect information from the debugging branch link; The generating of the defect management report based on the defect indicator data comprises: The state identifier and the process sequence are filled into a preset defect trajectory map template to generate a defect trajectory map.

4. The defect management method of the system according to claim 2, characterized in that: The defect management rule base is the defect attribute field rule; the rule indicator of the defect attribute field rule includes the problem attribute field indicator; The step of extracting rule indicators from the debugging branch link, the defect cause and the correct parameter based on the defect management rule base to obtain defect indicator data includes: According to the problem attribute field indicator, extract multiple problem data of the defect information from the debugging branch link, extract the problem cause of the defect information from the defect cause, and extract the improvement measures of the defect information from the correct parameters; The generating of the defect management report based on the defect indicator data comprises: Generate the defect detail list based on the multiple problem data, the problem causes and the problem measures; and / or generate the defect distribution map based on the multiple problem data, the problem causes and the problem measures; and / or generate the defect warning list based on the multiple problem data, the problem causes and the problem measures.

5. The defect management method of the system according to claim 2, characterized in that: The defect management rule base is the problem responsibility attribution rule; the rule indicators of the problem responsibility attribution rule include defect link indicators and responsibility role indicators; The step of extracting rule indicators from the debugging branch link, the defect cause and the correct parameter based on the defect management rule base to obtain defect indicator data includes: Extracting a defect link identifier of the defect information from the debugging branch link and the defect cause according to the defect link indicator; Extracting a responsible role identifier of the defect information from the debugging branch link and the defect cause according to the responsible role indicator; The generating of the defect management report based on the defect indicator data comprises: The defect responsibility attribution list is generated according to the defect link identifier and the responsible role identifier; and / or, the defect viewing permission list is generated according to the defect link identifier and the responsible role identifier.

6. The defect management method of the system according to claim 2, characterized in that: The defect management rule base is the defect repair rule; the rule indicator of the defect repair rule includes a repair data indicator; The step of extracting rule indicators from the debugging branch link, the defect cause and the correct parameter based on the defect management rule base to obtain defect indicator data includes: Extracting repair data of the defect information from the error cause and the correct parameter according to the repair data indicator; The generating of the defect management report based on the defect indicator data comprises: Perform regression testing according to the repair data to generate the test result; The defect information and test results are filled into a preset defect repair result table to obtain the defect repair result list.

7. The defect management method of a system according to any one of claims 1 to 6, characterized in that: After generating the defect management report based on the defect indicator data, the method further includes: Performing system tuning on the target system based on the defect management report; and / or, iteratively updating the target system based on the defect management report.

8. A defect management device for a system, characterized in that: The defect management device of the system comprises: An acquisition module, used to acquire defect data of a target system, wherein the defect data includes interface information and defect information of the target system, wherein the interface information includes a method name and / or a class name of the defect data, and the defect information is information related to defects in the target system; A determination module, configured to determine a target application to which the defect data belongs based on the interface information; A generation module, used to perform breakpoint debugging on the defect information by using the debugging module of the target application, and generate a debugging branch link, a defect cause and a correct parameter, wherein the debugging branch link includes multiple stage links where the defect data is located in the software development program; The management module is used to manage the debugging branch link, the defect cause and the correct parameter based on a preset defect management rule base.

9. A computer device, characterized in that: The computer device comprises: one or more processors; Memory; and One or more application programs, wherein the one or more application programs are stored in the memory and configured to be executed by the processor to implement the defect management method of the system according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: A computer program is stored thereon, and the computer program is loaded by a processor to execute the steps in the defect management method of the system according to any one of claims 1 to 7.

Images