Skip to main content

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.


Labels:

Comments

  1. UnknownDecember 17, 2015 at 4:12 PM

    nice

    ReplyDelete
  2. UnknownJuly 29, 2017 at 8:05 PM

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

    ReplyDelete
  3. AnonymousSeptember 20, 2017 at 3:35 PM

    better to explane with some example

    ReplyDelete
  4. JessicaNovember 15, 2021 at 6:19 PM

    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

Post a Comment

Popular posts from this blog

Difference Between Verification And Validation With Example?

Verification and Validation example is also given just below to this table.                Verification               Validation 1. Verification is a static practice of verifying documents, design, code and program. 1. Validation is a dynamic mechanism of validating and testing the actual product. 2. It does not involve executing the code. 2. It always involves executing the code. 3. It is human based checking of documents and files. 3. It is computer based execution of program. 4.  Verification uses methods like inspections, reviews, walkthroughs, and Desk-checking etc. 4.  Validation uses methods like black box (functional)  testing, gray box testing, and white box (structural) testing etc. 5.  Verification  is to check whether the softwar...
66 comments
Read more

Regression Testing with Example and Strategies

Regression Testing is done to ensure that fixed bug does not affect the remaining functionality of the modules and also the functionality of the same module. In short you can say regression testing  is always done to verify that modified code does not break the existing functionality of the application and works within the requirements of the system. Regression Testing Example  For Example there are three Modules in the Project named Admin Module, Personal Information, and Employment Module and suppose bug occurs in the Admin Module like on Admin Module existing User is not able to login with valid login credentials so this is the bug.  Now Testing team sends the above - mentioned Bug to the Development team to fix it and when development team fixes the Bug and hand over to Testing team than testing team checks that fixed bug does not affect the remaining functionality of the other modules (Admin, PI, Employment) and also the functionality of ...
31 comments
Read more

What Is Functional Testing Explain It with Example?

Functional testing means testing the application against business requirements. Functional testing is executed using the functional specifications given by the client or by the design specifications according to use cases given by the design team. Role of functional testing is to validating the behavior of an application. Functional testing is more important because it always verifies that your system is fixed for release. The functional tests define your working system in a useful manner. In functional testing tester has to validate the application to see that all specified requirements of the client whatever we have said in SRS or BRS have been incorporated or not. Functional testing  is always concentrating on customer requirements and whereas the Non-Functional testing is always concentrating on customer expectations. Functional and Non Functional Test Cases Functional test cases target business goals and non functional test cases target performance, resource...
29 comments
Read more