Software Testing Tutorial in Hindi - Smoke Testing Vs Sanity Testing in Hindi
Вставка
- Опубліковано 15 гру 2024
- In this video, I have explained about Difference Between Smoke and Sanity Testing. I have tried to explain the Theoretical and Practical differences between smoke testing and sanity testing. How are we need to explain smoke vs sanity in Interviews and what is a real-time difference between smoke and sanity testing?
What is Smoke Testing?
Smoke Testing is a software testing technique performed post software build to verify that the critical functionalities of software are working fine. It is executed before any detailed functional or regression tests are executed. The main purpose of smoke testing is to reject a software application with defects so that QA team does not waste time testing broken software application.
What is Sanity Testing?
Sanity testing is a kind of Software Testing performed after receiving a software build, with minor changes in code, or functionality, to ascertain that the bugs have been fixed and no further issues are introduced due to these changes. The goal is to determine that the proposed functionality works roughly as expected. If sanity test fails, the build is rejected to save the time and costs involved in a more rigorous testing.
✅💡For Appointments with me: calendly.com/f...
✅💡 If you like my videos, please consider buying me a coffee: www.buymeacoff...
✅ 💡For business write us on: Contact@fundootesters.com
Topics Covered:
What is software testing? bit.ly/3xYFIfg
SDLC Model: bit.ly/3hAwjon
Waterfall Model: bit.ly/2T6xQsJ
Prototype Model: bit.ly/3r4ApYV
Spiral Model: bit.ly/2U6BseT
V Model: bit.ly/36xXTw0
Hybrid Model: bit.ly/3wDY0AR
White box vs Black Box : bit.ly/3izgw8j
White box Testing: bit.ly/3kBkNLj
Functional Testing: bit.ly/3zlrs06
Integration Testing: bit.ly/3rn287r
System Testing: bit.ly/3zlFdMw
Smoke Testing: bit.ly/2UVPdgZ
Adhoc Testing: bit.ly/3zW86PJ
Regression Testing: bit.ly/3iX3r9e
Acceptance Testing: bit.ly/3icRaOH
Compatibility Testing: bit.ly/2VJtSY8
STLC: bit.ly/37yJaBs
What is Test Plan: bit.ly/2VKll71
Defect Life Cycle: bit.ly/3CByIaT
Test Case Review Process: bit.ly/3fOqkuW
Severity vs Priority: bit.ly/3jDx53O
-How to create test plan: rb.gy/2ejfc9
-How to write smoke test case : rb.gy/qq31o7
-Web Application testing approach : rb.gy/hqmxsn
-Mobile Application testing : rb.gy/xqlcl3
-How to raise a defect(bug) using google spreadsheet? : rb.gy/zjvoxg
Say hello to us, and stay updated!
✅ Facebook: / fundootesters
✅ Instagram: / fundootesters
✅ LinkedIn: / fundootesters
✅ Blog: fundootesters.com/
GEAR USE:
○ My Camera: amzn.to/3e2UqL7
○ Microphone: amzn.to/3bSUvOq
○ Microphone:amzn.to/2ZXuo3s
○ Tripod: amzn.to/2PqmTQN
DISCLAIMER
Links included in this description might be affiliate links. If you purchase a product or service with the links that I provide I may receive a small commission. There is no additional charge to you! Thank you for supporting me so I can continue to provide you with free content each week!
#smoketesting #sanitytesting #fundootesters
I have a lot to learn from your video. It is very helpful@
Please make a video on Automation testing
Will do soon
Sir aap bhut hi acche padhate ho similar automation testing ke bhi full course ke video bnao. Aapka sikhane ka trika bhut accha hai
Yes we are working on it.
mujse interviw may pocha gia k smoke vs sanity testing may kia difference hai ?
You can explain same
What is difference between manual and software testing
Question hi galat hai socho aur fir se pucho
Thanks for explain in details.... Keep doing
🙏
For example sir if we doing smoke testing when we get build first time and in that we find any bug in critical functionality at the time of smoke testing.
Then we assign that bug to developer and after fixing bug developer provide tester that build again for retesting so when after fixing bug we again testing that build so can we say that sanity testing???
Because then we focus on that bug only and not wasting time to focus previous functionality which passed at smoke testing time successfully .
If you find critical bug during smoke thn ideally testing team reject the build. Dev team will fix on priority and provide same build again.
Again testing team has to start with smoke on same build(which has bug fixed)
@@FunDooTesters thanx sir for reply and explanation
Tester perform smoke testing after unite testing and before integration testing?
If is right that means smoke testing perform every module build pls reply sir
After receiving every new build
when build is not stable then what are yu done
Dev team will provide quick fix
which testing perform after development process complete
It help me very much
Who decides whether we need to do smoke or sanity testing??
har kisine muje confuse kar rakha hai, smoke and sanity k naam pe 😂
True 🤣🤣😅😅
Thank you sir ❤️..
We are getting the content in portal also
Means, is that cms
Helpful❤️
Thanks you sir
Just a feedback Sir please try to explain little bit faster 😅
Sure. Thanks Kuljeet
1.5x pe daal de kullu