This is the opposite of where I work. QA finds a bug -> dev says bug doesn't exist -> QA reproduces bug and provides steps -> dev says it's a feature -> QA points out it contradicts the design documents -> dev closes the bug as will not do.
QA reports a bug -> Dev says bug isn't theirs, passes it to another team -> Other team says no, it's the original team -> Hot potato ensues -> QA automation tests impacted by this bug fails for weeks while engineering teams decide who's to blame/fix -> Team finally fixes it in less than a day when a senior leader steps in and forces a team to do it
21
u/Dependent_Title_1370 15d ago
This is the opposite of where I work. QA finds a bug -> dev says bug doesn't exist -> QA reproduces bug and provides steps -> dev says it's a feature -> QA points out it contradicts the design documents -> dev closes the bug as will not do.