October 9, 2017 at 2:43 pm #17719@tassaweraminOnly available when logged in
It is always confusing to understand the difference between smoke and sanity check.
Can anyone explain what is the difference between both and may be with the help of an example would be really helpful.October 11, 2017 at 9:44 am #17735October 19, 2017 at 8:02 am #17851@kristersOnly available when logged in
I think that, as usual, it can mean different to different people. They could mean the same. For me a smoke test is a test that checks if a release is stable enough to start structured testing, like a go/no-go decision.
the value of the test would be to not invest in heavy testing before you know it will be worth it. I like to do things in an sequence.
Check new functionality
I guess Sanity check could be an extended smoke test. The word sanity could imply that you check release notes, review status etc.
/KristerOctober 28, 2017 at 10:54 am #17922@web-eurostareuro-point-co-ukOnly available when logged in
I have always used the two terms interchangeably. The link @archana gave is an example where someone has tried to make a distinction, which in my view, is unnecessary.
If you look at the glossary that the ISTQB have put together (edited by Eric van Veenendaal, and including contributions from such people as Rex Black, Isabel Evans, Dorothy Graham, Stuart Reid and Mike Smith amongst many others), there is absolutely no distinction between the two.
The definition given by the ISTQB is:
A subset of all defined/planned test cases that cover the main functionality of a component or system, to ascertaining that the most crucial functions of a program work, but not bothering with finer details.
A searchable version is also available.October 29, 2017 at 8:03 am #17925@anubhavOnly available when logged in
Well every person have there own thoughts about this. So As per my understanding :
Smoke Testing : Smoke testing is the initial testing process exercised to check whether the software under test is ready /stable for further testing. Smoke testing is a type of software testing which ensure that the major functionalities of the application are working fine. This testing is also known as “Build verification testing “.
Ex : If any application have login window and after login we can continue further task then first we need to check that user is able to login with valid username and password or not. if its pass then mean smoke testing is pass. Because next we can continue another process.
this is the very simple example of smoke testing. there are lots of more example. its depend on the website functionality.
Sanity Testing : Sanity testing is performed after receiving a software build, with minor changes in code or functionality to confirm that the bugs have been fixed and there are no further issues introduced due to new changes. The objective is to determine that the recommended functionality works as expected. Sanity testing is a sub-set of regression testing.
For Ex : Like for Example we have bugs fixed in module like : Student Adding Details page, login page etc. so we need to check complete these two module and sure that there are no bugs remain related to these module.
This is my own thoughts. Every person have different.October 30, 2017 at 11:50 am #17930November 13, 2017 at 12:52 am #18052@michaelaboltonOnly available when logged in
There is no difference between the two, or the two are entirely different depending on your context. You get to decide.
The ISTQB says that there’s no difference between the two, but they can’t back that up in your organization if someone there who’s running things says there is. I claim that there might be a difference between the two, and it might even be meaningful, but that doesn’t matter if someone who matters in your organization says that there’s no difference. There is no authority over the way you or your organization go about your business—even in a regulated environment, you can have one set of terms internally and a different set for the auditors.
You must be logged in to reply to this topic.