Create Automated Smoke Tests for the Build

Whether or not you use continuous integration, create some automated smoke tests for the build. Smoke tests merely verify the build is not broken. Don’t let me dissuade you from adding as many regression tests as you like, but the idea behind a smoke test is to know whether the build is useful to anyone.

Automated smoke tests help the project team know whether anyone has broken the build. If you know as soon as a build is complete, you can do something about it. If you rely on a developer or tester to tell you whether the build is broken, you can’t act as quickly as you might like to fix the build.

Don't Let the Smoke Out!
by Meredith, senior tester
Meredith

As a tester, my job is to find problems. ...

Get Manage It! now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.