Emir Atli of Indie Hackers<\/a>. \u201cIt helps you to validate your idea. Smoke tests can even preempt the MVP concept.\u201d<\/p>\n\n\n\nFor example, suppose an online media site wants to implement a \u201csnooze my subscription” feature, but they don’t know if it will actually stop people from canceling. Instead of building out the full functionality on their site, they add a button and measure its clicks.<\/p>\n\n\n\n
The button doesn\u2019t do anything, of course (though maybe it takes them to a simple page that says \u201cthis feature is coming soon\u201d), but the number of clicks helps the company understand how many people would consider using such a feature.<\/p>\n\n\n\n
Origin of the Name \u201cSmoke Testing\u201d<\/h3>\n\n\n\n
We don\u2019t know exactly where the term came from, but there are two potential origin stories.<\/p>\n\n\n\n
One possible origin comes from the plumbing industry, where smoke was (and sometimes still is) used to test for leaks and cracks in pipes. It\u2019s a quick way to identify the problem.<\/p>\n\n\n\n
Another possible origin comes from hardware testing, where devices are initially switched on and tested for signs of smoke in their components.<\/p>\n\n\n\n
It\u2019s hard to say if either is true, but it\u2019s evolved into a widely used term in software development. Smoke testing is a subset of tests used to assess if a software build is stable enough for the next development stage. Specifically, it identifies any bugs blocking the release of a product.<\/p>\n\n\n\n
In classic marketing fashion, growth teams have adopted and redefined smoke testing as a quick tool to validate ideas. This is the context in which we\u2019ll be using it today.<\/p>\n\n\n\n
Why Do Marketers and Product Managers Use Smoke Tests?<\/h2>\n\n\n\n
The beauty of smoke testing is that it provides quick validation without requiring significant resources. You can find out if an initiative has genuine interest or demand before you develop it.<\/p>\n\n\n\n
Naturally, this means that smoke tests save time and money. By testing the waters with a basic version or even just a concept, you can gauge user interest without diving into a full-scale development project. It also reduces risk, so you can abandon ideas that don\u2019t resonate with your audience before you\u2019ve spent too much.<\/p>\n\n\n\n
Feedback is another benefit. When you put a preliminary idea out there, you can quickly learn what potential users think and feel about it. This expands your knowledge about your customers, which helps you refine or design future products.<\/p>\n\n\n\n
Smoke tests are also great tools for prioritizing features. If your resources are limited, it\u2019s important to focus on what will bring the most value. Smoke testing tells you which features or products are worth pursuing so you can better allocate resources.<\/p>\n\n\n\n