Skip to content
BENIBIX Learn

Smoke Test vs Regression Test

A smoke test is a quick check, in a minute or two, that the app works at all. A regression test checks that something which used to work still works after a change. Smoke tests ask if it is alive; regression tests ask if anything broke.

Development🧪 Testing & Quality

Smoke Test

A quick check that the main parts of an app work at all.

A smoke test is a quick check that the most basic parts of an app work at all. Does the site load, can a user log in and does the main page show data? It runs in a minute or two, often right after a deploy. If it fails, there is no point running the deeper tests. The name comes from hardware: switch it on and see if it smokes.

Example
After each deploy, Jack's smoke test loads the home page, logs in and opens one order. It takes 40 seconds.
Why it matters
It finds a broken release in a minute. Users do not see it, and slow tests do not waste an hour.
Full entry
Development🧪 Testing & Quality

Regression Test

A test that checks old features still work after you change the code.

A regression test checks that something which used to work still works after a change. A regression is a bug that comes back, or a feature that quietly breaks. When you fix a bug, you add a test that would have caught it. That test then guards the fix forever. Over time, the whole test suite becomes your regression suite.

Example
Emma fixes a bug where a cart with 0 items crashed. She adds a regression test for the empty cart, so it can never come back unseen.
Why it matters
Changes in one place often break things somewhere else. Regression tests catch that before users do.
Full entry

In one line

Smoke Test
A quick check that the main parts of an app work at all.
Regression Test
A test that checks old features still work after you change the code.