BUGZILLA: Software Test Management Tool
course's star rating by considering a number of different factors
such as the number of ratings, the age of ratings, and the
likelihood of fraudulent ratings.
Find online courses made by experts from around the world.
Take your courses with you and learn anywhere, anytime.
Learn and practice real-world skills and achieve your goals.
Bugzilla is an extremely popular, browser based, full featured Bug Tracking and Testing tool. It is used in thousands of installations around the world - from small software shops to some of the world's largest and most popular software products including MOZILLA FIREFOX, Apache server, LINUX Kernel to just name a few.
Learn and Master Bugzilla to build a WORLD CLASS defect tracking system for your organization and team.
Bugzilla: The FREE Testing Tool used on the World's most used Software Products
Bugzilla is used by both Microsoft Tech based companies and Open Source companies alike - product companies or services or consulting firms - have benefited from the robust, scalable and no-frills Bugzilla.
Course Overview and Contents
Upon completing this course, you will be able to use Bugzilla as a powerful tool in quality assurance and project management for your organization. You will also be able to implement end-to-end defect tracking and management for your product or project alike.NOTE:
Not for you? No problem.
30 day money back guarantee.
Learn on the go.
Desktop, iOS and Android.
Certificate of completion.
|Section 1: An INTRODUCTION to Bugzilla|
Welcome and congrats on your interest to learn Bugzilla.
I am Srikanth and have been managing software development for more than a decade. Bugzilla is one of the first things I get configured for my projects and I find it is an invaluable tool.
First of all, what is Bugzilla?
HOW TO: Watch this course in HD
|Section 2: Getting Started with BUGZILLA|
In this lesson, we will start with the very basics and see how you can get an user account in your Bugzilla installation.
Once that you have a Bugzilla account for yourself and before you actually start recording bugs and issues - you must create a product on Bugzilla.
I will leave the other options as it is we will see some of them later in the course.
In this lesson we will see how you can create new Bugzilla accounts for your team members or perhaps for your customers. In a previous lesson, you have already seen how a new user can be created by self registration and in this lesson we will see how an Admin level user can create user accounts for others.
For now, I will only want to look at the link here called "Users" - which will allow you to create new users as we want to do in this lesson. [crud possible]
There is a link "add a new user" - and we need to click it.
This interface is real simple and let us create a new user real quickly now.
For the "Login name" - give the email address of the new user - I am going to paste it here. Then the optional real name.
You can disable issues related mails from going to this user if you turn on this checkbox labelled "Bugmail Disabled".
The next box is interesting. Suppose you were disabling an existing user from accessing Bugzilla - you can write a message in this box. And if you write ANYTHING in this box, even an empty space character, then that user will be disabled and this message will be displayed when the user tries to log in.
However for this lesson, we will ignore this box.
You can see a confirmation message in the next page that the user has been created.
Now, I want to quickly do a test that the user I have created will be able to login correctly. Since I am already logged in - I will have to logout and try to login with the new user id. One simple trick is to login with a different browser - since the cookie that Bugzilla stores to remember current login is only applicable to that particular browser. Since I am currently using Firefox, I will login through Internet Explorer.
I will open IE and login.OK that looks great and I have been able to login with the new user.
So, in this lesson, we have seen how to create new users on the system. You might want to do this for your own team members or the customers team members. Once you create the userids, you should of course give them the user names and passwords that you have set and have them change the password later if they want.
|Section 3: The PHILOSOPHY of Bugzilla|
Let us dive right into Bugzilla and see the core page of Bugzilla which displays a particular bug. It's a good place to explain some important Bugzilla concepts and general best practices.
In conclusion, you have seen the anatomy of a bug in this lesson - that is all the different items of information that will make up a well written bug in Bugzilla.
As soon as a bug is entered into Bugzilla - it's lifecycle starts. In this lesson, you will get a solid understanding of the workflow provided by Bugzilla throughout the life of a bug. You will also get a clear idea of how different players like the Tester, Developer or the Manager can change the course of a Bug in Bugzilla.
Typically, very busy engineers will probably generally ignore UNCONFIRMED that have been assigned to them, until they have been confirmed in one way or another.
Sometimes, you will come across bugs that just can not be fixed, maybe because the bug itself is invalid or because of some technical or budgetary limitation. In that case the bug can change state directly from an CONFIRMED or UNCONFIRMED to RESOLVED.
The most common example of when to use WONTFIX is when it is too expensive, in time and effort to fix some trivial bug.
|Section 4: FILING Bugs - Create a BUG REPORT|
In this lesson, we will see how to report a new bug.
Try to limit these steps to a minimum set required to reproduce the problem. This will make the life of developers easier. If there are more than one ways to reproduce the same bug - then definitely write them down also.
So, we have successfully reported a bug and seen the simplicity that Bugzilla brings in its design. You can turn on other fields such as "URL" if it useful to you by visiting the Administration section.
|Lecture 9||3 pages|
Effective bug reports are the most likely to be fixed. These guidelines explain how to write such reports.Principles
In a previous lesson, we saw from a tester's perspective on how to raise a new bug. And when a new bug is raised, we will also have to specify a product, and a component that the bug belongs. Every component will have a default bug assignee.
|Section 5: ADDITIONAL: Bugzilla Installation Guide|
This section distills some Bugzilla tips and best practices that have been developed.
While Bugzilla installation is not covered in this course - this simple lesson must help you understand the sequence in which Bugzilla should be installed on a Windows machine.
PLEASE NOTE: A fully featured Bugzilla installation test server is available for your FREE access online, hosted by the Mozilla Corporation. Please search for "Landfill: The Bugzilla Test Server".
|Section 6: A Thank You GIFT for you|
A Thank You GIFT for you
Srikanth's recent leadership role as Senior Software Delivery Manager for one of the World's Largest Learning Management System implementation for online structured higher education - with more than 400,000 students pursuing online Masters/Bachelors and Certificate for one of India's largest and most diversified Education Providers with a global footprint in countries including the US, Singapore, UAE-Dubai, Malaysia etc.
Srikanth has directly managed clients including Telegraph Media Group UK, Microsoft, Yahoo, Marriott, Expedia, British Airways, Precise Media Group UK, Sequoia Media Group US, Tesco, and Hooper Holmes Inc. Managed teams sized in excess of 50, cross functional and projects/products in excess of 15 million USD.
Srikanth has over 18 years of experience in Software Delivery Management, Project Management, design and architecture, development of software solutions, spanning high-transaction enterprise level applications to standalone product development. He has extensive exposure to successful Program/Project management techniques such as PMP and Prince2; Experience in various software development methodologies like ISV Product Lifecycle, traditional Waterfall, Agile (Scrum and DSDM).Extensive experience in Proposal Engineering – effort, schedule and pricing estimations using WBS, COCOMO, pre-sales and customer relations – specially in Off shoring model. Specialties: Proposal Engineering, Product Development, Client relationships, high complexity and visibility software delivery management, architecture and design.