Retesting, Sanity, Smoke, and Canary Testing are often confused, but they serve different purposes in the release flow.
Retesting → checks the exact bug fix
Sanity → checks nearby affected areas
Smoke → checks if the build is stable
Canary → checks production health on a small % of users
Most QA engineers use OpenSearch just to search logs.
But experienced engineers use it to investigate entire systems 👀
Missing events, retry storms, correlation IDs, race conditions, hidden backend failures - this is where debugging becomes real detective work.
Check out this Linkedin post covering some of the most underrated OpenSearch techniques that can completely change how QA engineers investigate production issues 🚀
💸 Code vs. Revenue: why “shipping code faster” is no longer a competitive advantage
📅 May 26, 16:00 (CEST)
Where is real value created today — and how do you connect engineering with business results?
🎤 Julia Kniazeva — Director of Product & Engineering (10+ years, 6 products worth €1B+)
We’ll cover:
— why speed is no longer the key metric
— where business value gets lost
— what metrics actually work
— how to move from backlog to revenue
👨💻 For EMs, TLs, CTOs, and anyone who wants engineering to drive business impact