84
edits
QA/Talkback/Topcrash Analysis: Difference between revisions
m
initial outline
(initial checkin) |
m (initial outline) |
||
| Line 1: | Line 1: | ||
=Talkback | ==Introduction== | ||
How often does Firefox or Thunderbird crash? In what particular features (or which tasks) do we see frequent crashes? Talkback, our crash reporting tool, can show us data to help answer these questions. | |||
Publically accessible Talkback database: http://talkback-public.mozilla.org/talkback/fastfind.jsp | |||
===What needs to be done?=== | |||
Mozilla QA periodically analyzes the Talkback data to see if new topcrash bugs need filing (and ultimately developer attention). Ideally this would occur on a regular basis: | |||
* For the trunk products (Firefox and Thunderbird), check Talkback data approximately 3x a week. | |||
* For branch Firefox and Thunderbird products, check Talkback during the candidate process and immediately after release. Then about once or twice a month thereafter. | |||
* For branch (1.7.x) Mozilla, , check Talkback immediately after release. Then about once or twice a month thereafter. | |||
==How to view topcrash reports== | |||
# Go to http://talkback-public.mozilla.org/reports/ | |||
# Click on the product (firefox, thunderbird, mozilla, camino) | |||
# Choose the branch, trunk, release, etc. from the links under these three or two columns: | |||
#* Development: trunk builds are here | |||
#* Major releases (ffox and tbird only): 1.0, 1.0.x, etc. | |||
#* Milestone releases (also includes final mozilla releases) | |||
#* Beta releases (mozilla and camino only) | |||
# in the left side, a list of the reports available should appear, such as: | |||
#* Topcrashers by Build: this is the main report we'll start with | |||
#* Simple Reports: this groups crashes by signature, and skimming this helps with getting additional comments/feedback. | |||
#* Smart Analysis: also grouped by signature, but also lists bug number info (where available). | |||
# You can add info found here to new topcrash bugs we file, especially if it helps with finding a reproducible test. note that you should skim first to see that there's no sensitive data there (eg, user accidentally typed in a passwd!) and remove that before pasting into a bug report. | |||
==How to file a topcrash bug== | |||
# | |||
# | |||