Evolution of QA to GA: The Sensu Go Crucible
summary
Startup moves QA from manual Word docs to an automated pipeline that triples test coverage (147 → 454 cases) and cuts execution time ~66% (4–6h → ~2h). Team provisions environments with Terraform and Ansible, writes smoke and sequential tests in Serverspec (RSpec), pushes results into TestRail and into the monitoring UI via a custom Sensu Go handler that turns test suites into events used for go/no‑go release decisions.
AI-written summary · about
chapters (13)
- 0:00Sensu Go and QA Crucible intro
- 3:53Testing pyramid and Sensu shift
- 7:22Chaos before QA improvements
- 13:07What QA really means
- 17:51Bias in manual testing
- 22:27QA Crucible process born
- 23:31Automating tests wisely
- 27:48Test case management choice
- 31:26Diverse QA talent hiring
- 34:55Monitoring and testing workflows
- 36:17Sensu automated testing demo
- 40:38Metrics and error costs
- 41:20Q&A
related talks
46mQA to QE: Scaling Quality with Ownership, Code, and Culture
43mLean QA: Automation, Monitoring, Experiments
36mWhy a Growing Company Needs a Growing QA Team
30mQA in DevOps: Transformation thru Automation via Jenkins
32mTools for Better Testing for Open Source Projects
13mFewer Tools, More Impact: An Automated Testing Strategy for Scale-Up
49mOptimizing QA Flow to Minimize Time to Release While Meeting Quality Standards
46mMaking Security Agile