Thank god. At last someone explained with real time example. In order to understand this, I waited almost 6 years. Now got the clarification. Thanks man for your nice explanation with real time example. Now I am feeling only this is the difference ah? for this I waited for 6 years ah? Finally ufff. I can stop to search on this topic. For this nice explanation, I am subscribing you.
Hello sir you said that the checking the core functions is called smoke like checking purchase, home, login ok Sanity means checking new update, new function or error fixing ok While there is a error fixing in purchase or a home button is it sanith
Hello, thank you for the explanation. I have a question, is the Sanity testing the same as feature testing/functional testing or we just check new feature on high level? I understand that Sanity is type of Functional testing, but it is not clear for me what the difference when we run written TCs to check that feature work and when we run Sanity? Could you, please, explain? It will be really appreciated.
Sanity is same as functional but just checking the main functions not others For example: order module , checking just order creation is sanity . If you do order create edit cancel return order means it will be functional testing
In order to Accept or Reject the build promoted from "Dev Environment" to "QA Environemnt" when some extra new features are added + there is a bug fix which came along with the build , 1. We should do the Sanity Testing for the specific bug fix , and Smoke Testing for one complete core flow of the application (or all positive cases or Just some ??) . 2 . But then , I am getting confused Sanity with Retesting , and Smoke with Regression Testing. Please clarify with context to the example taken by me
Good. Retesting is just bug fix test, not new functionality testing. and regression means core feature with all the scenarios. But smoke just core functionality positive flow.
very good explanation sir really liked it thank you
Clear
This was very helpful for me😇
Glad it helped
Thank you so much... Explained very clearly
Well explained with example.
Another analogy is
Smoke testing is like regular health check up, sanity is like specific health issue check.
Useful comment bro... Easily understand by u r comment..
Thank god. At last someone explained with real time example. In order to understand this, I waited almost 6 years. Now got the clarification. Thanks man for your nice explanation with real time example. Now I am feeling only this is the difference ah? for this I waited for 6 years ah? Finally ufff. I can stop to search on this topic. For this nice explanation, I am subscribing you.
Hello sir you said that the checking the core functions is called smoke like checking purchase, home, login ok
Sanity means checking new update, new function or error fixing ok
While there is a error fixing in purchase or a home button is it sanith
Nice explained 👌
Well explained 👍
Smoke testing one video of other example of bike
Hello, thank you for the explanation. I have a question, is the Sanity testing the same as feature testing/functional testing or we just check new feature on high level? I understand that Sanity is type of Functional testing, but it is not clear for me what the difference when we run written TCs to check that feature work and when we run Sanity?
Could you, please, explain? It will be really appreciated.
Sanity is same as functional but just checking the main functions not others
For example: order module , checking just order creation is sanity .
If you do order create edit cancel return order means it will be functional testing
Is seems sanity testing is same as retesting because in retesting we also check whether the bug fixed or not.... Please help me with this daut Sir.
In order to Accept or Reject the build promoted from "Dev Environment" to "QA Environemnt" when some extra new features are added + there is a bug fix which came along with the build ,
1. We should do the Sanity Testing for the specific bug fix , and Smoke Testing for one complete core flow of the application (or all positive cases or Just some ??) .
2 . But then , I am getting confused Sanity with Retesting , and Smoke with Regression Testing. Please clarify with context to the example taken by me
Good. Retesting is just bug fix test, not new functionality testing.
and regression means core feature with all the scenarios. But smoke just core functionality positive flow.