CN107193677B - Method and system for notifying code defects - Google Patents
Method and system for notifying code defects Download PDFInfo
- Publication number
- CN107193677B CN107193677B CN201710253750.3A CN201710253750A CN107193677B CN 107193677 B CN107193677 B CN 107193677B CN 201710253750 A CN201710253750 A CN 201710253750A CN 107193677 B CN107193677 B CN 107193677B
- Authority
- CN
- China
- Prior art keywords
- target
- defect
- code
- repaired
- sub
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 230000007547 defect Effects 0.000 title claims abstract description 253
- 238000000034 method Methods 0.000 title claims abstract description 32
- 230000008439 repair process Effects 0.000 claims abstract description 83
- 230000005540 biological transmission Effects 0.000 claims description 10
- 238000010586 diagram Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0793—Remedial or corrective actions
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention provides a method and a system for notifying code defects, wherein the method comprises the following steps: acquiring defect subcodes in all branch codes in a code library, distributing corresponding ID and repair completion time to each defect subcode, and recording the ID and the repair completion time into a defect list; when the current time reaches any repair completion time, acquiring a target defect subcode and a target ID corresponding to the repair completion time, and judging whether the target defect subcode is repaired in all target branch codes related to the target defect subcode; and if not, taking the target ID and the code numbers of all the target branch codes of the target defect subcodes which are not repaired as information to be notified. According to the method and the system for notifying the code defects, whether the code defects are completely repaired or not can be automatically monitored when the specified repairing time is up, and notification information is sent when the code defects are not completely repaired.
Description
Technical Field
The invention relates to the technical field of code library management, in particular to a method and a system for notifying code defects.
Background
The code library provides a way to encapsulate code in a single file, allowing inheritance and modification of these files. The developer can combine the code files from a plurality of different projects into a code base, and the code of each project is used as a branch code in the code base and is called mutually to realize code sharing. For example, a product has different target markets and different customer requirements, so that the software codes are different, developers can combine different software codes of the product into a code base, and each software code is taken as a branch of the code base for management.
The occurrence of code defects in software, especially large software, is inevitable, and therefore, in the field of code library management technology, the management, monitoring and repair of code defects are also one of the important tasks of developers.
In the prior art, when a code defect is found, a software supervisor usually assigns a task of repairing the code defect to an engineer, and there may be many code defects in a code library, and the software supervisor cannot timely manage all the code defects, thereby resulting in a code defect that is missed to be processed.
Disclosure of Invention
Based on this, the invention aims to provide a method and a system for notifying code defects, so that when the specified repair time is reached, whether the code defects are completely repaired can be automatically monitored, and when the code defects are not completely repaired, notification information is sent.
The method for notifying the code defect according to the embodiment of the invention comprises the following steps:
acquiring defect subcodes in all branch codes in a code library, distributing corresponding ID and repair completion time to each defect subcode, and recording the ID and the repair completion time into a defect list;
when the current time reaches any repair completion time recorded in the defect list, acquiring a target defect subcode and a target ID corresponding to the any repair completion time, and judging whether the target defect subcode is repaired in all target branch codes related to the target defect subcode;
and if not, taking the target ID and the code numbers of all the target branch codes of the target defect subcodes which are not repaired as information to be notified.
In addition, the method for notifying a code defect according to the above embodiment of the present invention may further have the following additional technical features:
after the step of assigning a corresponding ID and repair completion time to each of the defect sub-codes, the method of notifying a code defect further includes:
and allocating a corresponding notification information transmission address to each defect sub-code, and recording the notification information transmission address into the defect list.
The step of notifying the target ID and the code numbers of all the target branch codes that the target defect sub-code is not repaired as information includes:
extracting a target notification information sending address corresponding to the target ID from the defect list;
and sending the target ID and the code numbers of all the target branch codes which do not repair the target defect subcodes to the target notification information sending address as information.
The step of determining whether the target defect subcode is repaired among all target branch codes associated with the target defect subcode comprises:
determining whether the target ID exists in all of the target branch codes associated with the target defect subcode.
After the step of determining whether the target defect subcode is repaired in all target branch codes related to the target defect subcode, the method of notifying a code defect further includes:
and if so, clearing all the contents related to the target ID and recorded in the defect list.
After the step of notifying the target ID and the code numbers of all the target branch codes that have not repaired the target defect sub-code as information, the method of notifying a code defect further includes:
and opening a code repair mode of the code base so that a user needing the appointed authority can edit the codes in the code base.
The system for notifying the code defect according to the embodiment of the invention comprises:
the code information recording module is used for acquiring defect subcodes in all branch codes in a code library, distributing corresponding ID and repair completion time to each defect subcode and recording the ID and the repair completion time into a defect list;
a judging module, configured to, when current time reaches any repair completion time recorded in the defect list, obtain a target defect subcode and a target ID corresponding to the any repair completion time, and judge whether the target defect subcode is repaired in all target branch codes related to the target defect subcode;
and the notification information sending module is used for notifying the target ID and the code numbers of all the target branch codes of the target defect subcodes which are not repaired as information when the target defect subcodes are judged not to be repaired in all the target branch codes.
In addition, a system for notifying a code defect according to the above embodiment of the present invention may have additional technical features,
the system for notifying the code defect further comprises:
and the address distribution recording module is used for distributing a corresponding notification information sending address to each defect subcode and recording the notification information sending address into the defect list.
The notification information sending module comprises:
an address acquisition unit configured to extract a target notification information transmission address corresponding to the target ID from the defect list;
and the notification information sending subunit is used for sending the target ID and the code numbers of all the target branch codes which do not repair the target defect subcodes to the target notification information sending address as information.
The judging module comprises:
a judging subunit operable to judge whether the target ID exists in all the target branch codes related to the target defect sub-code.
The system for notifying the code defect further comprises:
and the clearing module is used for clearing all the contents related to the target ID recorded in the defect list when the target defect subcode is judged to be repaired in all the target branch codes.
The system for notifying the code defect further comprises:
and the repair module starting module is used for starting the code repair mode of the code base after the notification information sending module sends the notification information so that a user needing to specify the authority can edit the codes in the code base.
The method and the system for notifying the code defect acquire all defect subcodes in the code library, allocate corresponding IDs and repair completion time (the IDs and the repair completion time of the same defect subcodes are the same) to each defect subcode, record all the IDs and the corresponding repair completion time into the defect list, automatically and timely control all the defect subcodes in the code library through the defect list, acquire a target defect subcode and a target ID corresponding to the repair completion time when the current time reaches a certain repair completion time recorded in the defect list, judge whether the target defect subcode is repaired in all target branch codes related to the target defect subcode, and notify the target ID and the target branch code which does not repair the target defect subcode as information when judging that the target defect subcode is not repaired, according to the notification information, the relevant responsible person can know that the defect subcodes are not completely repaired within the specified time limit, and can know the ID of the defect subcodes which are not completely repaired and the corresponding unrepaired branch codes, so that the code defect notification method can automatically monitor whether the code defects are completely repaired when the specified repair time is reached, and send the notification information when the corresponding code defects are not completely repaired, so that the relevant responsible person can timely process the defects, and products with the detected code defects continue to flow to the market.
Drawings
Fig. 1 is a flowchart of a method for notifying a code defect according to a first embodiment of the present invention.
Fig. 2 is a flowchart of a method for notifying a code defect according to a second embodiment of the present invention.
Fig. 3 is a schematic structural diagram of a notification system of code defects in a third embodiment of the present invention.
Description of the main elements
The following detailed description will further illustrate the invention in conjunction with the above-described figures.
Detailed Description
To facilitate an understanding of the invention, the invention will now be described more fully with reference to the accompanying drawings. Several embodiments of the invention are presented in the drawings. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete.
It will be understood that when an element is referred to as being "secured to" another element, it can be directly on the other element or intervening elements may also be present. When an element is referred to as being "connected" to another element, it can be directly connected to the other element or intervening elements may also be present. The terms "vertical," "horizontal," "left," "right," and the like as used herein are for illustrative purposes only.
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. The terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the term "and/or" includes any and all combinations of one or more of the associated listed items.
Referring to fig. 1, a flowchart of a method for notifying a code defect according to a first embodiment of the present invention is shown, which includes steps S01 to S03.
Step S01, acquiring the defect subcodes in all the branch codes in the code library, assigning a corresponding ID and repair completion time to each type of defect subcode, and recording the ID and repair completion time in a defect list.
It is understood that a code library usually includes a plurality of branch codes, each branch code has a plurality of sub-codes, and many sub-codes inevitably have defects (e.g. sub-code errors), and the sub-code sending the defect is the defect sub-code.
In the step S01, all defect sub-codes within the code library are acquired, and there may be a phenomenon that the acquired defect sub-codes are repeated, and the step S01 assigns an ID and a repair completion time to the same defect sub-code.
It should be noted that each defect sub-code has only one unique ID, and the ID is the unique ID of the corresponding defect sub-code, and the corresponding defect sub-code can be queried through the ID. In contrast, the purpose of assigning a corresponding ID to each defect sub-code is that a general sub-code may be complex, and an ID (simpler) user may preset, and the corresponding defect sub-code is mapped by assigning an ID, so that subsequent management is facilitated, and the defect sub-code is conveniently sent as notification information.
In a specific implementation, before the step S01, a defect sub-code in all branch codes in the code library may be found by a human (engineer) or a related program.
In specific implementation, the step of assigning a corresponding ID and repair completion time to each defect sub-code may be implemented according to the following steps: firstly, generating a corresponding ID for the current defect subcode according to a preset ID generation mode (such as a generation mode with the number from large to small), then acquiring the current time, and adding a preset time period on the basis of the current time to be used as the repair completion time of the current defect subcode.
Step S02, when the current time reaches any repair completion time recorded in the defect list, acquiring a target defect sub-code and a target ID corresponding to the any repair completion time, and determining whether the target defect sub-code is repaired in all target branch codes related to the target defect sub-code.
The target branch code refers to a branch code in which the target defect sub-code exists, and since the target branch code may exist in a plurality of branch codes, the target branch code may be a plurality of branch codes.
It can be understood that, in the step S01, the defect sub-code, the ID and the repair completion time are associated and corresponding, and are stored in the defect list, and when the current time reaches any repair completion time recorded in the defect list, the corresponding defect sub-code and ID, that is, the target defect sub-code and the target ID, can be obtained according to the any repair completion time.
In specific implementation, the ID is used as a repair identifier of a corresponding defect sub-code, that is, when a relevant worker repairs a certain defect sub-code on a certain branch code, the ID corresponding to the currently repaired defect sub-code may be recorded on the current branch code after the repair is completed, that is, when a defect sub-code is repaired, the corresponding ID is remarked on the corresponding branch code. Therefore, the step of determining whether the target defect sub-code is repaired in all target branch codes related to the target defect sub-code may be implemented as follows: judging whether the target ID exists in all the target branch codes related to the target defect subcode or not, if yes, representing that the target defect subcode is repaired in all the target branch codes, otherwise, representing that the target defect subcode is not completely repaired in all the target branch codes.
When the step S02 determines that the target defect subcode is not repaired in all target branch codes related to the target defect subcode, which means that the target defect subcode is not repaired (not repaired or not repaired in its entirety) in the designated repair completion time, the step S03 is executed, and when the step S02 determines that the target defect subcode is repaired in all target branch codes related to the target defect subcode, which means that the target defect subcode is repaired in all target branch codes in the designated repair completion time, which does not need to be operated.
Step S03, notifying the target ID and the code numbers of all the target branch codes of the target defect sub-code that are not repaired as information.
Wherein, the code number of the target branch code may be the name, number, etc. of the target branch code in the code base.
In specific implementation, the target ID and the target branch code of the target defect-unrepaired subcode may be sent to a mailbox, a mobile phone, or a computer of the relevant person as information, and the mailbox and the mobile phone number of the relevant person may be stored in advance, or a connection may be established with the computer of the relevant person in advance.
In summary, in the above method for notifying a code defect, all defect sub-codes in the code library are acquired, corresponding IDs and repair completion times (the IDs and repair completion times of the same defect sub-codes are the same) are assigned to each defect sub-code, then all the IDs and the corresponding repair completion times are recorded in the defect list, all the defect sub-codes in the code library can be automatically and timely controlled through the defect list, then when the current time reaches a certain repair completion time recorded in the defect list, a target defect sub-code and a target ID corresponding to the repair completion time are acquired, whether the target defect sub-code is repaired among all target branch codes related to the target defect sub-code is determined, and when it is determined that none of the target defect sub-codes is repaired, the target ID and a target branch code not repaired by the target defect sub-code are notified as information, according to the notification information, the relevant responsible person can know that the defect subcodes are not completely repaired within the specified time limit, and can know the ID of the defect subcodes which are not completely repaired and the corresponding unrepaired branch codes, so that the code defect notification method can automatically monitor whether the code defects are completely repaired when the specified repair time is reached, and send the notification information when the corresponding code defects are not completely repaired, so that the relevant responsible person can timely process the defects, and products with the detected code defects continue to flow to the market.
Referring to FIG. 2, a flowchart of a method for notifying a code defect in a second embodiment of the present invention is shown, which includes steps S11 to S17.
Step S11 is to acquire defect sub-codes in all branch codes in the code library, assign corresponding ID, repair completion time, and notification information transmission address to each of the defect sub-codes, and record the ID, repair completion time, and notification information transmission address in a defect list.
The notification information sending address can be at least one of a mailbox, a mobile phone or a computer of related personnel.
Step S12, when the current time reaches any repair completion time recorded in the defect list, acquiring a target defect subcode and a target ID corresponding to the any repair completion time, and backing up and storing the target ID.
Because each ID corresponds to a defect subcode, the target ID is backed up and stored for facilitating subsequent record query.
Step S13, determining whether the target ID exists in all the target branch codes associated with the target defect subcode.
In specific implementation, when a relevant worker repairs a certain defect sub-code on a certain branch code, after the repair is completed, an ID corresponding to the currently repaired defect sub-code may be recorded on the current branch code, that is, when a defect sub-code is repaired, the corresponding ID is remarked at a corresponding position. It may therefore be determined whether the target defect subcode in the target branch code is repaired by determining whether the target ID is present in the target branch code.
When the step S13 determines that the target ID exists in all target branch codes related to the target defect sub-code, representing that the target defect sub-code is repaired in all the target branch codes within the designated repair completion time, the step S14 is performed, and when the step S13 determines that the target ID does not exist in all the target branch codes related to the target defect sub-code, representing that the target defect sub-code is not completely repaired in all the target branch codes within the designated repair completion time, the steps S15 to S17 are performed.
Step S14, clearing all the contents related to the target ID recorded in the defect list.
Since the step S13 has determined that the target defect sub-code is repaired in all the target branch codes, and the target defect sub-code does not exist in the code library, the defect list is sorted by clearing all the contents related to the target ID recorded in the defect list, and the target ID is stored in the step S12, the relevant person can still inquire the target ID by the saved ID after the data is cleared in the step S14.
Step S15 is to extract a target notification information transmission address corresponding to the target ID from the defect list.
Step S16, sending the target ID and the code numbers of all the target branch codes that have not repaired the target defect sub-code to the target notification information sending address as information.
And step S17, opening a code repair mode of the code base so that a user needing to specify the authority can edit the codes in the code base.
It should be noted that, after the code repair mode of the code library is started, except for the relevant technical personnel, the codes of the code library cannot be edited (such as calling, inheriting, distributing, and the like) so as to force the relevant technical personnel to repair the overrun defect subcodes.
Referring to fig. 3, a schematic structural diagram of a system for notifying a code defect in a third embodiment of the present invention is shown, and includes a code information recording module 11, a determining module 12, and a notification information sending module 13.
The code information recording module 11 is configured to obtain defect sub-codes in all branch codes in a code library, assign a corresponding ID and repair completion time to each type of defect sub-code, and record the ID and the repair completion time in a defect list.
The judging module 12 is configured to, when the current time reaches any repair completion time recorded in the defect list, obtain a target defect subcode and a target ID corresponding to the any repair completion time, and judge whether the target defect subcode is repaired in all target branch codes related to the target defect subcode.
The notification information sending module 13 is configured to notify, when it is determined that the target defect sub-code is not repaired in all the target branch codes, the target ID and the code numbers of all the target branch codes of the target defect sub-code that are not repaired as information.
Further, the system for notifying the code defect further comprises:
an address assignment recording module 14, configured to assign a corresponding notification information sending address to each type of the defect sub-code, and record the notification information sending address into the defect list.
Further, the notification information sending module 13 includes:
an address acquisition unit 131 configured to extract a target notification information transmission address corresponding to the target ID from the defect list;
a notification information sending subunit 132, configured to send the target ID and the code numbers of all the target branch codes that do not repair the target defect sub-code as information to the target notification information sending address.
Further, the determining module 12 includes:
a judging subunit 121, configured to judge whether the target ID exists in all the target branch codes related to the target defect sub-code.
The system for notifying the code defect further comprises:
a clearing module 15, configured to clear all contents related to the target ID recorded in the defect list when it is determined that the target defect sub-code is repaired in all the target branch codes.
The system for notifying the code defect further comprises:
a repair module opening module 16, configured to open a code repair mode of the code library after the notification information sending module 13 sends the notification information, so that a user requiring an assigned right can edit codes in the code library.
Those skilled in the art will appreciate that all or part of the steps in the method for implementing the above embodiments may be implemented by a program instructing the relevant hardware. The program may be stored in a computer-readable storage medium. Which when executed comprises the steps of the method described above. The storage medium includes: ROM/RAM, magnetic disk, optical disk, etc.
The above-mentioned embodiments only express several embodiments of the present invention, and the description thereof is more specific and detailed, but not construed as limiting the scope of the present invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the inventive concept, which falls within the scope of the present invention. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. A method for notifying a code defect, comprising:
acquiring defect subcodes in all branch codes in a code library, distributing corresponding ID and repair completion time to each defect subcode, and recording the ID and the repair completion time into a defect list;
when the current time reaches any repair completion time recorded in the defect list, acquiring a target defect subcode and a target ID corresponding to the any repair completion time, and judging whether the target defect subcode is repaired in all target branch codes related to the target defect subcode;
if not, taking the target ID and the code numbers of all the target branch codes of the target defect subcodes which are not repaired as information to be notified;
wherein the ID is used as a repair identifier of the corresponding defect sub-code, and after repairing the defect sub-code on the branch code, the ID corresponding to the currently repaired defect sub-code is recorded on the current branch code, and the step of determining whether the target defect sub-code is repaired in all target branch codes related to the target defect sub-code includes:
determining whether the target ID exists in all of the target branch codes associated with the target defect subcode.
2. The method of notifying a code defect according to claim 1, wherein after said step of assigning a corresponding ID and repair completion time to each of said defect sub-codes, said method of notifying a code defect further comprises:
and allocating a corresponding notification information transmission address to each defect sub-code, and recording the notification information transmission address into the defect list.
3. The method according to claim 2, wherein the step of notifying the target ID and the code numbers of all the target branch codes that have not repaired the target defect sub-code as information comprises:
extracting a target notification information sending address corresponding to the target ID from the defect list;
and sending the target ID and the code numbers of all the target branch codes which do not repair the target defect subcodes to the target notification information sending address as information.
4. The method of notifying a code defect of claim 1, wherein after the step of determining whether the target defect sub-code is repaired among all target branch codes related to the target defect sub-code, the method of notifying a code defect further comprises:
and if so, clearing all the contents related to the target ID and recorded in the defect list.
5. The method according to claim 1, wherein after the step of notifying the target ID and the code numbers of all the target branch codes that have not repaired the target defect sub-code as information, the method further comprises:
and opening a code repair mode of the code base so that a user needing the appointed authority can edit the codes in the code base.
6. A system for notifying a code defect, comprising:
the code information recording module is used for acquiring defect subcodes in all branch codes in a code library, distributing corresponding ID and repair completion time to each defect subcode and recording the ID and the repair completion time into a defect list;
a judging module, configured to, when current time reaches any repair completion time recorded in the defect list, obtain a target defect subcode and a target ID corresponding to the any repair completion time, and judge whether the target defect subcode is repaired in all target branch codes related to the target defect subcode;
a notification information sending module, configured to notify, when it is determined that the target defect sub-code is not repaired in all the target branch codes, the target ID and the code numbers of all the target branch codes of which the target defect sub-code is not repaired as information;
wherein, the ID is used as a repair identifier of the corresponding defect sub-code, and after the repair of the defect sub-code on the branch code is completed, the ID corresponding to the currently repaired defect sub-code is recorded on the current branch code, and the judging module includes:
a judging subunit operable to judge whether the target ID exists in all the target branch codes related to the target defect sub-code.
7. The system of claim 6, further comprising:
and the address distribution recording module is used for distributing a corresponding notification information sending address to each defect subcode and recording the notification information sending address into the defect list.
8. The system of claim 7, wherein the notification message sending module comprises:
an address acquisition unit configured to extract a target notification information transmission address corresponding to the target ID from the defect list;
and the notification information sending subunit is used for sending the target ID and the code numbers of all the target branch codes which do not repair the target defect subcodes to the target notification information sending address as information.
9. The system of claim 6, further comprising:
and the clearing module is used for clearing all the contents related to the target ID recorded in the defect list when the target defect subcode is judged to be repaired in all the target branch codes.
10. The system of claim 6, further comprising:
and the repair module starting module is used for starting the code repair mode of the code base after the notification information sending module sends the notification information so that a user needing to specify the authority can edit the codes in the code base.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710253750.3A CN107193677B (en) | 2017-04-18 | 2017-04-18 | Method and system for notifying code defects |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710253750.3A CN107193677B (en) | 2017-04-18 | 2017-04-18 | Method and system for notifying code defects |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107193677A CN107193677A (en) | 2017-09-22 |
| CN107193677B true CN107193677B (en) | 2020-11-20 |
Family
ID=59871291
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710253750.3A Active CN107193677B (en) | 2017-04-18 | 2017-04-18 | Method and system for notifying code defects |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107193677B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108319551B (en) * | 2017-12-29 | 2021-12-17 | 五八有限公司 | Software testing method and device, computer equipment and readable storage medium |
| CN110221933B (en) * | 2019-05-05 | 2023-07-21 | 北京百度网讯科技有限公司 | Code defect auxiliary repairing method and system |
| TWI773939B (en) * | 2019-11-12 | 2022-08-11 | 緯創資通股份有限公司 | Version management system, version management method, and non-transitory computer readable storage medium for version management method |
| CN117667711A (en) * | 2023-12-08 | 2024-03-08 | 广州通则康威科技股份有限公司 | Production line bug detection method, device and system and storage medium |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100347682C (en) * | 2004-12-08 | 2007-11-07 | 上海科泰世纪科技有限公司 | Automatic detection building method |
| CN102141956B (en) * | 2010-01-29 | 2015-02-11 | 国际商业机器公司 | Method and system for managing response of security flaw during development |
| CN102819489A (en) * | 2012-07-05 | 2012-12-12 | 北京航空航天大学 | Software reliability designing method driven by defects |
| CN104182689A (en) * | 2013-05-24 | 2014-12-03 | 阿里巴巴集团控股有限公司 | Method and device for repairing and protecting system |
| CN106528427A (en) * | 2016-11-24 | 2017-03-22 | 上海携程商务有限公司 | Code quality checking method and system |
-
2017
- 2017-04-18 CN CN201710253750.3A patent/CN107193677B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN107193677A (en) | 2017-09-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107193677B (en) | Method and system for notifying code defects | |
| CN110928774B (en) | Automatic test system based on node type | |
| CN110569298B (en) | Data docking and visualization method and system | |
| CN111414229B (en) | Application container exception handling method and device | |
| CN105468393B (en) | Module release upgrade method and terminal installation | |
| CN111459631A (en) | Automatic batch processing method and system for server | |
| CN106844793A (en) | Management method, the apparatus and system of example service | |
| CN105260485A (en) | Method and device for loading data | |
| CN110602209A (en) | Firmware over-the-air upgrading method and system based on DMP | |
| CN105207797A (en) | Fault locating method and fault locating device | |
| EP2390739A2 (en) | A method and apparatus for providing industrial plant information | |
| CN110868309A (en) | Method and device for processing resources in VNFM (virtual network configuration function) and computer storage medium | |
| CN107463371B (en) | Code management and control method and system | |
| CN112446568A (en) | Dispatching method, system and computer readable storage medium | |
| CN111008209B (en) | Data reconciliation method, device and system, storage medium and electronic device | |
| CN114356654A (en) | Backup system, backup method, backup device, computer device, and storage medium | |
| US7281165B2 (en) | System and method for performing product tests utilizing a single storage device | |
| CN105897487B (en) | Equipment management method and device for operation and maintenance system | |
| CN110852571A (en) | House resource management method for franchisee, computer-readable storage medium, and server | |
| CN106301904A (en) | A kind of cluster server management method and device | |
| CN103218255A (en) | Information management method and system for server assembly | |
| CN110866225A (en) | Risk control method and device, electronic equipment and storage medium | |
| CN107256145B (en) | One kind is deployed to ensure effective monitoring and control of illegal activities method for managing object and device | |
| JP7516180B2 (en) | Work support system, work support device, and work support method | |
| CN113015150A (en) | One-to-many, power consumption-reducing and quick wireless device connection method and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |