Differences and comparison between Bugzilla and bugfree

Introduction

1.1 Introduction to bugfree

Bugfree is a lite defect management system based on Microsoft's software development philosophy, free and open source code, and Web. It is currently the only "clone" Microsoft internal bug management tool product stuido (formerly raid) free software. Bugfree is written in PHP + MySQL and runs on both Linux and Windows platforms. Bugfree 2.0 includes the following design ideas:

-Code: The program is an implementation (ing) of the requirement design specification instruction document (SPEC );

-Test Case: it is also an implementation (ing) of spec, but only from the test point of view;

-Test Result: Use test case (test ing) to check code (Development ing );

-Bug: The difference between the two mappings may be a bug (Code deviation from spec)

In this way, from the test case to the test result to the bug, the three are organically combined.

1.2 introduction to Bugzilla

Buzilla is a free tool provided by Mozilla to record product defects and trace. It can build a complete BUG Tracking System for you, it consists of four parts: reporting bugs, querying bug records and generating reports, handling and solving, administrator system initialization, and setting.

 

2 administrator operation comparison

2.1 main work content of bugfree

2. Project Management 1) Add and terminate projects 2) Bug module Management 3) Case module Management

2. User Management 1) add, edit, and delete users (only one admin in bugfree can perform background management, but Bugzilla can create a product and then assign it to the Administrator, the product administrator can manage the projects he is responsible for to relieve the admin burden .)

2. Group Management 1) assigns a project to a certain type of users. Otherwise, the user is not authorized to perform any operations. 2) The user can only operate on his or her own project and cannot operate on other projects.

2. System Maintenance (direct physical database operation) 1) virtual directory backup 2) Database Backup

2.2 Main work content of Bugzilla

2. Product, version, and Component definitions

2. Specify the corresponding developer (owner) and tester (QA contact) of the module)

2. Group Definition and Division

2. Definitions of bug severity and priority during testing

2. Add users and set group and permissions for all users

(2) setting of main parameters (parameters) (1) urlbase: Enter the IP address of the server where the bugzilla tool is located. 2) usebuggroupsentry: Set to on and can be grouped. 3) whinedays: If the bug is not handled within the period set by whinedays, the mail will be automatically resend. The default value is 7 days. 4) defaultpriority: Set the default priority 5) commentonresolve: Set to on, the system will force the developer to fill in the modified content after handling the bug.

Note: Bugzilla is only frequently used by the first two users. There is no strict bugfree in terms of permission control. For example, we can access projects that do not belong to ourselves (360 in the United States ).

 

3. user operation comparison

3.1 create a bug

2. The same function: directly create.

2. bugfree: A series of fields can be automatically copied based on case and result.

2. Bugzilla: modify some fields after cloning.

Comparison of creating bug fields:

Bugfree field Bugzilla field remarks
Bug title √ common
Project name/module path √ common
Assigned to √ common
CC to √ common
Severity √ common
Priority √ common
Bug type √ common
How to discover
Operating System √ common
Browser √ common
Creator √ common
Create build √ common
Machine configuration
Keyword √
Related bug dependency bug
Result x
Appendix √ common
Recurring steps √ common
X expiration date
URL annotation description
X product link statistics

Note: √ indicates that this field exists, and X indicates that this field does not exist. Common fields are consistent. 3.2 edit bug 2. The same function: you can modify and save Operation Records.

 

2. Bug type comparison:
Bug type-bugfree bug type-Bugzilla remarks
Code error defect is often used
Interface Optimization is generally used
Requirement change request is generally used
General Use of enhancement
Configuration
Installation and deployment
General security-related use
Performance optimization is generally used
Specification-related
Test script
Transaction Tracking
Other rollup task support is not commonly used

Note: The two developers have different development backgrounds and the types are of little significance to each other. The key is to determine which product is suitable for us.

 

2. How to find and compare:
How to find-bugfree remarks
Centralized Test
Test Cases
Random test
Version Verification Test
Customer Feedback
Partner
Regression testing
Requirement check
Others

Note: Bugzilla does not have this field. By convention, our bugs are generally found during centralized testing.

 

2. Solution comparison
Solution-bugfree solution-Bugzilla remarks
Fixed fixed
Postponed later
Won't fix
By design invalid
Duplicate duplicate
X accepted
X remind
X worksforme
X pushed
External x
Not repro x

Note: X indicates that this field does not exist. Common fields are consistent.

 

2. Other comparisons:

Bugzilla can reference and reply to a comment (operation record). bugfree does not have this function.

 

3.3 list display

2. The same function: You can customize the display fields.

2. bugfree: You can customize the number of pages.

2. Bugzilla: it cannot be paged. It is difficult to locate a bug when there is a large amount of data.

 

3.4 quick search

2. The same function: customize and save the query conditions.

2. bugfree: The Search Condition and search result are displayed on a page.

2. Bugzilla: it is easy to use when many query conditions are set.

 

3.5 data export

2. The same function: both can be exported.

2. bugfree: by default, all fields are exported in HTML format.

2. Bugzilla: It can be exported to the Excel format and the fields can be customized.

 

3.6 data statistics

2. The same function: statistics are available.

2. bugfree: collects statistics on the currently selected bugs, cases, and results, and generates Custom reports. The results are easy to understand and powerful. Bug-related reports include: 1) number of project bugs 2) Number of module bugs 3) Bug severity statistics 4) Bug solution statistics 5) Bug status statistics 6) Bug type statistics 7) number of new bugs per day 8) Number of bugs solved per day 9) Number of bugs closed per day 10) Number of bugs submitted per day 11) Number of bugs submitted per person 12) number of bugs in the head of each person 13) Number of bugs solved by each person 14) Number of bugs closed by each person 15) Bug handling time 16) Bug handling step statistics and so on. All levels of personnel can view reports, so that the bug can be solved quickly. There are also many reports generated by case and result.

2. Bugzilla: You can view simple statistics on the product link. For further reports, data can only be manually generated after being exported.

 

3.7 user-related bug and case presentation

2. Same function: display specific bugs by setting query Conditions

2. bugfree: You can view bugs, cases, and results in the lower-left corner of the page.

Bug and case display in bugfree include 1) assigned to me 2) created by me 3) a drop-down list is displayed when I query a large amount of data for easy locating. Developers can be urged to quickly respond to bugs.

 

3.8 compare the usability of other users from the following perspectives:
Description: bugfree Bugzilla
Easy to see. General functions are easy to see.
It is easier to learn. It does not help you clearly understand software.
Easy to use. Generally, whether to use the software using user manual
User-friendly Chinese and English
The database is located in the United States.
Good maintainability
User habits are generally used at present and used

 

4. Integration with other testing tools and data

4.1 integration with case

2. bugfree: It can be combined with testcase. First, design the case and execute the case. Then, generate a bug based on the result. 1) the test case module and the bug module remain independent. 2) create a module based on business processes and functions. Currently, the case module can only be input or copied, but cannot be imported in batches (only in the background database ). Whether it can be combined with testlink remains to be studied.

2. Bugzilla: currently, it is not integrated with case, but is a separate Bug management tool.

4.2 integration with result

2. bugfree: it is combined with testcase and testresult. First, design the case and execute the case. Then, generate a bug based on the result. Create a bug for the test result that fails to run. Automatically copy the following information: 1) Result title-> Bug title 2) result Project/module path-> bug Project/module Path 3) Related Result 4) Operating System 5) browser 6) run build-> Create build 7) machine configuration 8) Recurrence steps

2. Bugzilla: it is not currently integrated with result.

In summary, bugfree has XX advantages and Bugzilla has XX advantages. Therefore, we adopt xx.

 

5. Differences between the case section in bugfree and testlink:

5.1 batch Import

2. bugfree: currently, you can only edit input cases or copy input cases. Batch import can only be performed in the background database.

2. testlink: You can import Excel Data to the front-end for Quick loading.

5.2 batch query

2. The same function: both of them can perform batch query based on multiple query conditions.

2. bugfree: after batch query, use the paging Control for easy reading.

2. testlink: after batch query, there is no paging control.

5.3 batch assignment

2. Same functions: both can be assigned to corresponding personnel.

2. bugfree: can only be assigned separately.

2. testlink: can be assigned in batches according to the test plan.

5.4 test plan execution

2. testlink: We recommend that you test the plan and execute the case

5.5 test result record and statistics

2. Same function: Results and statistics can be recorded.

2. bugfree: the statistical report feature is powerful.

2. testlink: general statistical functions.