Asking developers to do QA is broken – why anyone should own QA
Asking developers to own QA is broken because developers are naturally biased towards the happy path. If you want to build a bar, you need someone to order -1 beers[1].<p>Handing off QA to an external team is broken because those people don&#x27;t have the necessary experience with the product, nor can they quickly and easily engage with development to get to the heart of a problem (and a fix.)<p>Having QA rely exclusively on automation brings quality down as the application&#x27;s complexity goes up. Writing tests to cover every possible edge case before the product ships isn&#x27;t feasible.<p>The best solution I&#x27;ve seen in the decades I&#x27;ve been in software development has been to have QA and Dev as part of a team. Automation covers as much of the product as possible, and continually grows as issues are identified that can be covered by CI from here on out. QA become essential at the boundary of new features, and require a deep understanding of the product in order to know what knobs to turn that might break the application in ways the developer never thought about. Once those sharp edges are also automated, QA pushes the boundary forward.<p>[1]: <a href="https:&#x2F;&#x2F;twitter.com&#x2F;brenankeller&#x2F;status&#x2F;1068615953989087232" rel="nofollow">https:&#x2F;&#x2F;twitter.com&#x2F;brenankeller&#x2F;status&#x2F;1068615953989087232</a>