Bugzilla – Installation

Bugzilla – Installation ”; Previous Next The Bugzilla GIT website is the best way to get Bugzilla. Download and install GIT from the website − https://git-scm.com/download and Run it. git clone –branch release-X.X-stable https://github.com/bugzilla/bugzilla C:bugzilla Where, “X.X” is the 2-digit version number of the stable release of Bugzilla (e.g. 5.0) The another way to download Bugzilla is from the following link − https://www.bugzilla.org/download/ and move down to the Stable Release section and select the latest one from the list as shown in the following screenshot. Click on Download Bugzilla 5.0.3. Bugzilla comes as a ”tarball” (.tar.gz extension), which any competent Windows archiving tool should be able to open. PERL Modules Bugzilla requires a number of Perl modules to be installed. Some of them are mandatory, and some others, which enable additional features, are optional. In ActivePerl, these modules are available in the ActiveState repository, and are installed with the ppm tool. Either it can use it on the command line or just type ppm and the user will get a GUI. Install the following mandatory modules with the following command. ppm install <modulename> Some of the most important PERL modules have been described below. CGI.pm − It is an extensively used Perl module for programming the CGI (Common Gateway Interface) web applications. It helps to provide a consistent API for receiving and processing user inputs. Digest-SHA − The Digest-SHA1 module allows you to use the NIST SHA-1 message digest algorithm from within the Perl programs. The algorithm takes as input a message of arbitrary length and produces as output a 160-bit “fingerprint” or “message digest” of the input. TimeDate − TimeDate is a class for the representation of time/date combinations, and is part of the Perl TimeDate project. DateTime − DateTime is a class for the representation of date/time combinations, and is part of the Perl DateTime project. DateTime-TimeZone − This class is the base class for all time zone objects. A time zone is represented internally as a set of observances, each of which describes the offset from GMT for a given time period. DBI − It is the standard database interface module for Perl. It defines a set of methods, variables and conventions that provide a consistent database interface independent of the actual database being used. Template-Toolkit − The Template Toolkit is a collection of Perl modules, which implement a fast, flexible, powerful and extensible template processing system. It can be used for processing any kind of text documents and is input-agnostic. Email-Sender − The Email-Sender replaces the old and problematic email send library, which did a decent job at handling the simple email sending tasks, but it was not suitable for serious use for a several reasons. Email-MIME − This is an extension of the Email-Simple module. It is majorly used to handle MIME encoded messages. It takes a message as a string, splits it into its constituent parts and allows you to access the different parts of the message. URI − A Uniform Resource Identifier is a compact string of characters that identifies an abstract or physical resource. A URI can be further classified as either a Uniform Resource Locator (URL) or a Uniform Resource Name (URN). List-MoreUtils − It provides some trivial but commonly needed functionality on lists, which is not going to go into the List-Util module. Math-Random-ISAAC − The ISAAC (Indirection, Shift, Accumulate, Add, and Count) algorithm is designed to take some seed information and produce seemingly random results as the output. File-Slurp − This module provides subs that allow you to read or write files with one simple call. They are designed to be simple, have flexible ways to pass in or get the file content and are very efficient. JSON-XS − This module converts the Perl data structures to JSON and vice versa. The primary goal of JSON-XS is to be correct and its secondary goal is to be fast. Win32 − The Win32 module contains functions to access Win32 APIs. Win32-API − With this module, you can import and call arbitrary functions from the Win32”s Dynamic Link Libraries (DLL), without having to write an XS extension. DateTime-TimeZone-Local-Win32 − This module provides methods for determining the local time zone on a Windows platform. The following modules enable various optional Bugzilla features; try to install these based on your requirements − GD − The GD module is only required if you want graphical reports. Chart − This module is only required if you would want graphical reports as the GD module. Template-GD − This module has the template toolkit for the template plugins. GDTextUtil − This module has the text utilities for use with the GD. GDGraph − It is a Perl5 module to create charts using the GD module. MIME-tools − MIME-tools is a collection of Perl5 MIME modules for parsing, decoding and generating single or multipart (even nested multipart) MIME messages. libwww-perl − The World Wide Web library for Perl is also called as the libwww-perl. It is a set of Perl modules, which give Perl programming an easy access to send requests to the World Wide Web. XML-Twig − It is a Perl module used to process XML documents efficiently. This module offers a tree-oriented interface to a document while still allowing the processing of documents of any size. PatchReader − This module has various utilities to read and manipulate patches and CVS. perl-ldap − It is a collection of modules that implements LDAP services API for Perl programs. This module may be used to search directories or perform maintenance functions such as adding, deleting or modifying entries. Authen-SASL − This module provides an implementation framework that all protocols should be able to share. Net-SMTP-SSL − This module provides the SSL support for Net-SMTP 1.04 RadiusPerl − This module provides simple Radius client facilities. SOAP-Lite − This module is a collection of Perl modules, which provide a simple and lightweight interface to the Simple Object Access Protocol (SOAP) on both the client and the server

Bugzilla – Overview

Bugzilla – Overview ”; Previous Next Bugzilla is an open-source tool used to track bugs and issues of a project or a software. It helps the developers and other stakeholders to keep track of outstanding problems with the product. It was written by Terry Weissman in TCL programming language in 1998. Later, Bugzilla was written in PERL and it uses the MYSQL database. Bugzilla can be used as a Test Management tool since it can be easily linked with other test case management tools like Quality Centre, ALM, Testlink, etc. Bugzilla provides a powerful, easy to use solution to configuration management and replication problems. It can dramatically increase the productivity and accountability of an individual by providing a documented workflow and positive feedback for good performance. Most commercial and defect-tracking software vendors charged enormous licensing fees in the starting days of Bugzilla. As a result, Bugzilla quickly became a favorite among the open-source users, due to its genesis in the open-source browser project with Mozilla. It is now the most precious defect-tracking system against which all the others are measured. Bugzilla puts the power in an individual’s hand to improve the value of business while providing a usable framework for natural attention to detail and knowledge store to flourish. Bugzilla – Key Features Bugzilla has many keys as well as advanced features, which makes it unique. Following is a list of some of Bugzilla’s most significant features − Bugzilla is powerful and it has advanced searching capabilities. Bugzilla supports user configurable email notifications whenever the bug status changes. Bugzilla displays the complete bug change history. Bugzilla provides inter bug dependency track and graphic representation. Bugzilla allows users to attach Bug supportive files and manage it. Bugzilla has integrated, product-based, granular security schema that makes it more secure. It has complete security audit and runs under the Perl’s taint mode. Bugzilla supports a robust, stable RDBMS (Rational Data Base Management System) back end. It supports Web, XML, E-Mail and console interfaces. Bugzilla has a wide range of customized, user preferences features. It supports localized web user interface. Extensive configurability as it allows to be configured with other test management tools for a better user experience. Bugzilla has a smooth upgrade pathway among different versions. In the next chapter, we will discuss the prerequisites for installing Bugzilla. Print Page Previous Next Advertisements ”;

Installation Prerequisites

Bugzilla – Installation Prerequisites ”; Previous Next To install and run Bugzilla on the server, the core requirement is to have Perl installed. This means that Bugzilla can be installed on any platform, where Perl can be installed; including Windows, Linux and Mac OS X. Hardware Requirements It is recommended to have a 4 GB RAM or more. Should have a Fast Processor, for instance, at least 3GHz or more. The hard disk space depends on the size of the team and the number of defects. A 50GB hard disk memory is a quite enough. Software Requirements Bugzilla requires a database server, a web server and Perl. In all the cases, (the newer, the better) the newer releases have more bug fixes, but they are still supported and they still get security fixes from time to time. Perl − Bugzilla 4.4 and older requires Perl 5.8.1 or newer, but Bugzilla 5.0 and newer will require Perl 5.10.1 or newer. It is not recommend installing Perl 5.8.x at this stage. Instead, install Perl 5.12 or newer, as these newer versions have some useful improvements, which will give better user experience. Database Server − Bugzilla supports MySQL, PostgreSQL, Oracle and SQLite. MySQL and PostgreSQL are highly recommended, as they have the best support from Bugzilla and are used daily by the Bugzilla developers. Oracle has several known issues and is a 2nd-class citizen. It should work decently in most cases, but may fail miserably in some cases too. SQLite is recommended for testing purposes only for small teams. If MySQL is used, version 5.0.15 is required by Bugzilla 4.x, but highly recommended version 5.5 or newer. For PostgreSQL installation, version 8.3 is required. Web Server − Bugzilla has no minimum requirements for its web server. It is recommended to install Apache 2.2, although Bugzilla works fine with IIS too (IIS 7 or higher recommended). To improve performances in Apache, recommend to enable its mod_perl module. Print Page Previous Next Advertisements ”;

Bugzilla – Login

Bugzilla – Login ”; Previous Next To login into Bugzilla, we have to follow the steps given below. Step 1 − Click on the Log In link on the header of the homepage. Step 2 − Enter the Email Address, Password and click on Log In Step 3 − The user will be logged in successfully; the users can see their user id in the header section. Step 4 − The user can see open bugs assigned to him, reported by him and requests addressed to him at the left bottom section. Print Page Previous Next Advertisements ”;

Bugzilla – Logging a New Bug

Bugzilla – Logging a New Bug ”; Previous Next The procedure of filling a new bug is quite simple and has been explained below. Step 1 − Click on the ‘New’ link, present on the header or the footer or Click on the File a Bug button on the home page as shown in the following screenshot. Step 2 − Now, select the product group in which the bug is noticed. Step 3 − After selecting the Product, a form will appear where the user should enter the following details related to the bug − Enter Product Enter Component Give Component description Select version Select severity Select Hardware Select OS Enter Summary Enter Description Attach Attachment Note − The above fields vary as per the customization of Bugzilla. The Mandatory fields are marked with a red asterisk (&ast;). Step 5 − Once the user starts typing in the Summary, Bugzilla filters the already logged in defects and displays the list to avoid duplicate bugs. Step 6 − Click on the Submit Bug button to log the bug. Step 7 − As soon as the user clicks on the Submit bug button, a Bug Id is generated with the details that of bug as that were entered. Step 8 − The Deadline and the Status will be shown as depicted in the following screenshot. A user can also add additional information to the assigned bug like URL, keywords, whiteboard, tags, etc. This extra-information is helpful to give more details about the Bug that is created. Large text box URL Whiteboard Keywords Tags Depends on Blocks In the next chapter, we will learn how a bug can be cloned. Print Page Previous Next Advertisements ”;

Bugzilla – Graphical Reports

Bugzilla – Graphical Reports ”; Previous Next Graphical reports are a group of line, bar and pie charts. These Reports are helpful in many ways, for example if a user wants to know which component has the maximum number of defects reported and wants to represent in the graph, then that user can select from the following two options − Severity on the X-axis Component on the Y-axis Then click on Generate Report. It will generate a report with crucial information. Similarly, the user can a select number of combinations from those that are available. Generate Graphical Reports To generate graphical reports in Bugzilla, we have to follow the steps given below. Step 1 − To begin with, click on the Reports link at the header of the homepage. Step 2 − Click on the Graphical Reports hyperlink, which is listed under the Current State section as shown in the following screenshot. Step 3 − Now, set various options to present reports graphically. Some of the important options are given below. Vertical Axis Horizontal Axis Multiple Images Format- Line graph, Bar chart or Pie chart Plot data set Classify your bug Classify your product Classify your component Classify bug status Select resolution Step 4 − Click on Generate Report to display a Bar chart, where the Severity of a bug is the vertical axis, while the Component “Widget Gears” is the horizontal axis. Step 5 − Similarly, a Line Graph can be created for % Complete Vs Deadline. The result for the above mentioned line graph will be as follows. Print Page Previous Next Advertisements ”;

Bugzilla – Sample Web Application

Bugzilla – Sample Web Application ”; Previous Next The Bugzilla installation requires several technical aspects to start with. A few websites provide the Bugzilla web application – Landfill: The Bugzilla Test Server is one of these. https://landfill.bugzilla.org/bugzilla-2.16.11/ this is the testing and demonstration website. Note − Landfill is a home for test installations of the Bugzilla bug-tracking system. If you are evaluating Bugzilla, you can use them to try it. They are also useful if you are a developer and want to try to reproduce a bug that somebody has reported. Once you navigate to the above-mentioned URL, the Bugzilla home page will display as shown below − Print Page Previous Next Advertisements ”;