Geeks With Blogs

News

Google My Blog


Murray Gordon Flash a-ah! Savior of the universe...

Bug Priority Levels:

 

Priority 1

If any of the cases true, then it’s a Priority 1 Otherwise, it’s a Priority 2

  • The tool hangs or crashes
  • Memory Leaks in working process/GC Handles
  • Data loss of any kind
  • Urgent issue that must be fixed right away (could be because of client priority/request)

 

Priority 2

If any of the cases true, then it’s a Priority 2 Otherwise, it’s a Priority 3

  • When a functionality or feature is broken, results or behavior contradicts with logically expected results and there is no work around available
  • Missing functionality
  • Bad user experience or interface issue
  • Poor performance with unacceptable response times

 

Priority 3

If any of the cases true, then it’s a Priority 3 Otherwise, it’s a Priority 4

  • When a functionality or feature is broken, results or behavior contradicts with logically expected results and there is a work around available.
  • Bug does not cause a bad user experience.
  • Bug does not block a good number of other test Cases

 

Priority 4

  • Cosmetic
  • Future item – something we’ve agreed needs to be done, but is of lowest priority

 

Priority 5

  • Suggestion/Question
  • Use if you are unsure if item is a bug or an enhancement
  • Items we have not agreed to do as yet – evaluation is required

 

If anyone has different thoughts on this, please let me know.

 

Thanks,

Murray

Posted on Monday, October 2, 2006 11:26 AM General | Back to top


Comments on this post: Thoughts on Bug Priority Levels

No comments posted yet.
Your comment:
 (will show your gravatar)


Copyright © Murray Gordon | Powered by: GeeksWithBlogs.net