A Smoke Test is a process of validating code changes before the changes are checked into the product’s official source code. That means it is usually done when a bug fixing or change request is executed. Smoke Testing is also called Build Verification Test or Rattle Test.
This can be done either by developers or testers. If developers do this, it should be done before the release of product (or “build”) and if testers, – done before moving to next types of testing. Nowadays these tests are performed by some automated system which is included in the build mechanism.
You must be logged in to post a comment.
Isn’t it something which we do anyway? Sometimes we do it along with routine detailed testing, sometimes the developer does it before a beta version is ready for the testers. But how would an automated system perform such basic tests?