2025-06-05 Thursday - Notes on Testing Schools of Thought

Status: work-in-progress 

Unless a business is in a highly regulated industry (and required, by regulation or standards - to establish separate testing teams), I do not believe it is generally beneficial to have a separate Testing/QA team - it simply creates yet another hand-off, and a gating function, that delays delivery of business value. 

If agile and DevOps practices are followed, the delivery team developers should be responsible for their own testing - and with CI/CD practices - testing should be automated to the maximum extent possible. 

This is a placeholder blog post to organize links to articles, books, and talks... 

Dave Thomas:

• YouTube: 
• Dave Thomas on Testing Past, Present, and Future
•  Code Quality: Lessons from The Pragmatic Programmer 

 

Dave Farley:  

• YouTube:
• Acceptance Testing Is the FUTURE of Programming  

• Articles:  
• The Impact of Continuous Delivery  

• Books: 
• Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation (Addison-Wesley Signature Series  (2010)
• Authors: Jez Humble, Dave Farley

Emily Bache: 

• YouTube:
• I REGRET Not Telling Dave Farley THIS about Approval Testing 
• Definition: Characterization Tests