After smoke lets go for sanity testing

 SMOKE TESTING: Smoke testing is a testing process to check whether software which is being tested is stable for further testing. 

In order to perform smoke testing tester need to create few test cases prior to smoke testing. These test cases are written keeping in mind all major functionalities are covered but not in deep.

SMOKE---->SANITY---->WELL TESTED APPLICATION

These are executed to check whether critical functionalities of application is working or not, these test cases can be executed manually or automated as per project requirement, Smoke testing does not care about the detailed testing of each software modules it s on the important functionality of the application. It is executed every time new build ease to the tester to check whether the provided release is in testable condition or not, by that if the build is not stable tester can reject the release in the initial phase of testing. 

This type of testing is application while performing the Integration testing, system testing, and acceptance testing level. The various advantages of performing smoke testing are that it helps in finding issues in the integration of module in the early phase of testing that develops confidence in tester who is performing testing that issues which have been fixed in this build or not breaking the major functionality of the application.

AFTER   SMOKE, let's GO FOR SANITY TESTING: SO  PLEASE GO THROUGH SOME CATCHY POINTS OF SANITY TESTING:-

-Sanity testing follows narrow approach for each and every build.

-Its a subset of regression testing which tests failure impact on other modules.

-Its a narrow regression testing with a focus on the smalll set of areas of a software application.

-If build gives pass result for smoke tests then it comes under sanity testing.

-It comes into existence when we have the short period for testing the application.

-Sanity Testing checks major functionality with finer details

-This needs to be done when developer wants quick response according to change in the latest build

-It is mostly done after re-testing.

-Sanity Testing involves with scripts but this is not required for smoke testing.

-It is required when a time period is actually very small.

THANKS