Dashboard > Selenium Remote Control > Home > Bug Triage HOWTO
Selenium Remote Control Log In View a printable version of the current page.
Bug Triage HOWTO
Added by Dan Fabulich, last edited by Dan Fabulich on Mar 17, 2008
Labels: 
(None)

These are directions for how to triage bugs in the OpenQA JIRA.

The responsibilities of a triager, IMO:

  • Go through every bug (even the old ones) and attempt to reproduce them.
  • If the issue reproduces, assign it a "Fix Version." Create new Fix Versions if necessary. (1.1, 2.0, Future) If you think we need to fix it before we release 1.0, then assign it Fix Version 1.0.
  • If not enough information is available to reproduce, just Close the issue with the Resolution "Incomplete." Make sure that you REMOVE the Fix Version from bugs marked "Incomplete."
  • For every issue marked "Incomplete," be sure to specify exactly what information you do need, e.g. "provide an example HTML page and an HTML Selenese test", or "a publicly available website that exercises that feature", log files, etc. In RC, you can also suggest trying to reproduce the problem using -interactive mode.
  • If you have enough information, but the bug doesn't reproduce, then Close the issue with the Resolution "Not Reproducible." Again, make sure that you REMOVE the Fix Version from any bug marked "Not Reproducible."
  • Do not mark the bug "Fixed" unless you are saying that you, yourself, just fixed that bug (in which case you should specify a revision number). If you think the bug must have been fixed in the past, then just mark it "Not Reproducible".

Site running on a free Atlassian Confluence Community License granted to OpenQA. Evaluate Confluence today.
Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.5.6 Build:#812 Aug 06, 2007) - Bug/feature request - Contact Administrators