tfs2012 - How to propose improvements in current bug tracking process? -


i have noticed problems in our current bug tracking process (tfs2012)

a) inconsistency in raising bugs b) inconsistency in logging bugs c) inconsistency in bug resolution d) difficult apply filters due less filters , meaningful values. e) bug reports virtually impossible create due lack of training tfs.

how propose change management thier consideration.

welcome @ron12345!

this big question have asked here, let me see if can break manageable chunks (flagrantly stolen original post, no less!):

inconsistency in raising bugs - mean this? in mind's eye presume mean bugs aren't being written/brought up? if case, can gotten around using simple axiom (that use myself) - "if have ask, 'is bug?', likely, is. it's mental paradigm-shift testers realize bug is, record of went awry or improved.

inconsistency in logging bugs - this, use very simple , formulaic approach:

<brief bug description>  1. repro 2. steps 3. go 4. here  actual:  happening.  expected:  expected behavior supposed be.  (as aside, try avoid using words 'should' here).  <this make note of attachments go along bug.>

we break our bugs down component in found, sprint found , note team need make fix.

inconsistency in bug resolution - use following @ current job resolution status:

active - bug new, , has not been reviewed anyone.

in progress - developer has moved bug queue , reviewing it.

resolved - bug has been fixed , re-assigned person reported it.

as designed - may bug but, resolved code changes or not require fix because of other factors updates design other teams.

cannot reproduce - developer unable reproduce issue, , bug may need more information or better repro steps.

closed - don't think needs explanation :)

difficult apply filters due less filters , meaningful values - problem can solved creating more effective filters within tfs search on. if agile shop, consider adding field allows filter sprint, example.

bug reports virtually impossible create due lack of training tfs - found this article on creating reports in tfs.

best of luck , project team/and hope answer useful you!


Comments

Post a Comment

Popular posts from this blog

c# - Operator '==' incompatible with operand types 'Guid' and 'Guid' using DynamicExpression.ParseLambda<T, bool> -

i'm using dynamic linq library , there source code , basic docu , nuget version pm> install-package dynamiclinq i'm trying construct clause involves guids i have tried string "id == @0" . parameter array object[] value ( guid xxxx ) var whereclausesb = buildlogicalkeywhereclause2(entity, logicalkey); //build string var parms = buildparamarray(entity, logicalkey); // object[] var wherelambda = ofsi.bos.core.dynamicexpression.parselambda<t, bool>(whereclausesb.tostring(),parms); //parse an exception thrown in dynamicexpression.parselambda operator '==' incompatible operand types 'guid' , 'guid' i have tried guid , string.(fail) i tried , "id = @0" (fail). string == string works, int32==int32 not guid == guid not any ideas? try using equals method instead of == operator in string: "id.equals(@0)"
Read more