Difference between revisions of "Bug Triage Extension"

From CDOT Wiki
Jump to: navigation, search
Line 37: Line 37:
 
*no much on the XMLRPC webservice api for bugzilla 2.23.3 but more is being added all the time. http://www.bugzilla.org/docs/tip/html/api/index.html
 
*no much on the XMLRPC webservice api for bugzilla 2.23.3 but more is being added all the time. http://www.bugzilla.org/docs/tip/html/api/index.html
 
*because of the bugzilla web services delays I have decided I can't wait any longer and am going to do what I can now.  This is try two at extension development. I've decided to post whatever I have at the end of every work session, this was only about an hour and a half while eating dinner but its a step in the right direction.
 
*because of the bugzilla web services delays I have decided I can't wait any longer and am going to do what I can now.  This is try two at extension development. I've decided to post whatever I have at the end of every work session, this was only about an hour and a half while eating dinner but its a step in the right direction.
 +
*I finally had more time to work on the extension again.  This release actually does something which is nice.
 +
**created build scripts for [http://cs1.senecac.on.ca/~b6001a07/build.sh linux]/[http://cs1.senecac.on.ca/~b6001a07/build.bat windows]
 +
**possible name:buggy bar
 +
**downloads top hottest bugs and displays them in a list
 +
**progress bar for refreshing list
 +
**designed screens and feature list
 +
**separated bugzilla facing code from GUI code to make future switch to web service based connections easier
 +
 +
I'm going to try and release as soon as possible again but this week is jammed with school work, I'm expecting to release again in a week.
 +
* I'm also taking name suggestions
  
 
==Extension Progress==
 
==Extension Progress==
 
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT.xpi ??/09/2006]
 
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT.xpi ??/09/2006]
 
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT2.xpi 01/11/2006] -> press shift + ctrl + b  
 
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT2.xpi 01/11/2006] -> press shift + ctrl + b  
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT3.xpi 02/11/2006] -> start firefox with console open(firefox -console) press shift + ctrl + b  
+
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT3.xpi 02/11/2006] -> start firefox with console open(firefox -console) press shift + ctrl + b
 +
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT4.xpi 02/11/2006] -> open the buggy bar under view -> sidebars
  
  

Revision as of 22:20, 19 November 2006

Project Name

Bug Triage Extension

Project Description

Mike Beltzner suggested this one after his talk. The idea is to make it trivial for testers to follow-through a bug's Steps To Reproduce (STR) so as to confirm it. A tester should be able to use this Extension to ask for a bug (i.e., one would be picked for him/her--no querying) and then a sidebar or similar would appear showing the steps to follow. Under that would need to be a way (e.g., buttons) to say that the bug is confirmed or not. Ideally the QA team could prioritize bugs so they appear in this list automatically, making it easier for testers to get the "right" bugs quickly.

Reference: talk to beltzner.

Project Leader(s)

Project Contributor(s)

Project Details

Project News

  • Spoke to robcee and jay on irc, and they are both interested in following this and helping out. Jay is going to be away until Oct 16. Contact him then. (dave)
  • Research time: lots of IRC talk, web searching, and such. Mostly XPCOM stuff and ways to handle the database connectivity, also a bit of java but I've put that idea aside. Looking for an existing XPCOM componet that can handle this.

I'm going to try and release as soon as possible again but this week is jammed with school work, I'm expecting to release again in a week.

  • I'm also taking name suggestions

Extension Progress


Project Resources