From 33058f2b292b3a581333bdfb21b8f671898c5060 Mon Sep 17 00:00:00 2001 From: Peter Bengtsson Date: Tue, 8 Dec 2020 14:40:17 -0500 Subject: initial commit --- .../bug_writing_guidelines/index.html" | 366 +++++++++++++++++++++ 1 file changed, 366 insertions(+) create mode 100644 "files/zh-cn/\350\264\250\351\207\217\344\277\235\350\257\201/bug_writing_guidelines/index.html" (limited to 'files/zh-cn/质量保证/bug_writing_guidelines/index.html') diff --git "a/files/zh-cn/\350\264\250\351\207\217\344\277\235\350\257\201/bug_writing_guidelines/index.html" "b/files/zh-cn/\350\264\250\351\207\217\344\277\235\350\257\201/bug_writing_guidelines/index.html" new file mode 100644 index 0000000000..a170bb1bfc --- /dev/null +++ "b/files/zh-cn/\350\264\250\351\207\217\344\277\235\350\257\201/bug_writing_guidelines/index.html" @@ -0,0 +1,366 @@ +--- +title: Bug 提交指南 +slug: 质量保证/Bug_writing_guidelines +tags: + - Bugzilla + - 可能过时 + - 问答 +translation_of: Mozilla/QA/Bug_writing_guidelines +--- +
+

This page needs a technical review from the Mozilla QA Team in Q4 2014. (Assigned to Ioana Chiorean.) The following articles have been merged into this page from QMO:

+ + + +

If you need help with Mozilla software (for example with Firefox or Thunderbird), use one of the available support options. Do not edit this page! Please read this page to learn how to report a bug using Bugzilla, which is Mozilla's bug tracking system.

+ +

If you're new to reporting bugs, you may want to try getting help from the more experienced contributors. See the Community section on the QA page for pointers. If you're going to report a Firefox bug, you can also get assistance in the #firefox channel on irc.mozilla.org.

+
+ +

有效的问题报告会最可能得到处理。这份指南则阐释了如何来写出这样的报告。

+ +

准备

+ +
    +
  1. 请确保你的软件是更新到最新的 +
      +
    • 理想情况下，请测试一个正在开发中的版本来看你所提交的问题是否已经处理掉。 (例如 Firefox Beta, Aurora, 或者 bleeding-edge Nightly).
      • +
    +
    2. +
  2. 在 Bugzilla 上搜索，看看你的问题是否已经被提交。(教程).
    3. +
  3. 点击 输入一个新bug  表单，它就会指引你来完成绝大部分问题报告过程。如果你有多个问题需要报告， 请对每个问题分别提交一个问题报告。
    4. +
+ +

写出清楚而准确的步骤来复现问题

+ +

开发者怎样可以在他的设备上复现这个问题？

+ +

复现问题的步骤是问题报告中最重要的部分。如何开发者可以重现这个问题， 这个问题就可能得到处理。 如果复现问题的步骤不清晰， 我们就不会知道这个问题是否已经被处理。 

+ +

除了与每个步骤交互的意图外，尽量精确的描述出与 Firefox 交互的方法。

+ + + +

在下面的步骤后，准确描述观察的结果和预期结果。明确区分实时（观察现象）和推测。

+ + + +

如果这个bug看起来非常严重，那么您的设置可能有一些不正常的地方，这是重现该bug的必要步骤之一。看看您是否可以在新的Firefox配置文件中重现此错误。如果错误只发生在您现有的概要文件中，请尝试找出重现错误需要哪些设置、扩展名或概要文件。

+ + + +

写出一个简洁的标题

+ +

怎样用尽量少的字来描述一个Bug? 这是开发人员将在你的反馈报告中看到的第一部分。

+ +

好的标题将会在众多反馈中被迅速区分开。它应该是报告一个问题, 而不是建议的解决方案。

+ +

下面有一些范例：

+ + + + + +

查找出准确的 product 和 component分类

+ +

你需要将你提交的问题分类到product和component, 来确保你提交的问题报告被相关的开发人员看到。

+ +

如果你正在使用 Firefox，问题很可能出在 "Firefox", "Toolkit"或"Core"中。

+ + + +

如果有疑问，请搜索类似的错误并查看它们所在的分类。

+ +

如果看起来以上的分类都不合适，那么在最合适的分类中寻找一个“通用”组件。

+ +

指定 bug 的类型

+ +

如果您正在报告一个崩溃错误，请包含一个Breakpad ID或附加堆栈跟踪，并在错误摘要中包含崩溃签名。如果您正在报告内存使用或溢出bug，请附上about:memory (Firefox 6+)的输出。理想情况下，找到一些步骤来重现在about:memory中显示的增长(即使在单击底部的“最小化内存使用”按钮之后)。如果您难以找到复制步骤，请尝试Firefox支持页面“高内存使用量”。如果您是c++开发人员，可以使用更精确的工具。

+ +
+

原始文档信息

+ + +
+ +
+
+

下面的文章源自QMO: 如何合适地报告bug

+
+ +

检查bug是否有效

+ +

验证您发现的问题是一个新bug

+ +

要验证您所发现的是否确实是Mozilla产品中的一个新bug，请查看下面的检查方法，以确保值得为其创建一个新的bug报告。

+ + + +

如果你不知道该做什么，看看irc频道的问答。如果没人回答，就看看或把问题发到bugzilla论坛。如果仍然没人回答再编写bug报告。

+ +

Bug报告

+ +

怎么创建一个bug报告？

+ + + +

在哪个社区可以发布bug报告？

+ +

在创建错误时，应该考虑几个原则。 比如：

+ +

     保持描述和摘要清晰简洁

+ +

     仅报告错误报告中的一个问题

+ +

     仅报告您的错误中的事实并删除您可能拥有的任何假设

+ +

bug报告的概要

+ + + +

继续阅读 How to Write a Proper Bug Report Part 2

+ +
+

Original document information

+ + +
+ +
+
+

The following article has been merged into this page from QMO: How to write a proper bug - Part 2

+
+ +

Reporting and Writing Good Bugs

+ +

By Tyler Downer

+ +

Contents

+ + + +
    +
  1. Thank You
    2. +
  2. Read for all bugs
    3. +
  3. Choose Your Issue
    4. +
  4. Using Bugzilla
    5. +
  5. Related Information
    6. +
+ + + +

Thank You!

+ +

So, you think have found a bug in Firefox and you want to report it to be fixed. Great and thank you. The Mozilla projects rely on users to find and report bugs. However, you need to make sure that you write a good bug report on Bugzilla (bugzilla.mozilla.org) in order for it to be useful. These guidelines will help you write a good bug.

+ +

Note: These instructions are written for Firefox, but similar ones apply for most Thunderbird and Seamonkey bugs, only details differ. Hopefully, a Thunderbird version of this page will be released with Thunderbird 3.

+ +

IMPORTANT

+ +

Please read For All Bugs thoroughly before going to your specific issue. The information contained there is critical to making sure your issue is with Firefox, and not with an extension or corruption in your profile.

+ +

For all Bugs

+ +

No matter what type of bug you have found, make sure to follow these steps to confirm that it is a bug in a Firefox, and not an extension. To do that, follow these steps:

+ +
    +
  1. Update Firefox, add-ons and plugins to the most recent versions (this includes programs like Flash and Acrobat Reader). All of your plugins must be on the latest supported version, as well as Firefox. NOTE:Firefox 2 is no longer supported, and support for Firefox 3 will end by the end of the year. Please update to Firefox 3.5.
    2. +
  2. Start Firefox in Safe Mode and try to find the bug. If the issue goes away: +
      +
    1. Disable your extensions/themes one by one, until you find the one causing the issue.
      2. +
    2. Contact the developer of that extension.
      3. +
    3. Read below for more information on Extensions.
      4. +
    +
    3. +
  3. If the issue is still there in Safe Mode, make a new profile with no extensions or changes (instructions here). Then try to find the problem. If the issue goes away, your Firefox install was most likely corrupted. Migrate your bookmarks and other information to this new profile, and you should be good to go.
    4. +
  4. You can read Basic Troubleshooting for more steps to try.
    5. +
  5. If the issue is still present after these steps, it is likely your problem is with Firefox. However, make sure to go to support.mozilla.com and search for your issue there. Many problems can be solved with simple end-user support steps, and do not need to be reported as bugs. If you can not find any information to help on Mozilla support, keep reading to make sure your issue is really a bug, and to write a good helpful bug report.
    6. +
  6. One thing to help developers is to use the latest nightly development build. These are the absolute latest in development on the Firefox program and help developers know if the issue has already been fixed. Also, if a patch is written, it will be put in the trunk first, making it easy to test. You can find trunk builds at the Mozilla FTP site.
    7. +
+ +

Extensions, Themes and Other Applications

+ +

If you are experiencing a problem with an add-on, plugin, or other programs, please follow these steps:

+ +
    +
  1. Update to the latest version. You can use Firefox's handy Add-on update manager to update extensions and themes. Some plugins and outside applications will have to be updated internally or manually from their website. It is very important that you are always using the latest version of plugins like Adobe Acrobat Reader, Flash Player, Real Player, VideoLAN and the like.
    2. +
  2. Read troubleshooting extensions and themes for more information.
    3. +
  3. If the problem lies with the extension (this can be proved using the steps listed for all bugs), then you should contact the developer of the extension or other application. Mozilla can not fix someone else's program for them.
    4. +
  4. If the issue lies with how Firefox uses the extension, the go ahead and report it to both Mozilla and the extension developer.
    5. +
+ +

Choose your Issue

+ +

After reading the information for All bugs above, choose your issue below.

+ + + +
    +
  1. Crash
    2. +
  2. Enhancement
    3. +
  3. Internet Connectivity Issue
    4. +
  4. Memory Leak
    5. +
  5. Performance Issue
    6. +
  6. Regression
    7. +
  7. Webpage
    8. +
  8. Window Shakes
    9. +
  9. For Bugs Not Listed
    10. +
+ + + +

崩溃

+ +

If Firefox crashes, and you have already followed the steps for all bugs above, fill out a bug report with the following information:

+ +
    +
  1. Try to reproduce the bug (what you did to make the crash occur). If possible, try to reproduce it on different computers with the same version of Firefox, and with the current nightly development build of Firefox.
    2. +
  2. Make sure you turn on the crash reporter, and provide the crash ids with your bug report (those can be found by typing about:crashes in your URL bar and copying the appropriate number).
    3. +
  3. Make sure to read how to get a stacktrace and more information that is important for developers.
    4. +
  4. Now that you have all this information, create a bug with a severity of Critical. Give as much information as possible.
    5. +
+ +

Enhancement

+ +

When you would like a feature added to Firefox, it is called an Enhancement and the severity is marked as such. To file a good enhancement request, simply follow these two steps:

+ +
    +
  1. Make sure you have explored all possible settings and other areas of Firefox to confirm that what you want does not already exist.
    2. +
  2. Give a clear description on what, where and how this should be changed. Give the dialog box to be improved, maybe even a screenshot if it is a little known feature or it would assist in understanding. Remember, there are many areas of Firefox, so don't be offended if the Triage team asks for more details or why this should be added.
    3. +
+ +

Internet Connectivity Issue

+ +

If you are having issues connecting to the Internet, it is most likely not an issue with Firefox, but an incorrectly set up Firewall. Make sure your Internet settings are set up correctly, and follow the steps listed for all bugs, then search the Firefox Support site. They will let you know if it is something you should report on Bugzilla or not.

+ +

Memory Leak

+ +

Memory Leaks are very difficult to diagnose, so make sure the issue is not with your machine. Then provide the following information:

+ +
    +
  1. Detailed information on your machine, what is happening when the leak occurs, and what seems to cause it.
    2. +
  2. Read the following information found on David Barron's blog (Part 1, Part 2)and the Mozilla Developer Center on writing good memory leak bugs.
    3. +
+ +

Performance Issue (High CPU use, hard drive use, etc)

+ +

Performance issues are also difficult to confirm and diagnose. The only real way to confirm them is to have a website (create a testcase, read here for more info) that we can use to confirm on any similar machine. Please try to test on at least one other machine of the same or similar configuration before reporting. Also, issues such as startup times are almost impossible to confirm and can be influenced by other factors, so please make a strong case before submitting. Developers are always working on performance, so your problem may be fixed in the next release of Firefox.

+ +

Regression

+ +

If a bug has just recently occurred in Firefox that was not there before and is caused by an update, it is a regression. These usually only happen on the Trunk builds, though occasionally they creep onto the Releases. To properly report a regression:

+ +
    +
  1. Follow the steps listed for all bugs. Also, make sure you did not make a change recently to the settings or something else that could have caused this.
    2. +
  2. Install an older version of Firefox (starting with the most recent) to find out where the bug crept in. When you find it, then file that information.
    3. +
+ +

Webpage Displaying Incorrectly

+ +

Make sure that the issue you are seeing is a Firefox problem, and easy way to do this is follow these steps:

+ +
    +
  1. Test in another browser such as Internet Explorer, Opera or Safari. If the issue is still there, it is probably something wrong with the website and they should be contacted.
    2. +
  2. Follow the steps for all bugs. Extensions can mess with the rendering of a website, especially audio and video.
    3. +
  3. Try to reproduce the issue on another computer running Firefox. You can also adjust your screen resolution to see if that is causing the issue.
    4. +
  4. Try contacting the webmaster in charge of the website. Inform them of the problem, and ask if they know what could be causing it (some sites only work with certain browsers).
    5. +
  5. Finally, if the issue is still there, make a testcase that shows in the bare minimum what the problem it. Information on how to can be found here.
    6. +
+ +

窗口抖动

+ +

If you Firefox window begins to shake, vibrate, or move around without any action on your part, it is usually fixed easily by reading these webpages:

+ +
    +
  1. Follow the steps for all bugs. Extensions can cause window shakes.
    2. +
  2. Read this support document, Window Shakes.
    3. +
+ +

对于没有列出的问题

+ +

If the issue you are experiencing does not fall into these specific categories, follow the steps for all bugs, then write a clear, concise bug report. Make sure you eliminate any unnecessary information that could distract from the bug itself, and give a detailed steps to reproduce with all the information you think is necessary. Remember, no bug is too little to report and it will never get fixed unless it it reported.

+ +

使用Bugzilla

+ +

Now that you have followed all these steps, found that your problem is with Firefox, and gathered the proper information, you can submit to bugzilla. When you submit a bug, make sure you read Bug Filing Guidelines. This provides basic information to make sure you fill the bug out completely Also, read the Etiquette and Privacy Policy. Before filing any bug, make sure to search thoroughly for any duplicates of the same issue. Keep your bug reports down to only one issue per bug report, it may be closed because of too many issues in one report.

+ +

相关信息

+ +

You can visit the following pages for more information on bug reports and good related resources:

+ + + +
    +
  1. Bug Writing Guidelines
    2. +
  2. Mozilla Support
    3. +
  3. Mozilla Developer Center
    4. +
  4. Firefox Trunk builds
    5. +
  5. Bugzilla
    6. +
+ + + +

返回顶部

+ +
+

Original document information

+ + +
-- cgit v1.2.3-54-g00ecf