Uncategorized

SMOKE TESTING AND SANITY TESTING

INITIAL LEVEL TESTING

The smoke testing and sanity testing are two types of initial level testing. In the initial level testing software is tested for readiness before the detailed testing by QA team. Initial level testing is also called as build acceptance testing. A build is a complied code packaged in a single file called as .exe file which can be used for installation of software.

The two terms smoke testing and sanity testing are sometimes used interchangeably. Below are the two terms smoke testing and sanity testing explained with examples.

SMOKE TESTING:

It is testing technique which works similar to hardware testing. Suppose if u have any hardware device and you connect to the power and switched on if you get smoke then the test fails. In the same way it is applicable in software to test the basic functionality which is built. If it fails then it is considered as unstable. The primary goal of smoke testing is verify the main application functionalities and to satisfy the product. It shows those errors which saves the time as well as the developer’s effort. For example if a software has modules with the login page, main page and gallery. This testing deals whether the user is able to login properly with the valid credentials or is there a facility to create new user whether he can open the main page or gallery by logging in etc.

SANITY TESTING:

It is a basic or quick test done to the software when you don’t have enough time to do the other types of testing  it is a part of regression testing or performed before retesting. It is done to check whether the system has acquired any new problem or any bugs has left unfixed. It is mostly done after retest that after fixing all bugs in the software. For example your software has five modules Login page, Main Menu page, Form filing page and Feedback page. If any new functionality should be added like there is no new user creation or password reset option in the application. Then the QA team sends the application to development team. The developer team adds functionality to the application and checks the functions of all other pages as retest for any other minor problems which has to be fixed. It is also called as quick regression testing. There is always confusion between sanity testing and smoke testing. Sanity testing is done when the developer or a tester wants to know the quick performance of the product. Smoke testing is done after the software is developed to check the critical functionalities of the software. Sanity testing is  to show that minor changes in functions of the software does not affect to the main requirement of the product.

Check your understanding:

  1. Try to identify the differences and similarities between smoke testing and sanity testing.
Facebook Comments

Related Articles

52 thoughts on “SMOKE TESTING AND SANITY TESTING”

  1. The primary goal of Smoke Testing is to verify the main application functionalities and to satisfy the product. It shows those errors which saves the time as well as the developer’s effort. It is done after the software is developed to check the critical functionalities of the software.
    Sanity Testing is done to check whether the system has acquired any new problem or any bugs has left unfixed. It is mostly done after retest that after fixing all bugs in the software. It is done when the developer wants to know the quick performance of the product.

  2. Similarity: They are both initial level testing.
    Difference: Smoke testing is done after the software is developed to check the critical functionalities of the software. Sanity testing is done when the developer or a tester wants to know the quick performance of the product and check whether the system has acquired any new problem or any bugs has left unfixed. It is mostly done after retest that after fixing all bugs in the software.

  3. Try to identify the differences and similarities between smoke testing and sanity testing.

    Smoke Testing:
    Smoke testing is an end to end testing performed on the application that is deployed for the QA to test, to determine the stability. It is done by testing the crucial functionality of the application.
    The Development team does smoke tests before deploying the build to make sure the build is good.
    Smoke testing is done to ensure that, the crucial functions of the program are working as expected, and not concerned about the inner details. This is because, if the major functionality does not work, then there is no point in testing the other details.

    Sanity Testing:
    Sanity testing is done to check whether the newly added functionality/ bug fixes are working as expected or not.
    If sanity test cases are failed then there is no point in testing further as the required features or functionality is not available.

    Similarities:
    1. Both smoke and sanity are used as criteria for accepting or rejecting a build. Smoke is done to check the crucial functionality. whereas, sanity to check the new functionality.
    2. Smoke is performed on relatively unstable product (initial builds) while sanity is done on stable builds.
    3. Once the build passes smoke, the next step would be Functional testing and then regression testing.
    4. For Sanity, if a new functionality is added then Functional testing and regression. If there is a bug fix its retesting and regression.

  4. Ans.: The smoke testing and sanity testing are two types of initial level testing.
    Smoke testing technique which works similar to hardware testing. Suppose if u have any hardware device and you connect to the power and switched on if
    you get smoke then the test fails. In the same way it is applicable in software to test the basic functionality which is built. If it fails then it is considered as
    unstable. The primary goal of smoke testing is verify the main application functionalities and to satisfy the product.
    Sanity testing is a basic or quick test done to the software when you don’t have enough time to do the other types of testing. It is a part of regression
    testing or performed before retesting. It is done to check whether the system has acquired any new problem or any bugs has left unfixed.
    Difference between Smoke testing & Sanity testing
    S. No. Smoke Testing Sanity Testing
    1 Smoke testing means to verify (basic) that the Sanity testing means to verify the newly added
    implementations done in a build are working fine. functionalities, bugs etc. are working fine.
    2 This is the first testing on the initial build. Done when the build is relatively stable.
    3 Done on every build. Done on stable builds post regression.

  5. Both smoke and sanity testing are types of initial level testing.
    Smoke testing is to verify the main functionalities of the software.
    Sanity testing is done when the developer or tester wants to know the quick performance of the product and to show the minor changes in functionalities of the software does not affect the main requirements of the product. it is also called quick regression testing.

  6. Smoke testing is before delivering the application to the testing team they will do the basic functionality testing.

    sanity testing is the basic functionality testing will be conducted whenever we receive the bill from the developer.

  7. In manual testing test cases are executed manually without any support from tools or scripts. but with automation testing test cases are executed with the assistance of tools scripts and software. Testing is an integral part of any successful software project.

  8. Smoke testing and sanity testing, both are Initial level testing.Difference is that Smoke testing is to test initial steps of each functionality of the developed software where as Sanity Testing is to test initial steps of functionality in which defects are fixed.

  9. There is always confusion between sanity testing and smoke testing. Sanity testing is done when the developer or a tester wants to know the quick performance of the product. Smoke testing is done after the software is developed to check the critical functionalities of the software. Sanity testing is to show that minor changes in functions of the software does not affect to the main requirement of the product.

  10. Smoke Testing: Is an Initial Level Testing. Smoke testing checks the initial steps of each functionality. It is also known as build acceptance testing. It makes software ready for Functional Testing. If a software has login, links, buttons pages etc, smoke level testing is done to check the basic functions of these pages and buttons.
    Sanity Testing: Is also a type of Initial Level Testing. It test the initial steps of functionalities in which defects were identified and fixed. For eg: In the login page there was an error in password reset and it was reported to the developer and it was fixed. Sanity test is now done to check the password reset functionality only.
    Smoke testing and Sanity Testing are Initial Level Testing. Smoke Testing is done to check crucial functionality where as Sanity Testing is done to check New functionality.

  11. Smoke testing and sanity testing are two types of initial level testing.
    – Smoke testing tests the basics functionality of an application and satisfies the product. It shows the errors to save time as well as the developer effort. It’s done after the software is developed to check the critical functionalities it.
    – sanity testing is a basic and quick test done when there is not enough time to do other types of testing. It’s a regression testing, performed before testing to fix bugs and to see if the system has acquired a new problem.
    Sanity testing is also done to know the quick performance of the product.

  12. Both testings are initial level testing and testing the initial steps of each functionality. The difference is that, Smoke testing is to check the crucial fuctionality before the functional testing, but Sanity testing is done when the developer fix some issues and the new version is needed for testing the initial steps of functionality. It is done to check whether the system has acquired any new problem or any bugs has left unfixed.

  13. The differences between smoke testing and sanity testing are :
    *Smoke testing is done after the software is developed to check the critical functionalities of the software.
    *Sanity testing is to show that minor changes in functions of the software does not affect to the main requirement of the product.
    *Smoke testing will be done to check the critical or primary functionalities of software .
    * Sanity testing will be done to check the new functionalities added which does not affect the software .

  14. Smoke testing is done after the software is developed to check the critical functionalities of the software. Sanity testing is to show that minor changes in functions of the software does not affect to the main requirement of the product. both testing are done at a initial level testing and done before detailed QA testing is done

  15. The main point of smoke testing is verify the main application functionalities and to satisfy the product. It is the first stage to check the software is stable or unstable.
    Sanity testing: It is done to check whether the system has get any new problem or check the defect still there . It is done while the software is in developing stage , just to show any additional requirement added.

  16. Sanity testing and smoke testing both are initial level testing techniques.
    Sanity testing is done when the developer or a tester wants to know the quick performance of the product. Smoke testing is done after the software is developed to check the critical functionalities of the software. Sanity testing is to show that minor changes in functions of the software does not affect to the main requirement of the product.

  17. Smoke testing: To check whether the build received from the development team is ready for next level of testing. Just to see whether the important functionalities are working fine.
    Sanity testing: It is kind of mini regression testing. To check all the bugs are closed and nothing major components broke while fixing the defect.

  18. Smoke testing :- is an initial level of testing done before actual testing by QA is done. It test the basic functionalities of the software. if it fails the software is a failure.
    Sanity testing :- on the other hand is performed after retesting. It is done to check if the sysytem has acquired any new problem or any bugs has left unfixed. It is done to know the quick performance of the product

  19. Similarities:
    Both are part of initial testing
    Differences:
    Sanity testing is done when the developer or a tester wants to know the quick performance of the product whereas Smoke testing is done after the software is developed to check the critical functionalities of the software

  20. Similarities between smoke testing and sanity testing:
    Both are done at initial level.
    Both are basic and quick test done.
    Differences:
    Smoke testing: Testing is done after the software is developed to check the critical functionalities of the software. Primary goal is to verify the main application functionalities and to satisfy the product.
    Sanity testing: Testing is done when the developer or tester wants to know the quick performance of the product to show the minor changes in functions of the software does not affect the main requirement of the product.

  21. The smoke testing and sanity testing are two types of initial level testing.
    Sanity testing is done when the developer or a tester wants to know the quick performance of the product after minor changes.
    Smoke testing is done after the software is developed to check the critical functionalities of the software.

  22. Similarities:
    They are both initial level testing
    Differences:
    Smoke Testing-Testing done after the software is completed to see if the basic functionalities of the software behave properly.
    Sanity Testing-quick testing done to see if any new bugs appear in the software or if the previous bugs were never fixed.

  23. Smoke testing and sanity testing are both types of initial level testing- that is there common ground. The difference between them is that the smoke testing is to verify the main application functionalities of the system, the sanity testing though is the testing done by developers or QA to quickly verify if the software is performing or if any bugs left unfixed. Smoke testing is more comprehensive that requires more time testing and verifying if modules are working. Sanity testing is done to quickly check before retesting.

  24. Sanity and smoke testing both are initial level testing.
    Smoke testing is done to test functionality of software at initial level after it is developed eg login, sign up etc.
    Sanity test is done for performing quick test on software and to test initial level of functionalities in which the defects are fixed by developers.

  25. – Differences are:
    1. Smoke testing tests initial steps of each functionality whereas Sanity testing tests initial steps of the functionality in which defects are fixed.
    2. Smoke testing satisfies the main functionalities of the product and Sanity testing checks whether the system has acquired any new problem or any bugs has left unfixed.
    – Similarities are:
    1. Both the testing types test the main functionalities of the software, like links, buttons, etc

  26. The two types of initial testing are smoke testing and sanity testing. Both are used interchangeably. It is done to check the software readiness.

  27. Smoke testing and Sanity testing are two types of initial level testing.Smoke testing is done to verify the main application functionalities and to satisfy the product.it shows those errors which saves time and developer’s effort.Sanity testing is done to check whether the system has acquired any new problems which has left unfixed.sanity testing is also called as quick regression testing. Sanity testing is done when the developer or a tester wants to know the quick performance of the product. Smoke testing is done after the software is developed to check the critical functionalities of the software. Sanity testing is to show that minor changes in functions of the software does not affect to the main requirement of the product.

  28. Similarity:
    Both of testing is done at the initial level of software testing.
    Difference:
    Smoke testing is done to check the initial level of each functionality of the software. Like login functionality, link button etc. while Sanity testing is done to check whether defects are fixed or not.

  29. Smoke Testing: Is an Initial Level Testing. Smoke testing checks the initial steps of each functionality. It is also known as build acceptance testing. It makes software ready for Functional Testing. If a software has login, links, buttons pages etc, smoke level testing is done to check the basic functions of these pages and buttons.
    Sanity Testing: Is also a type of Initial Level Testing. It test the initial steps of functionalities in which defects were identified and fixed. For eg: In the login page there was an error in password reset and it was reported to the developer and it was fixed. Sanity test is now done to check the password reset functionality only.
    Smoke testing and Sanity Testing are Initial Level Testing. Smoke Testing is done to check crucial functionality where as Sanity Testing is done to check New functionality.

  30. Similarity:
    Both are initial level testing .
    Difference:
    Smoke testingsimilrities:
    Both smoke testing and sanity testing are intial leveltesting of the software.
    Differences:
    Smoke testing:
    it is done after the software is developed.
    It tests all the intial level functanalities. e.g., login, sign in, signup
    Sanity testing:
    It is done after the developers fix the bugs .
    it helps to verify whether all the bugs are fixed or newly added functionality of the software working.

  31. Smoke Testing and Sanity Testing are both types of Initial Testing. The primary goal of smoke testing is verify the main application functionalities and to satisfy the product. It shows those errors in the initial stages . Sanity Testing is is a basic or quick test done to the software.It is a part of regression testing or performed before retesting. It is done to check whether the system has acquired any new problem or any bugs has left unfixed.

  32. Smoke testing:
    it is done after the software is developed.
    It tests all the initial level functionalities.
    Sanity testing:
    It is done after the developers fix the bugs or add new functionality.
    it helps to verify whether all the bugs are fixed or newly added functionality of the software working.

  33. sanity testing and smoke testing both are initial level testing.
    Differences:
    Sanity testing is done when the developer or a tester wants to know the quick performance of the product. it is type of quick Regression testing.
    Smoke testing is done after the software is developed to check the critical functionalities of the software.
    Sanity testing is to show that minor changes in functions of the software does not affect to the main requirement of the product.

  34. Q1.1. Try to identify the differences and similarities between smoke testing and sanity testing.

    Ans. Before Functional testing there should be initial level of testing.Which is called Smoke testing or initial level of testing so that software is ready for functinal testing.

    Sanity Testing:- Suppose defects are identified at initial level and fixed by developer but before we release it to the client ,we perform another level of initial level testing which is called re-testing.So initial level of testing are defects are fixed are called sanity testing.
    Both smoke testing and sanity testing are done at initial level
    Smoke testing are done at initiaal level before any defects are fixed whereas as sanity testing are done after defects are fixed by developers and retested at initial level.

  35. smoke testing and sanity testing both are types of initial level testing.
    Smoke testing is done to check the functinality of software at initial level after the software is developed.
    sanity testing is done to check the initial level functionality in which the defects were found and fixed.If sanity test cases are failed then there is no point in testing further as the required features or functionality is not available.
    Similarities:
    1. Both smoke and sanity are used as criteria for accepting or rejecting a build. Smoke is done to check the crucial functionality. whereas, sanity to check the new functionality.
    2. Smoke is performed on relatively unstable product (initial builds) while sanity is done on stable builds.
    3. Once the build passes smoke, the next step would be Functional testing and then regression testing.
    4. For Sanity, if a new functionality is added then Functional testing and regression. If there is a bug fix its retesting and regression.

  36. Identify the differences and similarities between smoke testing and sanity testing.

    Smoke testing is the initial testing process exercised to check whether the software under test is ready/stable for further testing. The Smoke testing is typically executed by testers after every build is received for checking the build is in testable condition. This type of testing is applicable in the Integration Testing, System Testing and Acceptance Testing levels. However, Sanity tests helps to avoid wasting time and cost involved in testing if the build is failed. After completion of regression testing the Sanity testing is started to check the defect fixes & changes done in the software application is not breaking the core functionality of the software.

  37. Smoke Testing: Smoke testing is done after the software is developed to check the basic functionalities of the software. If it fails then it is considered as unstable.
    Sanity testing: It is done to check whether the system has acquired any new problem or any bugs has left unfixed. it is mostly done after fixing all bugs in the software.

    Both smoke & sanity tests are initial level tests. In the initial level testing software is tested for readiness before the detailed testing by QA team.

  38. Smoke Testing is a kind of Software Testing performed after software build to ascertain that the critical functionalities of the program are working fine. It is executed “before” any detailed functional or regression tests are executed on the software build.
    Sanity testing is a kind of Software Testing performed after receiving a software build, with minor changes in code, or functionality, to ascertain that the bugs have been fixed and no further issues are introduced due to these changes. The goal is to determine that the proposed functionality works roughly as expected. The objective of this testing is to verify the “stability” of the system in order to proceed with more rigorous testing
    similarity
    Both sanity tests and smoke tests are ways to avoid wasting time and effort by quickly determining whether an application is too flawed to merit any rigorous testing. The objective of the testing is to verify the “rationality” of the system in order to proceed with more rigorous testing

    Both smoke and sanity tests can be executed manually or using an automation tool. When automated tools are used, the tests are often initiated by the same process that generates the build itself.
    As per the needs of testing, you may have to execute both Sanity and Smoke Tests in the software build. In such cases, you will first execute Smoke tests and then go ahead with Sanity Testing. In industry, test cases for Sanity Testing are commonly combined with that for smoke tests, to speed up test execution. Hence, it’s a common that the terms are often confused and used interchangeably

  39. Differences between smoke testing and sanity testing:
    • Smoke testing is to test the basic functionality which is built in software.
    • Smoke testing is done after the software is developed to check the critical functionalities of the software.
    • Sanity testing is a basic or quick test done to the software when you don’t have enough time to do the other types of testing
    • Sanity testing is done when the developer or a tester wants to know the quick performance of the product.
    Similarities between smoke testing and sanity testing:
    The smoke testing and sanity testing are two types of initial level testing. In the initial level testing software is tested for readiness before the detailed testing by QA team.

  40. Difference: Smoke test verifies the basic that the implementations done in a build are working fine; however, sanity testing means to verify the newly added functionalities, buts are working fine.
    Smoke test is the first test on the initial build; however, sanity test is done when the build is relatively stable.
    Smoke test is done on every build; but sanity testing is done on stable builds post regression.
    Similarities: They are both done at the initial level of build release.

  41. 2. Try to identify the differences and similarities between smoke testing and sanity testing.
    The smoke testing and sanity testing are two types of initial level testing.
    Smoke Testing- Smoke testing is done to check the normal health of the build and make sure if it is possible to continue testing. It is done in the beginning of the software testing cycle.
    Sanity Testing- Sanity testing is done after thorough regression testing is over, it is done to make sure that any defect fixes or changes after regression testing does not break the core functionality of the product. It is done towards the end of the product release phase.

  42. identify the differences and similarities between smoke testing and sanity testing.
    Smoke testing is performed to ascertain that the critical functionalities of the program is working fine .sanity testing is done to check the new functionality / bugs have been fixed .Objective of smoke testing is to verify the stability of the system in order to proceed with more rigorous testing.Sanity testing objective is to verify the rationality of the system. Smoke testing is a sub set of Acceptance testing where as Sanity testing is subset of Regression testing. Smoke testing is usually documented . sanity testing is not documented.

  43. Similarities:The Smoke Testing and Sanity Testing are the Initial level testing.
    Differences are as follows:
    Smoke Testing:It is a type of system testing.The basic functionality of the software are tested after the software is developed.
    Sanity Testing:It is done when the developer wants to know the quick performance of the product.It is quick test done to the software when you don’t have enough time to do the other type of testing.

  44. Both smoke and sanity testing are types of initial level testing.
    Smoke testing is to verify the main functionalities of the software.
    Sanity testing is done when the developer or tester wants to know the quick performance of the product and to show the minor changes in functionalities of the software does not affect the main requirements of the product. it is also called quick regression testing.

  45. Smoke testing is initial testing performed after software build to make sure that the critical functionalities of the program is working fine or not.
    Sanity testing is performed after receiving a new build version to verify that there are no further issues introduced to the application after making any changes in the code or functionality or any bug fixes.

  46. Both types of testing are the intial level testing.
    Smoke test: tests initial steps of each functionality. Eg: login link, Valid pages link, buttons. Smoke testing is performedby developers and testers
    Sanity testing: tests intial steps of functionality in which defects are fixed.Sanity testing is performed by testers alone.

  47. Try to identify the differences and similarities between smoke testing and sanity testing.
    Smoke testing and sanity testing are both initial levels testing. It is done to test the system readiness.
    Smoke testing, the initial steps of the functionalities of the software are tested. If the initial steps have defects then the software is said to be unstable. The defects found are fixed by the developer within one or two days and they release the new version of the software. Only if the software passes the smoke testing , the functionality testing will be done.Example:
    ~Whether the user can login with valid credentials
    ~if the main/home page is opening with the URL
    ~ If the links and buttons are available on the main page
    Sanity testing, to test the initial functionalities of the software in which the defects were fixed. Example:
    ~ Forget password link wasn’t present. Now after the developer fixed the defect , the QA tests to see if the forget password link is present.

  48. Smoke Testing is performed to ascertain that the critical functionalities of the program is working fine.
    This testing is performed by the developers or testers.
    Smoke testing is a subset of Acceptance testing
    The primary goal of smoke testing is verify the main application functionalities and to satisfy the product
    Sanity testing is usually performed by testers
    Sanity Testing is done to check the new functionality/bugs have been fixed
    Sanity testing is a subset of Regression Testing.
    It is also called as quick regression testing.

  49. Similarities – Smoke testing and sanity testing are two types of initial level testing where software is tested for readiness before the detailed testing by QA team.
    Differences: Smoke testing is done to check whether the basic functionalities of the software are functioning. Eg: testing the main page, links to sign in, store details, search feature, etc. In Sanity testing, the QA checks whether the system has acquired any new problem or any bugs have been left unfixed. It is done to show that minor changes in functions of the software do not affect to the main requirement of the product. Smoke testing is done after the software is developed to check the critical functionalities of the software. Sanity testing is done when the developer or a tester wants to know the quick performance of the product.

  50. Differences and similarities between smoke testing and sanity testing.
    Sanity testing is done when the developer or a tester wants to know the quick performance of the product whereas smoke testing is done after the software is developed to check the critical functionalities of the software.

    Both are initial level testing.

  51. In Smoke testing all areas of the software application are tested without going into details. Sanity software testing is a narrow testing with a focus on one or a small set of areas of functionality or module of the software application.
    Smoke testing is done to ensure whether the main functions of the software application are working or not. Sanity testing is done whenever a quick round of software testing can prove that the software application is functioning according to business and functional requirements.
    Smoke testing of the software application is done to check whether the build can be accepted for thorough software testing. Sanity testing of the software is to ensure whether the requirements are met or not.

  52. Sanity testing is done when the developer or a tester wants to know the quick performance of the product.
    Smoke testing is done after the software is developed to check the critical functionalities of the software.
    Smoke testing and Sanity testing are both initial level testing.

Leave a Reply

Your email address will not be published. Required fields are marked *

Check Also

Close
Close