Smoke signals our journey towards Environment Reliability
summary
Built a smoke pipeline on Jenkins with multiple OS agents and parallel executors that runs 40 atomic checks across 21 applications and returns a full-cycle result in 9 minutes across SIT UAT and Prod, surfacing 33 environment defects so far. Teams stop bloated, UI-heavy checks, reuse existing automation frameworks, and shift checks to API/service layers for speed. Roadmap adds Grafana dashboards and ML on historical logs to predict likely failures before check-ins.
AI-written summary · about
chapters (7)
- 0:00Introduction to talk
- 1:32Industry need for smoke testing
- 4:00Team objectives for smoke testing
- 6:33Reference architecture explained
- 9:03Common pitfalls in smoke testing
- 13:55Key success metrics achieved
- 15:23Future plans for optimization
related talks
24mSmoke to avoid Fire
35mUsing the DevOps Pipeline to Generate Continuous, Valuable Insights
43mHow We Gained Observability Into Our CI/CD Pipeline
35mGaining Observability Into Your CI/CD Pipeline
26mIntelligent Deployment Pipelines
48mSmokeTests
24mIgnite Talks Day 2
53mTransforming testing methodologies: From manual to robust strategies