Achieving Excellence in a Startup without a Dedicated QA
summary
A startup removed its dedicated QA and focused on reducing time-to-market by about one day while keeping incident rates steady. Engineering implemented automated testing (Cypress end-to-end, frontend component tests, backend integration tests in Go with containerized runs), CI/CD with GitLab review apps and canary releases using Argo Rollouts, and added observability (logs, alerts, tracing, canary metrics, Sentry) to speed deployments and reduce process handoffs.
AI-written summary · about
chapters (9)
- 0:00About me. Agenda
- 1:07About the company Howly by SKELAR
- 2:15Engineering
- 10:04Processes
- 17:45Testing strategy
- 22:50Observability
- 24:05CI/CD
- 28:24Takeaways
- 35:16Q&A
related talks
21mEstablishing Quality Assurance in Startup environment
49mOptimizing QA Flow to Minimize Time to Release While Meeting Quality Standards
13mFewer Tools, More Impact: An Automated Testing Strategy for Scale-Up
42mI Don’t Need No Tests
01h 09mScaling up with Embedded Testing
46mQA to QE: Scaling Quality with Ownership, Code, and Culture
38mScaling Automated Testing & Architecture from Startup to Enterprise
24mWhen Start-Up Meets Quality… A Short Story of QA Agent