What Is Sanity Testing Explain It with Example?

Sanity Testing is the subset of Regression Testing and it is performed when we do not have enough time for doing testing.

Sanity testing is the surface level testing where QA engineer verifies that all the menus, functions, commands available in the product and project are working fine.


Sanity Testing Example

For Example in a project there are five modules like login page, home page, user detail page, new user creation, and task creation etc. So we have the bug in login page like on login page username field accepts the less than six alpha-numeric characters which are against the requirements as in requirements it is specified that username should not be below than six characters but as username accepts the less than six characters it is the bug.

So now the bug is reported by the testing team to the developer team to fix it. When the developing team fixes the bug and passed it to testing team than the testing team checks the other modules of the application means checks that fix bug does not affect the functionality of the other modules but keep one point always in mind that testing team only checks the extreme functionality of the modules, do not go deep to test the details because of the short time so this is the sanity testing.  

Sanity testing is performed after the build has clear the Smoke test and has been accepted by QA team for further testing, sanity testing checks the major functionality with finer details.

When we Perform Sanity Testing?


Sanity testing is performed when development team needs to know quick state of the product after they have done changes in the code or there is some controlled code change in a feature to fix any critical issue, and stringent release time-frame does not allow complete regression testing.

Conclusion:

Sanity testing will be done mostly after retest (retest will be done after fixing the bug). We always use Script for Smoke but do not for sanity.

Related Post

Complete Difference Between Sanity and Regression Testing

15 comments:

  1. awesome! explanation!

    ReplyDelete
  2. Very simple and understandable.

    ReplyDelete
  3. I would like to say that is a subset of Acceptance testing. Regression testing is run very often when code is changed. But Sanity is run from time to time, e.g. when we want to release a product to users.

    ReplyDelete
    Replies
    1. Thanks for the simple explanation.....

      Delete
  4. Wow..Superb..Thank u so much !!

    ReplyDelete
  5. At first read , I understood it clearly, thanks!

    ReplyDelete
  6. super explanation boss. thanks u for sharing ur exp
    with us

    ReplyDelete
  7. Fine but after resolve the bug by developer team .Is there need of any re-testing or confirmation testing for testing team. mean which testing have to perform .pls mention your thought

    ReplyDelete
    Replies
    1. Retesting then Regression testing

      Delete
  8. Fine but after resolve the bug by developer team .Is there need of any re-testing or confirmation testing for testing team. mean which testing have to perform .pls mention your thought

    ReplyDelete
  9. hi,I have confusion in definition of sanity testing .I read some where sanity testing mean test the newly released functionality in depth,please here something different .plz clear my confusion.bcoz this question mostly ask in interview.thanks

    ReplyDelete
  10. sir pls provide with real time example code to my email beesetti@gmail.com

    ReplyDelete
  11. i found a bug in a module at the last day before release.. i have 500 regression Test case.. Developer fixed and passed to the QA team.. should i again run all my 500 Test cases or test cases only for the particular defect. Pls share ur answer.. thanks in advance

    ReplyDelete
  12. It is done after the regression testing ,to check the core functionality of the project should be working properly or not.

    It is done at the time of project release.

    ReplyDelete

Related Posts Plugin for WordPress, Blogger...