Why Companies Without Testers are the Best Place to Be One
Talkat CAST 2016 · on Wednesday, 2016-08-10· at 13:15· Fletcher Challenge Theatre (1900), Simon Fraser University Vancouver 515 West Hastings Street Vancouver, BC V6B 5K3·
summary
Company runs without a separate QA group: engineers write tests first with TDD, pair about 80–90% of the time, and push through CI using Concourse pipelines across AWS/OpenStack/vSphere that parallelize long integration and acceptance suites. Complex ops get manual checks—e.g., toggling disable_auto_sst false on a 3‑node MariaDB/MySQL cluster and exercising it via BOSH Lite—while exploratory work is tracked as exploratory charters as tracker stories and a small Go replication canary validates cross‑node commits.
AI-written summary · about
chapters (17)
- 0:00Intro
- 2:18Testing Without Testers
- 3:27Pivotal Labs
- 9:10Continuous Integration
- 14:38Exploratory charters
- 18:08The value of exploratory charters
- 23:37Pairing
- 24:49Another Testing Practice
- 27:44Planning Meetings
- 29:52Ping Pong
- 31:36Communication
- 34:44Iterating
- 38:54Play Zendo
- 40:10Ask Questions
- 40:59Product Managers
- 42:59Traditional Development Tasks
- 47:37Tester vs Developer
related talks
42mI Don’t Need No Tests
58mHow I became a tester!
36mWhole team quality: In the same boat or up the creek?
36mHow programmers & testers can be productive
44mAchieving Excellence in a Startup without a Dedicated QA
01h 09mScaling up with Embedded Testing
31m#testedAF: Test All the Things (Not Just Your Units)
51mQuality Assurance vs. Testing