Testing Basic Interview Questions : Difference between Smoke and Regression Testing in Tabular Form

Difference between Smoke and Regression Testing in Tabular Form

Distinction between Smoke and Regression Testing - Simple

              Smoke testing
               Regression testing
1. Smoke testing is a surface level testing to verify/ensure that build provided/given by development team to QA team is ready to accept for further testing.
1. Regression testing is not considered as a surface level testing and it is performed/ executed by testers only.
2. Smoke testing is known as a quick-and-dirty test means that the major/crucial functions of a piece of software work/perform without bothering with finer details.
2. Regression testing is not known by the quick-and-dirty test and in this testing testers test the application with more details.
3. It is executed/ performed when testers have to accept a build for further testing.
3. It is executed/performed when tester’s have enough time for testing.
4. Smoke testing may be conducted manually or by using automation tools.
4. Regression testing is also conducted manually or using automated tools.
5. Performing smoke testing will not enlarge the product cost and budget because it didn’t requires more manpower and time.
5. Performing Regression testing definitely will enlarge the product cost and budget because it requires more manpower and time.
6. It is also called as BAT (Build Acceptance Test) or BVT (Build Verification Testing).
6. It is not known by any other name.
7. It is done by developers before the build is released or by testers before accepting a build for further testing.
7. It is usually done by testers only.
8. We use script for smoke testing.
8. We use script for regression testing.


4 comments:

  1. Do we alter the Regression test scripts for every changes in the same module?

    ReplyDelete
  2. better to explane with some example

    ReplyDelete
  3. Well, smoke testing should take place at the beginning of the software testing life cycle. Smoke testing quickly verifies the quality of the build and evaluates the basic tasks whether they can be executed or not. This method of testing should be adopted when there is a change in the build or whenever a new build is deployed.

    ReplyDelete