Smoke Vs Sanity Testing

Smoke Testing

Price: INR 8,999.00
Price: INR 15,999.00
Was: INR 16,999.00

Smoke Testing is done to ensure that whether the build can be accepted for through software testing or not. Basically, it is done to check the stability of the build received for software testing.

 

Smoke Testing verify that the critical functionalities of the program are working fine or not.

Smoke is executed “before” any detailed functional or regression tests are executed on the software build.The purpose is to reject a badly broken build.

Smoke vs Sanity Testing

 

Sanity Testing : Sanity testing of the software is done at later cycles after through regression test cycles. If we are moving a build from staging / testing server to the production server, sanity testing of the software application is done to check that whether the build is good enough to move to further at production server or not.

Sanity testing of the software is done at later cycles after through regression test cycles. If we are moving a build from staging/testing server to the production server, sanity testing of the software application is done to check that whether the build is good enough to move to further at production server or not.

Sanity testing of the software is done at later cycles after through regression test cycles. If we are moving a build from staging/testing server to the production server, sanity testing of the software application is done to check that whether the build is good enough to move to further at production server or not.

 

After receiving a software build, with minor changes in code, or functionality, Sanity testing is performed to verify that the bugs have been fixed and no further issues are introduced due to these changes. If sanity test fails, the build is rejected to save the time and costs involved in a more rigorous testing.

The objective is “not” to verify thoroughly the new functionality.

 

Difference between Smoke & Sanity Software Testing

  • Smoke testing is, where all areas of the software application are tested without getting into too deep. However, a sanity software testing is a narrow regression testing with a focus on one or a small set of areas of functionality of the software application.

  • Smoke Testing is documented and scripted Sanity testing is nor documented neither Scripted.

  • Smoke testing is done to ensure whether the main functions of the software application are working or not. Sanity is done whenever a quick round of software testing can prove that the software application is functioning according to business / functional requirements.

  • Smoke testing of the software application is done to check whether the build can be accepted for through software testing. Sanity testing of the software is to ensure whether the requirements are met or not.

  • Smoke testing is to check entire build and sanity is to exercise only the particular component of the entire system.

 

0 Comment

Leave a Reply