Difference between revisions of "Bug Triage Extension"

From CDOT Wiki
Jump to: navigation, search
Line 51: Line 51:
 
* new version is getting closer, right now the preferences is set up pretty good but they have to be manually changed.  You can alter the rows of each bug to view, and the bugzilla instance to hit in the preferences.
 
* new version is getting closer, right now the preferences is set up pretty good but they have to be manually changed.  You can alter the rows of each bug to view, and the bugzilla instance to hit in the preferences.
 
* new version fixes some html parsing problems, adds two new features: the view bug page button and the send email button.
 
* new version fixes some html parsing problems, adds two new features: the view bug page button and the send email button.
 +
preferences added, and search and better html tag stripping
  
 
==Extension Progress==
 
==Extension Progress==
Line 60: Line 61:
 
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT7.xpi 28/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar-7.bmp screen shot]  
 
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT7.xpi 28/11/2006] -> [http://cs1.senecac.on.ca/~b6001a07/buggyBar-7.bmp screen shot]  
 
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT8.xpi 28/11/2006]
 
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT8.xpi 28/11/2006]
 +
*[http://cs1.senecac.on.ca/~b6001a07/inveigleEXT9.xpi 29/11/2006]
  
 
==To Do==
 
==To Do==

Revision as of 13:14, 29 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.
  • new version more features
  • new version is getting closer, right now the preferences is set up pretty good but they have to be manually changed. You can alter the rows of each bug to view, and the bugzilla instance to hit in the preferences.
  • new version fixes some html parsing problems, adds two new features: the view bug page button and the send email button.

preferences added, and search and better html tag stripping

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