Guia para descrever erros

Erros efetivamente reportados são mais fáceis de corrigir. Este guia mostra como reportar de forma eficaz o erro.

Orientações iniciais

1. Faça seu software ser essencial.
   • Idealize, teste a versão em desenvolvimento para ver onde seu erro deve ser reparado. (e.g. Firefox Beta, Aurora, or bleeding-edge Nightly).
2. Search BugzillaPara ver se seu erro já foi bem reportado (tutorial).
3. Abra o class="link-https" href="https://bugzilla.mozilla.org/enter_bug.cgi?format=guided">Entre com o novo erro Formule, o que irá guia-lo na maior parte dos processos de reportar erros.
   • If you have multiple issues, please file separate bug reports.

Escrevendo passos precisos para reproduzir os erros

How can a developer reproduce the bug on his or her own computer?

Steps to reproduce are the most important part of any bug report. If a developer is able to reproduce the bug, the bug is very likely to be fixed. If the steps are unclear, it might not even be possible to know whether the bug has been fixed.

Describe your method of interacting with Firefox in addition to the intent of each step.

• Imprecise: "Open Gmail in another window".
• Precise: "Press Cmd+N to open a new browser window, then type https://mail.google.com/ in the address bar and press Enter".

After your steps, precisely describe the observed result and the expected result. Clearly separate facts (observations) from speculations.

• Imprecise: "It doesn't work"

• Precise: "Instead of showing my Inbox, it shows the message 'Your browser does not support cookies (error -91)'."

If the bug seems egregious, there might be something unusual about your setup that's a necessary part of the steps to reproduce the bug. See if you can reproduce the bug in a new Firefox profile. If the bug only happens in your existing profile, try to figure out what settings, extensions, or files in your profile are needed to reproduce the bug.

• What if my bug seems "random" or "intermittent"?

Escrevendo um resumo claro

How would you describe the bug using approximately 10 words? This is the first part of your bug report a triager or developer will see.

A good summary should quickly and uniquely identify a bug report. It should explain the problem, not your suggested solution.

• Good: "Cancelling a File Copy dialog crashes File Manager"
• Bad: "Software crashes"

• Good: "Down-arrow scrolling doesn't work in <textarea> styled with overflow:hidden"
• Bad: "Browser should work with my web site"

Encontrando o componente e produto correto

You will be asked to categorize your bug into a "product" and a "component" within that product, in order to direct your report to the correct developers.

If you're using Firefox, the bug is most likely in "Firefox", "Toolkit", or "Core".

• List of components in the "Firefox" product - Most parts of Firefox that you interact with directly
• List of components in the "Toolkit" product - Interface widgets and some frontend features
• List of components in the "Core" product - Web page rendering, networking, etc.

When in doubt, search for similar bugs and see what component they are in.

If none of the components seem appropriate, look for a "General" component in the most appropriate product.

Tipos específicos de erros

If you are reporting a crash bug, please include a Breakpad ID or attach stack trace, and include the crash signature in the bug summary.

If you are reporting a memory use or leak bug, please attach the output of about:memory (Firefox 6+). Ideally, find steps to reproduce an increase in what is shown in about:memory (even after clicking the "Minimize memory usage" button at the bottom). If you have trouble finding steps to reproduce, try the Firefox Support page titled High Memory Usage. If you are a C++ developer, more precise tools are available.

If you are reporting a bug involving a specific web page, please try to make a reduced testcase and attach it to the bug report.

If the bug was recently introduced, finding a regression window can help identify the cause of the bug.