These are very clear examples of when to use smoke testing and sanity testing. People always tend to use these terms interchangeably or run both smoke and sanity tests every time although there should be a clear condition when we should stop allocating resources and time to the smoke test so we can focus on what's next.
Hi Pramod, I think smoke testing comes under acceptance testing because here we are making sure that whether S/W or application is applicable for further testing or not and sanity testing is subset of regression testing because it comes later once application is sane or stable.
In Internet many people talk about this and they are saying they will clear the doubts about smoke vs sanity. Atlast both looks like same. No one is giving proper difference with good example. In History, Some dumb people used terms smoke and some people used sanity. Because of these two terms everyone is getting confusion. its better no one should ask this question in Interview. Both sounds same. somewhere they would say smoke is scripted and somewhere they would say smoke is done at the early stage. I suggest you just forget this topic and concentrate on other topics. Till today no one has given proper explanation with good example. All are reading some article in internet and they are explaining same in different style. could anyone of you explain diff bn smoke and sanity with real time examples? while answering please use simple English and Do not use words like rigorous, general health check up, scripted, sanity is subset of regression which leads to lot of confusion. Explain each difference with example.
Sir you told smoke testing is used to check whether software is fit for testing or not but y we need to check the trasnsction and gui ? These all internal functionality isn't it sir ?
These are very clear examples of when to use smoke testing and sanity testing. People always tend to use these terms interchangeably or run both smoke and sanity tests every time although there should be a clear condition when we should stop allocating resources and time to the smoke test so we can focus on what's next.
Hi Pramod, I think smoke testing comes under acceptance testing because here we are making sure that whether S/W or application is applicable for further testing or not and sanity testing is subset of regression testing because it comes later once application is sane or stable.
In Internet many people talk about this and they are saying they will clear the doubts about smoke vs sanity. Atlast both looks like same. No one is giving proper difference with good example. In History, Some dumb people used terms smoke and some people used sanity. Because of these two terms everyone is getting confusion. its better no one should ask this question in Interview. Both sounds same. somewhere they would say smoke is scripted and somewhere they would say smoke is done at the early stage. I suggest you just forget this topic and concentrate on other topics. Till today no one has given proper explanation with good example. All are reading some article in internet and they are explaining same in different style.
could anyone of you explain diff bn smoke and sanity with real time examples? while answering please use simple English and Do not use words like rigorous, general health check up, scripted, sanity is subset of regression which leads to lot of confusion.
Explain each difference with example.
Facing same.. Almost everyone confuses so better is tell its almost same smoke is just advance version of sanity testing..
This was useful for me from IT Project Manager standpoint
Amazing, this is success for me,
Sir you told smoke testing is used to check whether software is fit for testing or not but y we need to check the trasnsction and gui ? These all internal functionality isn't it sir ?
Which testing done first ??
Hello bro,
u have done a great job. 👍👌
Is it necessary to do smoke testing always??
Depends on the requirements
sir please make a video difference between smoke and system testing
Its already there.
They sound like the exact same thing