Testing Done in Limited Time Sanity Testing

Posted By : Palak Tiwari | 28-Dec-2017

    

Sanity Testing (short process of regression testing)

It is a part of regression testing.

It is also known as surface-level testing meaning that a tester checks the whole functionality of the software works in a proper way. It's a limited time testing. Sanity testing is done if we have small time for testing.

Sanity testing is not cost effective.On the other hand regression testing is long duration testing. Testers should be aware of product details. Regression testing is more detailed. Codes are used for regression testing but not for sanity. sanity testing is outlined view of regression testing if time is less than tester can easily follow this type of testing.

Important  facts of Sanity testing:

1.Sanity testing goes with the narrow and deep approach with detailed testing of some limited features.

 

2.Sanity testing is another form or part of regression testing.

 

3.It is a small view of regression testing.Sanity testing is outlined testing to assure application is working as mention in the specification documents & reach its level of testing.

 

4.Sanity testing is used to verify either requirement meet its timeline or not

 

5.It basically checks after minor fixes, the small section of code or functionality is fine or not.

 

WHEN IS SANITY TESTING DONE?

 

-This testing is a narrow line regression test that focuses on one or a few areas of functionality. Sanity testing is basically narrow and deep. It's an unscripted testing. It works on a small section of the application.Sanity Testing checks whether the application works due to a minor change or not.

Sanity Testing (A Specialized Health check-up)

Irrespective of Testing, the Sanity check is a basic concept – which simply check if the produced output is rational (that the product’s creator was thinking rationally, applying sanity).  Hereafter each and every small change in a build Sanity testing is just to certify that each  small changes are working as expected. If sanity test gives a fail result, then build is not considered and it will save both time and costs.

 

Some differences between Smoke and Sanity Testing:--------

 

Smoke Testing is done to sure that the build we get from the development team is testable or not.

Sanity Testing is done in the release phase.It will check for the major functionalities of the application without going in depth.

 

Both Developers and Testers can perform smoke testing.

Sanity Testing is performed by Testers alone.

Smoke Testing roams the entire application from one end to another end.

Sanity Testing roams only the specific component of the whole application.

Smoke Testing, sometimes build is stable or sometimes build is unstable.

Sanity Testing, build is comparatively stable.

 

 

THANKS

Related Tags

About Author

Author Image
Palak Tiwari

Software tester with good knowledge testing skills in various areas. She believes in continuous learning .

Request for Proposal

Name is required

Comment is required

Sending message..