Example of Bug Resolution
Times document
Created
by Roman Savin, web: QATutor.com.
Feel
free to use it for your projects!
Read
about this document in Tutorial
How to Become a Software Tester
by Roman Savin
Bug Resolution Times
Important notes
Bug resolution time is a period given to developer to
fix assigned bug,
unit test the fix and check it in. If developer is
unable to do it within specified resolution time,
he/she must immediately communicate this with his/her
manager.
Fixed code for P1 and P2 bugs found on Production
must be pushed as patch release.
Relevant Documents
EBF Procedure
Bug Priority Definitions
Bug Resolution times
Bug
Priority* |
Production |
Test
Environment |
P1 |
ASAP. Drop whatever you do. |
24 Hours |
P2 |
24 Hours |
48 Hours |
P3 |
n/a* |
72 hours |
P4 |
n/a** |
Fix if possible |
* P3s are to be fixed in the
next minor or milestone release
** P4s are fixed if possible
and thus are not suitable for patch releases.