Difference between sanity testing & smoke testing

 Sanity testing and smoke testing are two different types of software testing that are performed at different stages of the testing process. Here are the main differences between the two:

Objective: Smoke testing is performed to check the basic functionality of the software application, while sanity testing is performed to ensure that the new or modified features are working as expected and do not adversely affect the existing functionalities.

Scope: Smoke testing is a broader type of testing that covers a wide range of functionalities, while sanity testing is more focused and only covers specific functionalities or modules that have been added or modified.

Test Depth: Smoke testing is a shallow type of testing that only checks the surface-level functionality of the application, while sanity testing is a deeper type of testing that involves more detailed and comprehensive tests.

Timing: Smoke testing is usually performed at the beginning of the testing process, after a new build is created, to ensure that the application is stable enough for further testing. On the other hand, sanity testing is performed after smoke testing, when specific changes or enhancements have been made to the application.

Severity: Smoke testing is primarily focused on identifying critical defects or issues that could prevent further testing, while sanity testing is focused on identifying issues or defects that could affect the quality of the new or modified features.

In summary, smoke testing and sanity testing are two different types of testing that serve different purposes. Smoke testing is performed to ensure that the application is stable enough for further testing, while sanity testing is performed to ensure that the new or modified features are working as expected and do not adversely affect the existing functionalities.

Comments

Post a Comment

Popular posts from this blog

What is Smoke testing

Smoke testing is a type of software testing that is conducted to check whether the basic functionality of the software application is working or not. It is a preliminary test that is conducted to ensure that the critical components of the software system are functioning correctly after any major changes or updates. The term "smoke testing" comes from the idea of testing the software application just like a smoke test is done to check whether a machine is working or not. Smoke testing is performed after the build process to determine whether the build is stable enough for further testing. The main objective of smoke testing is to detect the major defects or errors that can cause the system to crash or not function correctly. It is a quick and easy test that is designed to identify any critical issues before proceeding with further testing. Smoke testing involves executing a few basic tests on the application, such as opening the application, logging in, navigating to different
Read more

java.lang.NoClassDefFoundError: groovy/lang/GroovyObject (issue for Rest Assured project in Eclipse)

Code: import org.testng.annotations.Test; import io.restassured.RestAssured; import io.restassured.response.Response; public class AppTest { @Test public void test_01() { Response response = RestAssured.get("https://reqres.in/api/users?page=2"); System.out.println(response.getStatusCode()); System.out.println(response.getTime()); } } ...................................................................................................................... Error message: [RemoteTestNG] detected TestNG version 6.14.3 FAILED: test_01 java.lang.NoClassDefFoundError: groovy/lang/GroovyObject at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(Unknown Source) at java.security.SecureClassLoader.defineClass(Unknown Source) at java.net.URLClassLoader.defineClass(Unknown Source) at java.net.URLClassLoader.access$100(Unknown Source) at java.net.URLClassLoader$1.run(Unknown Source) at java.net.URLClassLoader$1.run(Unknown S
Read more

Examples of Sanity testing

Examples of sanity testing: Web Application : In the case of a web application, sanity testing can involve testing the specific modules or functionalities that have been added or modified. For example, if a new payment gateway has been integrated into the application, sanity testing will focus on verifying whether the payment gateway is working correctly, the payment data is being stored securely, and the transaction is being processed without any errors. Mobile Application : In the case of a mobile application, sanity testing can involve testing the new features or modifications that have been made to the application. For example, if a new feature for push notifications has been added to the application, sanity testing will focus on verifying whether the notifications are being sent correctly, the notifications are being received on time, and the user can disable the notifications if required. API : In the case of an API, sanity testing can involve testing the new endpoints or modific
Read more