88""Yb 888888 db 8888b. Yb dP 888888 dP"Yb 888888 888888 .dP"Y8 888888
88__dP 88__ dPYb 8I Yb YbdP 88 dP Yb 88 88__ `Ybo." 88
88"Yb 88"" dP__Yb 8I dY 8P 88 Yb dP 88 88"" o.`Y8b 88
88 Yb 888888 dP""""Yb 8888Y" dP 88 YbodP 88 888888 8bodP' 88
Software QA and Support ★ Automation ★ Manual Testing
Current Date & Time (Pacific) ★
------------------------------------------------------------------------
QA Accountability
philosophy.htm ⮐
QA owns risk communication and coverage. If a critical path wasn't
tested or QA knew about an issue but didn't clearly flag the risk
before release, that's on QA. I've missed things before. It happens,
but I've been fortunate not to work on teams that treat QA as the
fall guy.
💡Once, someone blamed QA for a bug, but the Jira ticket showed
QA flagged the risks and the release was rushed anyway. It was
a process miss, not a QA one.
I've seen a lot of chatter in QA forums about teams where blame
rolls downhill to QA. Bugs show up when requirements are unclear,
designs are skipped, or code is rushed, but instead of improving
planning or ownership, some orgs just pin it on QA. That hasn't
been my experience, but I know it's real for others.
------------------------------------------------------------------------
Top ⇧