Panoramic Quality: The Fellowship of Testing in DevOps
1 like240 views
Brendan Connolly, a Senior Quality Engineer at Procore Technologies, discusses the evolving landscape of software quality, emphasizing the importance of understanding code, architecture, and customer needs. He advocates for strong ownership of quality processes and features, highlighting the role of tests, observability, and collaboration in ensuring software reliability. The focus is on proactive coordination and stewardship in product development to create effective and user-friendly applications.
Panoramic Quality: The Fellowship of Testing in DevOps
- 1. Panoramic Quality Brendan Connolly @theBConnolly || http://brendanconnolly.net Sr. Quality Engineer, Procore Technologies, Santa Barbara CA
- 2. @theBConnolly Panoramic Quality Brendan Connolly @theBConnolly || http://brendanconnolly.net Sr. Quality Engineer, Procore Technologies, Santa Barbara CA
- 4. @theBConnolly SPEED Orders of Magnitude Risk / Release Inversion
- 11. @theBConnolly Know =>Code Topography => how the pieces fit together => how data flows
- 12. @theBConnolly Know =>Code Streets & Neighborhoods => Find your way around => Know the Rough Areas => Where “stuff” goes down
- 13. @theBConnolly Know =>Code Talk Me Thru Your Changes => Know the story behind the code => Be a the sounding board => How do unit tests reflect the change?
- 14. @theBConnolly Protect =>Code Code is Protected by Tests Not Testers => Unit Tests are a foundation for quality
- 15. @theBConnolly Verify =>Code Demonstrate Before Deploy => At any stage => Is it performant? Is it secure?
- 17. @theBConnolly Know => Architecture The Geography of Software => How it’s built / deployed => Where it’s running => How it solves your customers problems
- 18. @theBConnolly Know => Architecture Environmental Impact => Local, Staging, Production => What Works Where? => What Doesn’t?
- 19. @theBConnolly Know => Architecture Boundaries of Risk => Boundaries of components can be borders between developers
- 20. @theBConnolly Verify => Architecture Minimum Viable Environment => Work as close to home as you can => Take the Developers local changes => Identify tests
- 21. @theBConnolly Protect=> Architecture Seams, Cracks & Gaps - Seams=> where Information exchanged - Cracks=> Where faults occur at the seams - Gaps=> Missing coverage / holes in your strategy
- 22. @theBConnolly Protect=> Architecture Happy Little Tests => No middle child avoidance => Write tests that stress interactions target their level appropriately
- 23. @theBConnolly Verify => Architecture Health & Wellness => Monitoring => Surfacing information
- 25. @theBConnolly Know => Customer Application & Audience => Application Expertise => Persona / Permission Boundaries => Interactions & Motivations
- 26. @theBConnolly Protect => Customer Feature Corruption - When adding functionality for one group of users affects others NEGATIVELY - Not a regression because it’s a new/ additive change.
- 27. @theBConnolly Know => Customer Change Tolerance => Instability is indistinguishable from rapid change
- 28. @theBConnolly Protect => Customer Feature Flags => You need it in production does your customer? => Do all of your customers?
- 29. @theBConnolly Verify => Customer Test In Production If a bug is production but no customers can access it, is it still a bug?
- 30. @theBConnolly Verify => Customer User Analytics => It’s not just about catching errors => Instrument to measure effects and usage
- 31. @theBConnolly
- 33. @theBConnolly Product Ownership - Define the product backlog - Groom and prioritize the backlog - Ensure completed user stories fulfills the acceptance criteria https://medium.com/@melissaperri
- 34. @theBConnolly Product Ownership Focused On: - Features, Market, Schedule Goes Deep On: - Domain, Competition, Planning
- 35. @theBConnolly Quality Ownership Focused On: - Features, Value, Safety Goes Deep On: - Application, Customers, Planning
- 38. @theBConnolly Quality Ownership Stewardship: - An ethic that embodies the responsible planning and management of resources. - the responsible overseeing and protection of something considered worth caring for and preserving
- 39. @theBConnolly Quality Owner => Steward Product => steward of what will be built Quality => steward of what has been built
- 40. @theBConnolly Quality Owner => Stewardship Quality is in Your “Charge” Responsibility for controlling or caring for something A formal statement accusing someone of committing a crime
- 41. @theBConnolly Quality Ownership=> Support Open Source your Mindset => Be an #ALLY for testing => Enable & Mentor Quality => Infuse Quality into automation
- 42. @theBConnolly Quality Ownership=> Support Supporting Quality Testing
- 43. @theBConnolly Quality Ownership=> Support Avoid Pyramid Obsession => Pyramids aren’t models of efficiency => Quality isn’t in layers
- 44. @theBConnolly Quality Ownership=> Support Testing Cathedral => Your app is central => Counter-balance risk with efficient supports
- 45. @theBConnolly Quality Ownership Observability: - An ethic that embodies the responsible planning and management of resources. - the responsible overseeing and protection of something considered worth caring for and preserving
- 46. @theBConnolly Quality Ownership=> Observe Continuous Feedback Virtuous cycle of better observability Source: https://medium.com/@copyconstruct
- 47. @theBConnolly Quality Ownership=> Observe Continuous Collaboration => Build skills to break down barriers to collaboration
- 48. Quality Ownership Hands on Code Hands on Customer Supporting a pipeline of Quality from pull request to production
- 49. @theBConnolly Be Well, Connect, Share Connect With Me Twitter / LinkedIn : @theBConnolly Blog: http://brendanconnolly.net