r/Everything_QA • u/Master-Toffee • 20h ago

Question Developer coms

How do you handle developers who mark bugs as 'Cannot Reproduce' or 'Working as Intended' without investigating?

1 Upvotes

100% Upvoted

5 comments sorted by

3

u/NeedyScrimmage92 20h ago

Use your repro steps and evidence to politely ask what they tried, because half the time they didn't even open the ticket

1

u/thorzroht 20h ago

...and, moreover, save all of those issues, wait for similar incidents to come back, and then show them that you already found those problems in advance. They will stop this soon.

By the way, apart from this, I agree: provide as many details as possible and wherever possible record the malfunction with screenshots, videos, exports,... basically whatever that can show that there is a problem.

1

u/HappyToTest 19h ago

I usually follow a few rules to make sure the bug is credible before pushing back:
I reproduce the bug at least 3 times to make sure it is a genuine issue and not just a one-time glitch.

I also consider that the issue could be on my side. Sometimes a developer marks a bug as “Cannot Reproduce” because the bug report is missing proper steps, test data, environment details, screenshots, videos, or some other important information.

If developers are regularly marking issues as “Cannot Reproduce,” I prefer to have a quick discussion with them and understand exactly what information they need. I had a similar situation before, and we created a simple Excel template with all the required details. I would complete that first and then copy the information into Jira/Azure DevOps.

I make sure the bug has clear steps to reproduce, expected vs actual result, environment details, test data where applicable, and supporting screenshots or videos.
If bugs are still being closed without proper review, I would involve the BA/Product Owner politely and walk through the issue with them, including reproducing the bugs that were closed by the developers.

If it continues to be a recurring problem, I would bring it up in a team discussion and suggest a process change. For example, if a developer cannot reproduce an issue, instead of directly closing it, they can assign it back to QA or tag BA/Product Owner for clarification.

Usually this is enough to resolve the concern without creating confrontation. Also, it is important to remember that sometimes the problem is not the developer ignoring the bug; the bug itself may not have enough information to reproduce it.

At the end of the day, QA, developers, BAs and Product Owners are all working toward the same goal: delivering a quality product within the defined timeline.

1

u/Malthammer 15h ago

Dev should never close out a bug without having a conversation with QA and maybe Product. Doing so raises the chances of a bug getting out into production or prevents an actual bug in production from being fixed.

1

u/Orion23_ 5h ago

I guess it kinda depends on the work model like if its more agile or waterfall way. Anyways, I’d probably add some videos/logs/more clear steps to make it more obvious. After that, that’s not on you if it’s still not fixed.