If you don't select anything in the other 5 scrollboxes there, then you are saying that "any of these are OK" we're not locking ourselves into only finding bugs on the "DEC" Platform, or "Windows 95" OpSys (Operating System).Ģ. The default query for "Status" is to find all bugs that are NEW, ASSIGNED, or REOPENED, which is what we want. Do nothing in the boxes marked "Status", "Resolution", "Platform", "OpSys", "Priority", or "Severity". Ensure you are back on the "Bugzilla Query Page".
#Bugzilla tutorials how to#
Here is a example that how to make a few successful queries to find out what there are in the Bugzilla bug-tracking system itself.ġ.
Near the upper-left-hand corner of your browser window you should see the word "Status" underlined. The first thing you need to notice about the Bugzilla Query Page is that nearly every box you see on your screen has a hyperlink nearby, explaining what it is or what it does.
#Bugzilla tutorials Patch#
It is the master interface where you can find any bug report, comment, or patch currently in the Bugzilla system.
The Bugzilla Query Page is the heart and soul of the Bugzilla user experience. Voila! Select "Commit" and send in your bug report! Next we'll look at resolving bugs. Enter "The Bugzilla Guide" in the Summary text box, and place any comments you have on this tutorial, or the Guide in general, into the Description box. This way you don't end up sending copies of your bug to lots of other people, since it's just a test bug.Ĩ. Fill in the "Assigned To" box with the email address you provided earlier. If those are wrong, change them - if you're on an SGI box running IRIX, we want to know!ħ. Bugzilla should have made reasonable guesses, based upon your browser, for the "Platform" and "OS" drop-down boxes. The "reporter" should have been automatically filled out for you (or else Bugzilla prompted you to Log In again - you did keep the email with your username and password, didn't you?).Ħ. Now you should be at the "Enter Bug" form. Select the Enter a new bug report link.Ĥ. (Specific bugs have the added bonus of remaining relevant when an engineer actually gets to them in a rapidly changing web, a bug report of "foo.com crashes my browser" becomes meaningless after the site experiences a half-dozen redesigns and hundreds of content changes.)Ģ. If you're crashing on a site, please take the time to isolate what on the page is triggering the crash, and include it as an HTML snippet in the bug report if possible. The quicker the engineer can isolate the issue to a specific problem, the more likely it'll be expediently fixed. Every relevant detail you can provide helps. If an engineer can't see it or conclusively prove that it exists, the engineer will probably stamp it WORKSFORME or INVALID, and move on to the next bug. A useful bug report normally has two qualities: Useful bug reports are ones that get bugs fixed.
0 kommentar(er)
