diff between smoke testing and sanity testing
Answer Posted / rajendra prasad reddy penumall
Dear Sujatha
smoke testing and sanity testings are not same in real.
ofcourse some companies may treat both are same but you
cannot give this answer in intervew.
to avoid Unnecessary confusion,you must know the root from
where these words are originated.
here the word Smoke testing is barrowed from electronics
testing industry.
In electronic manufacturing process after designing the
circuit they will put it for testing.
if there is any fault or miswiring or Miscontacts are there
in circuit then smoke comes out from the circuit.
This testing is called a Smoke testing.
In software industry after build is released from
development team it will be installed in the test server or
testers PC.
Initial test will be conducted to to check the Build
stability by checking the software properly working without
any hangings .
The software navigation controls must work smoothly.
so this can be called Build verification Testing or in a a
short form BVT.
If you come for Sanity testing,This is also called tester
Acceptence testing.
This is to determine, Whether the supplied build is
testable or not,
So Smoke Test -Build Verification Test(BVT)
Sanity Test -Tester Acceptence Test(TAT)
these are the very first tests conducted by the testing
team.
Also called as level -zero tests in STLC.
If you still have any doubt feel free to mail me at :
rajendra_penumalli@yahoo.com
or call me:9885162742
| Is This Answer Correct ? | 9 Yes | 2 No |
Post New Answer View All Answers
what is acid testing?
Hi Could someone please provide Siebel Testing Interview questions for 5 years exp.
I have an Interview about Guidewire claimcenter,so could you provide any info regd it?.I would really appreciate any kind of help- email at hvshah2001@gmail.com
Write a Test scenario for Outlook Search functionality.
What is bidirectional traceability ??? and how it is implemented
You have a testing team of 10 members, and now you have to reduce it by 5 member and you dont want to increase risk in your product, you are try to cover all functionality to test. What test Strategy you follow.
Give an example for pre testing and post testing ?
What's the difference between alpha and beta testing?
What is a defect age?
How can a LOG for testcases be maitained which can give information about a TestCase that is it new one or has been occured in previous versions of the software.
What is baseline testing?
what is the impact analysis?
What is bug priority?
write test case for gmail sign up page ?
Write UI Test case, Integration Test case, Functional Test case & Performance Test case for the File Menu for MS-Word?