What do you do when your developer denies that what you filed is a bug?

What do you do when your developer denies that what you filed is a 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.

  1. Understand what’s happening.
  2. 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.

What is a bug report?

A bug report contains device logs, stack traces, and other diagnostic information to help you find and fix bugs in your app.

What is a valid bug?

Case 1: If the error message is not as per the acceptance criteria ,and if there is a separate error message mentioned for special characters input ,then it will be a valid bug.

How to fix a bug, step by step?

How to fix bugs, step by step. 1 Step 1: Enter the bug in your case tracking system. 2 Step 2: Google the error message. 3 Step 3: Identify the immediate line of code where the bug occurs. 4 Step 4: Identify the line of code where the bug actually occurs. 5 Step 5: Identify the species of bug.

What should I do if I find a bug in my software?

If the bug goes away then it was either the hardware, operating system or runtime. You might even try this step earlier in the process–per your judgement–as hardware failures frequently masquerade as software dysfunction. If your program does network I/O then check switches, replace cables, and try the software on a different network.

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

If you can’t isolate the bug to any particular line of code, either begin to disable blocks of code (comment them out) until the crash stops happening, or use a unit-testing framework to isolate methods and feed them the same parameters they’d see when you recreate the bug.

Can you step backwards to find a bug?

Once you know the immediate line, you can step backwards to find where the actual bug occurs. Only sometimes will you discover that they’re both one and the same line of code. Just as often, you’ll discover that the crashing line is innocent and that it has been passed bad data from earlier in the stack.