Community of Software Testing Professionals
5 Reasons for not fixing a bug
What can be the reasons that bug might not be fixed?
According to my opinion
1. When a tester is not able to reproduce that bug to developer.
2. When a tester have some misconception about the functionality and raise that bug.
What can be the other valid reasons?
According to my opinion
1. When a tester is not able to reproduce that bug to developer.
2. When a tester have some misconception about the functionality and raise that bug.
What can be the other valid reasons?
Replies to This Discussion
-
Permalink Reply by Harish Pulari on -
1. Technical issues ( For Example :- memory leak issue in some flex controls)
-
Permalink Reply by Ajithkumar G on -
1.Some times time line may be a reason.
2.Developers ego to accept that as a bug.
-
Permalink Reply by Marichamy on -
Palasa marakka kudathu ... boss.......
Varalaru remba mukkiam amaicharey............
-
Permalink Reply by Venkataraman on -
1. Due to the low severity, some of the bugs can be "Deferred" or even "Rejected"
2. Low severity bugs, which has the major impact on the other working modules
3. Bugs which are very rarely produced by the end user
-
Permalink Reply by Marichamy on
-
Yes, Great.. i agreed all your points. I listed my options also.
1. Missed use case may be We(Developer/Tester) also missed some use cases.
2. Some Edge use cases.
3. Dis-similar between our testing and real time environment, that means our testing setup data and real customers data.
4. As mentioned Venkat, we allowed some low severity bugs. These bugs really impact other modules, yes i have an experience in that.
-
Permalink Reply by nagendra on -
As always the human ego, is one of the major reasons.
As Ajithkumar mentioned its not Developers ego its the human perspective and I hope we all share some of it.
Now what if I tell you that your testing knowledge is so dumb to ask this question, wont you feel bad and tell 'common who is this guy to talk about my knowledge, I am worth asking a question atleast' this attitude of humans makes them to reject or come up saying its not reproducible and some times ask us to change the priority.
I guess Communicating the bug in a proper manner will help in fixing the bug, and also not disturbing a person's ego.
Thanks,
Nagendra
-
Permalink Reply by Vanita on -
1)One reason is bug is not guniue.
2)Another reason may be bug is inconsistent.
-
Permalink Reply by Mohit Wattal on -
Possibly the most frequent and the important one's have been stated already but to filter out :
1: There is No exact documentation to identify the exactness/correctness of the bug
2 : Developer's ego,not to accept but there are people above his levels to make him accept that anyways and this is the job of the tester himself to convince him after all. But this however, remains a very important factor.
3: Time constraints in case of project deadline etc.
4: Quite frequently the bugs are not even observed,neither by the tester's nor the client or users,leaving them unfixed but a mystery.
Thanks,
Mohit Wattal
© 2010 Created by EDISTA.
