The editor of Downcodes will introduce you to BugFree, a streamlined web-based defect management tool. It draws on Microsoft's software development philosophy and presents it in the form of free and open source code. It is one of the few free software that has successfully "cloned" Microsoft's internal bug management tool Product Studio (formerly called Raid). This article will delve into the introduction of BugFree, the code completion process, and how to deal with software defects. I hope it can help you better understand and use this tool.
BugFree is a free, open source, Web-based streamlined defect management tool that draws on Microsoft's software development philosophy. It is currently one of the few free software that "clone" Microsoft's internal bug management tool Product Stuido (formerly called Raid).
BugFree is a free, open source, Web-based streamlined defect management tool that draws on Microsoft's software development philosophy. It is currently one of the few free software that "clone" Microsoft's internal bug management tool Product Stuido (formerly called Raid).
BugFree is written in PHP+MySQL and can run on both Linux and Windows platforms. The design ideas included in BugFree 2.0 are:
– Code: The program is an implementation (mapping) of the requirements design specification document (Spec);
– Test Case: It is also an implementation (mapping) of Spec, but from a testing perspective;
– Test Result: Use Test Case (test mapping) to check the Code (development mapping);
– Bug: The inconsistency between the two mappings may be a bug (Code deviates from Spec)
In this way, from test cases (Test Case) to test results (Test Result) to defects (Bugs), the three are organically combined.
BugFree in "Digital Nervous System" is written in open source PHP+MySQL and runs based on the browser. I didn't have any previous development experience with Linux+Apache+MySQL+PHP, but I was lucky enough to recruit two excellent web programmers who were able to build such a system in just two months. Among them, BugFree was developed by my colleague Wang Chunsheng. It took him less than a month to write the code, which surprised me and made me realize the charm of web development based on Linux.
After we test it for more than a month, it can be used in actual work. BugFree has become the most important tool in our daily work. Every employee is also accustomed to using Bug to record and track things. Not only defects in the code can be bugged, but also new requirements, design changes, etc. can use this bug management system. Manage effectively. In fact, Bugs can not only be used to record defects in software, but can also be used to track daily affairs of the company. For example, before the company's online reimbursement system was established, we used BugFree to handle reimbursement. Even, a colleague gave me this bug: Your desktop is too messy, please tidy it up :-)
Further reading:
Usually when people find software defects, they classify software defects. There is only one way to classify them, which is the severity level. Is there no other way to classify them? For example, we encounter the following situation. The tester finds that there is a function that must be added. At this time, he tells the programmer, and the programmer says that there is no time or it is not necessary. In this case, this situation will cause a conflict between the two. If you waffle, the final result will not be known. This will dampen the enthusiasm of the testers. Next time they will not consider the product problems as much as they can, as long as it can run. In fact, this situation can be solved. Below I will mention a new software defect classification concept to effectively solve this problem.
Software defects are not only serious errors, but also functions that are not implemented. At this point, maybe everyone understands that the needs have not been taken into account, but the needs will not be perfect once, and it requires everyone's joint efforts to continuously improve. So how can we effectively implement the good suggestions made by testers? This is what I want to say next. There is another way to classify software defects. According to the defect content, they are mainly divided into requirement bugs and program bugs. The advantage of this classification is that the person responsible for bug handling is clearly defined. We all know that program bugs are handled by the relevant developers. The following mainly discusses demand bugs. Judging from the name, demand bugs need to be handled by demand personnel. How to deal with it and how to be effective in the process? At this time, our testers submit the requirement bug not to the programmer, but to the requirements analyst for processing. However, what I want to emphasize here is the positioning of requirement bugs. If this bug is clearly mentioned in the software requirements specification, it is impossible to locate it as a requirement bug. It must be implemented by programmers and is called a software functional defect. , the submission is handled by the programmer. But if the requirements specification does not clearly mention it, we can locate it as a requirement bug.
The above is the content about bugfree. I hope it will be helpful to everyone.
I hope this introduction to BugFree will be helpful to everyone. The editor of Downcodes will continue to bring you more practical technical articles. If you have any questions or suggestions, please leave a message!