Difference between revisions of "IS480 Team wiki: 2011T1 TheTalkies Bug Tracker"
Jump to navigation
Jump to search
Mtaung.2008 (talk | contribs) |
|||
Line 1: | Line 1: | ||
+ | Goals: | ||
+ | * To keep track of unsolved bugs | ||
+ | * To ensure quality of the Web Application | ||
+ | * To let the team knows which function has more bugs. | ||
+ | |||
<b>Severity Level</b> | <b>Severity Level</b> | ||
<br/><br/> | <br/><br/> | ||
Line 4: | Line 9: | ||
In our bug tracker sheet, we assign each bug with its calculated severity level so that the debugger knows which bugs is more urgent to be solved so that it will not affect the other features. | In our bug tracker sheet, we assign each bug with its calculated severity level so that the debugger knows which bugs is more urgent to be solved so that it will not affect the other features. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
<b>Bug Tracker</b> | <b>Bug Tracker</b> |
Revision as of 17:25, 21 November 2011
Goals:
- To keep track of unsolved bugs
- To ensure quality of the Web Application
- To let the team knows which function has more bugs.
In our bug tracker sheet, we assign each bug with its calculated severity level so that the debugger knows which bugs is more urgent to be solved so that it will not affect the other features.
Bug Tracker
In the graph, we show how many bugs found in a particular iteration and how many bugs fixed in which iteration. For some bugs, we could not solve in the assigned iteration. Later iteration, therefore, the number of bugs fixed is higher than the number of bugs found. For example, in iteration 3, actually bugs found is only 2 but because of the leftover bugs from iteration 2 we have to solve 3 bugs instead.