Why I run smoke tests directly in production and how they once broke my analytics

In this article, the author explores the practice of running automated smoke tests directly in a production environment. The focus is on using synthetic traffic to simulate real user scenarios within messaging applications. The author shares a personal experience where test bot activity was mistakenly identified as real user behavior, leading to significant distortions in key product metrics such as DAU, WAU, and MAU. The article discusses strategies to prevent such issues, including methods for filtering technical traffic and implementing 'soft delete' mechanisms. It offers practical recommendations for engineers looking to adopt production testing without compromising the accuracy of business analytics or the quality of collected user behavior data.
This is a summary. Read the full article at the original source:
HabrRelated stories
How Sanity Context & MCP Supercharged AI Customer Support in Basegent & Bucket Space
Developer Miracle Onyenma details the architecture behind Basegent, an AI-driven customer support platform integrated with Sanity Context. Moving beyo…
Vincent Bernat explores a robust, self-hosted approach to creating HTTP tunnels using standard SSH and Nginx configurations. Rather than relying on th…
I built a 2,000-page, four-language website with AI. Google sends it two people a day
The creator of artatlas.site shares their experience building a large-scale art history encyclopedia using the AI tool Claude Code. The site contains…



