Difference between revisions of "Bug Triage Extension"

From CDOT Wiki
Jump to: navigation, search
Line 47: Line 47:
 
*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 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 looking for better name and a logo if anyone wants an easy way contribute.  If I use it I'll add you.
 
*I'm also looking for better name and a logo if anyone wants an easy way contribute.  If I use it I'll add you.
 +
*I pushed back my other work and got another update in before the busy week started. I started adding the preferences as well as started the view bug specs feature.
  
 
==Extension Progress==
 
==Extension Progress==
Line 53: Line 54:
 
*[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
 
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT4.xpi 02/11/2006] -> open the buggy bar under view -> sidebars
 +
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT5.xpi 02/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar.bmp screen shot]
 +
 +
==To Do==
 +
*create user preferences feature
 +
*switch html special character back to original character
 +
*view bug specs feature
 +
**steps to reproduce
 +
**summary
 +
**etc
 +
*login to bugzilla feature
 +
*control bug list search parameters
 +
 +
*finish to do list
 +
*allow for multiple searches/bugzilla instances
  
  

Revision as of 22:45, 20 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 looking for better name and a logo if anyone wants an easy way contribute. If I use it I'll add you.
  • I pushed back my other work and got another update in before the busy week started. I started adding the preferences as well as started the view bug specs feature.

Extension Progress

To Do

  • create user preferences feature
  • switch html special character back to original character
  • view bug specs feature
    • steps to reproduce
    • summary
    • etc
  • login to bugzilla feature
  • control bug list search parameters
  • finish to do list
  • allow for multiple searches/bugzilla instances


Project Resources