Contents
What would you do if developer rejects your bug?
There are many reasons and things you can do but the first thing you need to do is to understand why developer does not agree with you.
- Understand what’s happening.
- If developers do not get your bug report or do not fully understand the severity of the bug you found, review your bug report again.
How do you handle a production bug?
In this post, I’ll walk through a series of steps testers can take to handle Production bugs and prevent them in the future.
- Step One: Remain Calm.
- Step Two: Reproduce the Issue.
- Step Three: Gather More Information.
- Step Four: Understand the Root Cause.
- Step Five: Decide When to Fix the Issue.
- Step Six: Test the Fix.
How do you handle a major bug if you found close to release?
How to handle major bug if found very close to release
- Don’t report it since it may block the release and you may be blamed for reporting it too late.
- Double check the bug vulnerability.
- Report bug and inform Project manager.
- If you running out of time for release suggest to add this to release letter.
- etc.
What is a rejected bug?
Rejected: If the developer feels the defect is not a genuine defect then it changes the defect to “rejected.” Deferred: If the present bug is not of a prime priority and if it is expected to get fixed in the next release, then status “Deferred” is assigned to such bugs.
When does a developer get frustrated with a bug?
When bug count increases or bugs are severe and it’s causing difficulty for the developer to solve that bug, the developer gets frustrated at the count and even at the person as well. The understanding level between these two roles conflict not only in one place but in many areas.
Can a developer accept that someone else has detected a bug?
It’s sometimes difficult for developers to accept the fact that their code is defective—and someone else has detected it. Developers need support from the testing team, who can assure them that finding new bugs is desirable, healthy, and important in making the product the best it can be.
Why do some developers do not like testers?
Take a psychological approach. Praise the developer’s job from time to time. The reason why most developers dislike our bug reports is very simple: They see us as tearing down their hard work. Some testers communicate with developers only when there is a problem.
Why do so many developers dislike bug reports?
The reason why most developers dislike our bug reports is very simple: They see us as tearing down their hard work. Some testers communicate with developers only when there is a problem. For most developers, the software is their own baby, and you are just an interfering outsider.