QA 2.0

In this talk, I focus on how "QA" has turned into a loaded word. Engineering leaders should be wary of creating departments where a "wall" can exist, that the work of quality can be thrown over.

Ultimately, engineers need to be responsible for quality, and there needs to be a strong culture of quality in order to make that happen.

Things that can add to this culture of quality are peer code reviews, testing plans crafted by engineers, staging walkthroughs, and keeping the team around for deploys and maintenance of the feature they launched.

Testers can assist engineers bring quality to their work, but they should not be thought of as a replacement for an engineering culture of quality.

Transcript

1. QA 2.0
4. THE WALL
5. ENGINEERING OWNS QA.
7. ENGINEERING OWNS QA??
8. Every engineer you hire is a QA engineer. — Michael Bolton - Developsense
9. Testing is not quality assurance. Testing brings awareness to the people who put the quality in. — Michael Bolton - Developsense
10. QUALITY Assistance
11. YOU ALWAYS HAVE TESTERS
12. CULTURE OF QUALITY
13. AVOIDING QA
14. PEER REVIEWS ▸ Don't rely on one guy ▸ Engineers spend maybe 10-15% of their time reviewing ▸ Ultimately team lead should have final say
15. TESTING CHECKLISTS
17. CODE REVIEW, TESTING STATES
19. DEPLOYMENTS & DEFECTS ▸ Team is online to deploy features ▸ Will support + fix any reported defects ▸ Keep teams static
20. DHH IS RIGHT!!
21. DHH IS WRONG!!
22. THANKS! @GAMMONS