User:Sardisson/Crash Analysis UI - Revision history

Sardisson: /* Topcrash reports */ one more

2007-04-04T07:09:11Z

Topcrash reports: one more

Sardisson: /* Search UI */ one more again

2007-03-15T23:39:50Z

Search UI: one more again

Sardisson: /* Results Page */ one more

2007-03-15T23:32:29Z

Results Page: one more

Sardisson: s/server/webtool/

2007-03-15T23:15:05Z

s/server/webtool/

Sardisson: some issues

2007-03-15T23:08:15Z

some issues

New page

Right now, mozilla.org uses Talkback for its crash reporting, and http://talkback-public.mozilla.org for access to/analysis of the crash reports that are sent in. Unfortunately, this server UI has a number of annoying limitations. As QA lead for Camino, I run into them often :(

Hopefully the future mozilla.org [http://code.google.com/p/google-breakpad breakpad] report server will be able to handle some of these issues in a better fashion.

==Search UI==
* No way to select "all products on this branch" to run a single query
*: ''e.g., to see if Camino and Firefox both crash in a certain function/stack on Mac OS X on the 1.8 branch and generate a list of incidents for mining urls and comments''
* The "Start Date" and "End Date" fields are grouped underneath the "build selectors" menus, but they are for the '''date of the crash, not the date of the build''' (confusing UI)
* There is no way to search for crashes occurring in '''builds''' produced within a certain range
*: ''e.g., there was a big crasher, you fixed it, but some reports with the same stacks are still showing up. You want to get those reports but only for builds after your fix. Right now you have to either construct separate queries for each build (and for each stack, if a crash had two or more signatures), or take the general query for the stack(s) and weed out the builds that don't match''
* No "now" option in the date field, so you always have to fill in a future date if you want to bookmark a by-date query (all crashes with this stack since date ''foo'')
* Date order is opposite of Bonsai and uses different separators, so you can't copy/paste from one to the other when trying to find checkins given a regression range you've gleaned from Talkback

==Results Page==
* Existing query is not pre-filled/preserved when a results page is generated
*: ''e.g., to allow for easy modification of a query for slightly different inputs''
* No way to sort a results page other than editing the url or going back and re-running the query

==Topcrash reports==
* Only shows one open and one fixed bug per stack
* Doesn't always find Camino bugs when trying to match bugs to stacks
* See also [http://wiki.mozilla.org/Talk:Mozilla_QA_Community:Talkback_Report_Challenge_1 Jesse Ruderman's list] of desired Topcrash report improvements
*: ''most of which are more relevant for Fx/Core, but the "help me reproduce" report would be very helpful''

← Older revision		Revision as of 07:09, 4 April 2007
Line 25:		Line 25:
	* See also [http://wiki.mozilla.org/Talk:Mozilla_QA_Community:Talkback_Report_Challenge_1 Jesse Ruderman's list] of desired Topcrash report improvements		* See also [http://wiki.mozilla.org/Talk:Mozilla_QA_Community:Talkback_Report_Challenge_1 Jesse Ruderman's list] of desired Topcrash report improvements
	*: ''most of which are more relevant for Fx/Core, but the "help me reproduce" report would be very helpful''		*: ''most of which are more relevant for Fx/Core, but the "help me reproduce" report would be very helpful''
		+	* Clicking on the number in the date column would pull up a query returning just those results (i.e., just that build's crashes for that particular stack)

@@ Line 6: / Line 6: @@
 * No way to select "all products on this branch" to run a single query
 *: ''e.g., to see if Camino and Firefox both crash in a certain function/stack on Mac OS X on the 1.8 branch and generate a list of incidents for mining urls and comments''
 * The "Start Date" and "End Date" fields are grouped underneath the "build selectors" menus, but they are for the '''date of the crash, not the date of the build''' (confusing UI)
 * There is no way to search for crashes occurring in '''builds''' produced within a certain range

@@ Line 16: / Line 16: @@
 *: ''e.g., to allow for easy modification of a query for slightly different inputs''
 * No way to sort a results page other than editing the url or going back and re-running the query
 ==Topcrash reports==

@@ Line 1: / Line 1: @@
-Right now, mozilla.org uses Talkback for its crash reporting, and http://talkback-public.mozilla.org for access to/analysis of the crash reports that are sent in.  Unfortunately, this server UI has a number of annoying limitations.  As QA lead for Camino, I run into them often :(
+Right now, mozilla.org uses Talkback for its crash reporting and http://talkback-public.mozilla.org for access to/analysis of the crash reports that are sent in.  Unfortunately, this webtool UI has a number of annoying limitations.  As QA lead for Camino, I run into them often :(
-Hopefully the future mozilla.org [http://code.google.com/p/google-breakpad breakpad] report server will be able to handle some of these issues in a better fashion.
+Hopefully the future mozilla.org [http://code.google.com/p/google-breakpad breakpad] report webtool will be able to handle some of these issues in a better fashion.
 ==Search UI==