Skip to main content

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

Labels:

Comments

  1. AnonymousJuly 19, 2013 at 11:11 AM

    awesome! explanation!

    ReplyDelete
  2. AnonymousSeptember 17, 2013 at 3:56 PM

    Very simple and understandable.

    ReplyDelete
  3. AnonymousOctober 30, 2013 at 8:38 PM

    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. AnonymousJanuary 10, 2014 at 3:49 PM

      Thanks for the simple explanation.....

      Delete
  4. AnonymousNovember 27, 2013 at 9:45 AM

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

    ReplyDelete
  5. Khyati SehgalMarch 20, 2014 at 12:34 PM

    At first read , I understood it clearly, thanks!

    ReplyDelete
  6. AnonymousSeptember 17, 2014 at 4:43 PM

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

    ReplyDelete
  7. Arjun singh fresherFebruary 13, 2015 at 10:22 PM

    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. AnonymousMarch 31, 2015 at 3:21 PM

      Retesting then Regression testing

      Delete
  8. Arjun singh fresherFebruary 13, 2015 at 10:23 PM

    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. kshreeJune 26, 2015 at 6:25 PM

    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. maddySeptember 22, 2015 at 11:48 PM

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

    ReplyDelete
  11. AnonymousDecember 12, 2015 at 4:03 PM

    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. AnonymousDecember 14, 2015 at 5:10 PM

    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
  13. UnknownJuly 27, 2016 at 3:42 PM

    superb article..thanks..

    ReplyDelete
  14. AnonymousJuly 16, 2018 at 7:40 PM

    Very nice and lucid explanation without much use of technical jargon.

    ReplyDelete
  15. UnknownAugust 20, 2018 at 10:34 AM

    Sir can you provide all interview questions in my mail id ashishnkd@gmail.com

    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