hi friends..

can anybody share your experience in bugzilla???? with me...I am waiting for your reply

1.how effectively i can report bugs using bugzilla..

2.Suppose if i am testing a web page how can i find errors in the form using bugzilla..

3. Shall i use bugzilla for the brand new project???

Thanks
Deepasree

hi deepasree,

hope this link helps you Features :: Bugzilla :: bugzilla.org.

but as of my self experience, bugzilla is very user friendly and yes you can use bugzilla for a brand new project, but u need to have administrative right to set up the view.

Thanks
Sushma

hi friend..

will you please give a clear idea about bugzilla, the link specified is little bit confusing

my question is if i have a form and i have some fields too say like, text box, radio button, search button and next link to navigate another form.. now tell me how bugzilla reports error to me.. explain with an example..

bugzilla has the capability to check database???? it is so then how???? will bugzilla fetch the information from Databse????

I need to know where to start... is bugzilla similar to QTP??? will it record the application and test application or else what??I want to know the entire procedure.. I have n number of questions from my mind..

Thanks
Deepasree

hi deepasree,

I have worked with Bugzilla only to to raise defects, as far as i know it is not used for caputure and playback. so, if oyu want to know the procedure of taht i can explain you in detail.

Correct me if i am wrong, but it is not an automated tool.

Thanks
Sushma

hi friend..

please explain me how to raise defect...step by step... if possible with example.. waiting for your reply...

Thanks
Deepasree

hi deepasree,

The procedure for filing a bug is as follows:
1. Click the “New” link available in the footer of pages, or the “Enter a new bug report” link displayed on the homepage of the Bugzilla installation.
2. You first have to select the product in which you found a bug.
3. You now see a form where you can specify the component (part of the product which is affected by the bug you discovered; if you have no idea, just select “General” if such a component exists), the version of the program you were using, the Operating System and platform your program is running on and the severity of the bug (if the bug
you found crashes the program, it’s probably a major or a critical bug; if it’s a typo somewhere, that’s something pretty minor; if it’s something you would like to see implemented, then that’s an enhancement).
4. You now have to give a short but descriptive summary of the bug you found. “My program is crashing all the time” is a very poor summary and doesn’t help developers at all. Try something more meaningful or your bug will probably be ignored due to a lack of precision. The next step is to give a very detailed list of steps to reproduce
the problem you encountered. Try to limit these steps to a minimum set required to reproduce the problem. This will make the life of developers easier, and the probability that they consider your bug in a reasonable timeframe
will be much higher.
Note: Try to make sure that everything in the summary is also in the first comment. Summaries are often updated and this will ensure your original information is easily accessible.
5. As you file the bug, you can also attach a document (testcase, patch, or screenshot of the problem).
7. Now is a good time to read your bug report again. Remove all misspellings, otherwise your bug may not be found by developers running queries for some specific words, and so your bug would not get any attention. Also make sure you didn’t forget any important information developers should know in order to reproduce the problem, and
make sure your description of the problem is explicit and clear enough. When you think your bug report is ready to go, the last step is to click the “Commit” button to add your report into the database.
You do not need to put "any" or similar strings in the URL field. If there is no specific URL associated with the bug, leave this field blank.

hope my answer my answer is clear. please let me know if you have any queries. Actually i worked with it in my past company, at present i use Lotus Notes.

Thanks
Sushma

hi friend

You mean whatever the bug is filed by us will report to the developer immediately how...

i have to identify bug manually and just i have to tell the developer through bugilla and then they will identify that particluar bug and fix.. is this the process

thanks
Deepasree

hi,

yes whatever bug that has been raised by us will be assigned to teh developer, because there will be a dropdown list , from where you can select the Lead Developer and assign it to them, then its upto hom whether he will fix it or he will assign it to another developer, that is how it works.

you can setup a filter search and find if there is a exsisting bug, if so you can just assign it to the developer.

Thanks
Sushma

hi friend..

oh i see.. bugzilla acts as a centralized data to mingle developer and tester through . i can just find errors manually and update it through bugzilla..i can't find bugs through bugzilla am i right..

Thanks
Deepasree

hi,

Well, bugzilla can be used with QTP, but i am not sure how use it, as i haven't used bugzilla with QTP, i have used iot manually, i shared my experience with you, i.e manually how you raise defect and how it can be assigned to developers etc. I cannot really say anything about automation as i am not into automation.

Thanks
Sushma

hi friend..

ok fine then... Another question from my side whether we can raise bugs through bugzilla for all the applications i mean .. windows, web and other domains

I want to know whether this is correct "bugzilla acts as a centralized data to mingle developer and tester in a common area.. so that we can track the bug is fixed or not..

Thanks
Deepasree

hi,

yes, we can raise bugs regarding all the applications under the respective header, i mean for ex: if you are testing X application which belongs to Y project and you find a issue, then you raise the issue for X application under project Y, you can do that only if Project Y is created in Bugzilla, and you need administrative rights to do so, usually it will be created by managers like Project Manager/Development Manager/Tema leader etc.

yes, we can trach the status of bug through bugzilla.

Thanks
Sushma

hi friend..

ok i got it ..

Thanks
Deepasree

hi,

not a problem, it was a nice question, really made me to think how i used it. Keep posting such questions

Thanks
Sushma

hi friend

ok fine ..

Thanks
Deepasree

hi,

do you use bugzilla for raising defects???

Thanks
Sushma

hi friend..

I am not using Bugzilla for raising defects???? i want to know the technology behind it...

Thanks
Deepasree

hi,

ok not a problem. Is there anyone else who is using Bugzilla............ please share your experience

Thanks
Sushma

Hi Deepasree,

As Sushma said Bugzilla is a bug tracking (defect tracking) tool. It's similar to FogBugz, and TeamTrack. There will be one administrator who takes care of assigning the issues to different people. In QC and TD, we directly assign the issues to developers and cc them to managers, whereas in these tools the administrator assigns the issue to the manager. After his acknowledgement the administrator assigns it to the developer, and it goes like that. Lot of steps and very structured, I would say. In my company, the clients use Bugzilla. We (Testers) use Quality Center.

Let me know, if you need more specific information.

Thanks,
Bavani.