What will you do if developer is not able to reproduce defect?

What will you do if developer is not able to reproduce defect?

Reproduce the defect when developer has marked as CNR: When developer is unable to reproduce the defect then perform the same scenario (that caused the defect) on same environment where it occurred for the first time.

How do you tell a customer about a bug?

3 simple rules for when a bug or outage affects your users

1. Find out the root cause of the issue (and fix it) As quickly as possible figure out the root cause, and stop it from continuing.
2. Identify people affected. Who was affected?
3. Email your customers before they email you.

Why is defect rejected?

Defect rejection related to test description – When the developer is unable to understand what you were trying to convey via reported defect, expect it to be rejected because they are also loaded with other tasks and if they do not find proper description, no matter how critical the defect is, it’s expected to be …

How do systems communicate with problems?

11 outage communication best practices

1. Acknowledge the issue.
2. Empathize with impacted customers.
3. Clearly communicate the scope of the outage.
4. Focus on customer impact.
5. Give alternatives where possible.
6. Don’t lay blame; take responsibility.
7. But do give important context.
8. Write to your audience’s technical level.

What organisms can survive but not reproduce?

A virus is a microscopic particle that can infect the cells of a biological organism. Viruses can only replicate themselves by infecting a host cell and therefore cannot reproduce on their own.

Why do developers reject bugs?

When the developer does not able to understand what you were trying to convey via the bug report, expect it to be rejected because they are also loaded with other tasks and when they do not find proper description and required details in bug report, no matter how critical the bug is, it is expected to be marked as …

Is it possible to reproduce a bad bug report?

Reproducing problems, especially when you are working from a bad bug report (“the system was running fine all day, then it crashed… the error said something about a null pointer I think?”) can be a serious time sink. But what if you can’t reproduce the problem at all?

What to do if you can’t replicate a bug?

If you discovered the bug, you should be able to replicate it. If you can’t replicate it, then you simply haven’t considered all of the contributing factors leading towards the bug. This is why whenever you have a bug, you should document it. Save the log, get a screenshot, etc.

Why is it important to reproduce a bug?

But reproducing the problem first gives you the confidence that you aren’t wasting your time and that you actually fixed the right issue. Trying to reproduce the problem should almost always be your first step. What’s involved in reproducing a bug?

Are there any bugs that you can’t reproduce?

(Of course, this very much depends on how severe the bug is). Many users have strange software configurations, invasive browser extensions, and unusual network conditions. These often create problems that are impossible to reproduce. And often these problems are worth fixing. Of course, I’m assuming that you do have other important things to do.