(51CTO official C/C development engineer QQ group (1090119), please enter your ID for verification. ??Programmers are a very hard industry, generally facing endless overtime, but through analysis, it is found that most of the overtime is not because the project is not working at all times, but because the early development is not well designed, and it is impossible to track or even manage in the later stage. bugs, resulting in uncontrollable development time, which is commonly referred to as "bugs are the source of overtime." Therefore, if we can prevent and expose a lot of bugs in the design stage, it will greatly reduce the pressure on programmers and make the development work very happy!?? The technical clinic is a 51CTO community brand program. Broad technical netizens answer questions. From hot technology to cutting-edge knowledge, from technical Q&A to industry design. Each issue has a theme, standing at the forefront of the latest and hottest technology to guide you!?? In this issue of technology clinics, we invite experts in the field of software development and management, IT book author Xiao Ge, and we comment on common bugs in C/C development management method. ?? Expert in this issue: Xiao Ge Specialty Field: C/C , Commercial Data Transmission Expert Profile: R&D Director of Puluo Communication () Co., Ltd., MCSE, commercial programmer. Has many years of experience in software development and development management. Proficient in C/C , TCP/IP, good at the development of distributed databases, server clusters and parallel computing. He has served as a guest lecturer at Southwest Jiaotong University, teaching the course "C/C Language Error-Free Programming". He has worked as a project manager in many companies, and has worked on projects such as "httptunnel firewall tunnel traversal system", "freeppV1.5 server cluster", "electronic whiteboard subsystem" and so on. Author of "0Bug----C/C Commercial Engineering". Check out the highlights of this outpatient clinic: doctor.51cto/develop-144.html Participate in the latest technology outpatient clinic: doctor.51cto/Selected questions and answers from netizens in this issue for netizens to learn and reference. Q: Hello Mr. Xiao! The primary purpose of software testing is to find bugs in the software. How to manage the bugs found in testing will directly affect the role of testing. Only by managing these errors accurately, agilely and accurately can software errors be eliminated and the software to be released be guaranteed to meet the requirements designed. In the process of practical software testing, each bug must pass the management process of testing, recognition, repair, verification, etc., which is an important part of software testing. Relatively speaking, bug management is also very important. Can you briefly discuss the general process of bug management? A: I understand that bug management is necessary only for software companies. In general, bug management is a management process, and it has nothing to do with the program originally, but there is such a mechanism for managing "people" in the enterprise, so as to track the bug and implement it to the head of the management. Generally speaking, a bug management system should be installed on the intranet of the enterprise. Our company uses Mantis, which is an open source product and is very easy to use. According to the permissions, QA detects bugs, that is, submits them to this system, and PM depends on the situation. , assigned to a certain RD management, after management, RD reply has been managed, and modify the status, QA does regression verification, and finally achieves a closed loop. In my understanding, it is not difficult for ordinary testers to find bugs, but how to accurately describe bugs is difficult. Generally, the more accurate QA describes the generation of bugs, the faster RD can locate and manage them. But this requires experience, and not everyone can do it. Therefore, I generally recommend that the management and management of bugs should be a joint effort of RD and QA, not just a problem of the testing part. I emphasize white-box testing in development, that is, after RD has written each module, the test project of the module must be attached when submitting the manuscript. These test codes will not be released in the end, but they can help PM and QA to do the initial analysis. Module verification, originally only need to have this verification process, many bugs can be managed before RD submits the code. My new book "0Bug----C/C Commercial Engineering", was originally a book written by RD for RD, to help RD develop good development habits and understand the differences of many details in development, so that Write programs with as few bugs as possible. This itself is an attempt to manage bugs from the source and reduce the work intensity of later QA.
[Technical Clinic No. 132] Actual combat is king: Analysis of common bugs in C-C development.doc)
收藏
