Bugzilla Interview Questions

Bugzilla is defined as a bug tracking system and a testing tool that was originally developed and used by the Mozilla project. It was released by open-source software and was adopted by many organizations for the purpose of a bug tracking system and can be used for both proprietary projects and products as well as free and open-source software.

The components of Bugzilla include –

• Administration and general assembling
• All of the documentation
• All of the incoming and outgoing emails.
• Bug list and everything related to it.
• Reporting and managing the generating reports.
• Every detailed aspect of the user account and its management from a user’s perspective.
• User interfaces and issues related to it.

Yes, Bugzilla is a defect management protocol hence reports are actually a piece of defect or work which are utilized to analyze the current state of bug. One of the essential motives of defect report is to analyze the behavior, communication and the stage of the defect which is occurring at any of the stages in the life cycle.

The significant feature of Bugzilla is that page which displays entire details of a bug. For most of the pages, labels are hyperlinks. Thus, clicking over them will take to the next context of that individual field. If the field is marked by ‘*’ then they might not be present at every installation.

The fields of Bugzilla are-Product

• Component
• Platform
• Operating system
• URL
• Summary
• Description

A group of line, a bar or Pie Charts is referred to be as graphical reports they are very helpful in order to perform a number of functions. For example, if any of the users want to know about the component which has the maximum number of defects and want to represent it in a graph then they collect it from the options like-

• Severity on x-axis
• Component on y-axis

Bugzilla majorly performs the following-

• It tracks the bugs and code changes.
• It can communicate with fellow mates.
• It can efficiently submit the patches.
• It can review.
• It can manage quality assurance.

Bugzilla is a defect management tool which allows the development and modification with its segments on the web interface. It is an open source tool which allows the testing in order to figure out the defects. It also supports ‘defect tracking system’ or ‘bug tracking system’.

In order to create a user account in Bugzilla, I would perform-

• First I will enter the email address and the actual name of the user in the space. Then I will select the ‘create account’ button.
• After clicking over the above, I will receive a confirmation email which will contain the essential login details. A password will be provided in order to access the account later.

For the deployment of Bugzilla the system requirement is-

• Compatible database management system (MySQL).
• A perfect release of Perl 5.
• Association of Perl modules.
• Compatible web server.
• Any of the suitable mail transferring protocol.

Bugzilla was launched in 1998. It is written in the Perl language and its latest version is Bugzilla 4.2.5.

Yes, of course, there is a difference between both of them.

• Quality Centre is a test management tool, on the other hand, Bugzilla is a defect management tool.
• Quality Centre supports the complete application lifecycle management while Bugzilla is a part of test management.
• Quality Centre also supports the design, execution, traceability and defect management while Bugzilla doesn't.

The most essential and appropriate Bugzilla features are-

• It is an integrated and product based Security Scheme.
• It has inter-bug dependency graphing.
• It has advanced report capabilities.
• It has the strongest RDBMS backend.
• It has an extensive configuration.
• It has the most significant bug resolution protocol.
• Email, XML, HTTP and console.

Editing is extremely convenient in Bugzilla as it is provided with a provision for editing on an existing bug. If the user wants to edit it during the lifecycle then in most of the cases there is an edit hyperlink option which can be preferred. It entirely depends on the administrator to avail the editing options for different fields.

In Bugzilla, the dependency tree link highlights the dependent relationships of the bug. It is characterized in a tree-like structure and user can easily change the depth in order to either show or hide the resolved bug from the page.

Here the user can store a number of queries on the server and in case someone runs regularly, it would just be a drop-down menu away.

In ‘user to watch’ text entry box right after entering the email and names of the users which are the line by commerce one can watch the bugs of other users. This is the most significant feature through which the seamless events are enabled when developers wish to change their project.

The provision of cloning in an existing back is also supported in Bugzilla. The bugs which are created later actually are having most of the settings from the former bug. Through this most of the similar fields can be tracked which require different handling in case of a new bug.