diff between smoke testing and sanity testing
Answers were Sorted based on User's Feedback
Answer / 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 |
Answer / samsirsameer
Smoke Testing:
Also called as BVT 'Build Verification Testing'
Done every time a new build is received to verify whether
the basic functionlaity is working fine or not.
Example, page navigations, all tabs, entities creation,
updations, deletions.
Usually done by Automation engineers whenever a new build
is recieved.
Sanity Testing: Testing major functionalities of the system
to ensure whether we can proceed further testing with the
build.
Example: We encountered a showstopper bug (blocking major
part of the application under test) and it was fixed and
given to QA. The QA will do a sanity test around that fix.
Thanks, SamsirSameer
Is This Answer Correct ? | 4 Yes | 0 No |
Answer / chandra sekhar
Smoke Testing...testing the basic features of application
are present with out any failure based on screenshot/FS
document.
Sanity Testing:Testing...Basic functionalities..(check
box..list box...buttons...etc.) are working or not...in an
application.
Is This Answer Correct ? | 1 Yes | 0 No |
Smoke Test is scripted wheras Sanity Test is unscripted.
Smoke Test is shallow and wide coving all arears but not in
depth.
Sanity Test is Narrow and deep. To check the particular
module is working fine after changes (Form of regression
Tesing)
Smoke test is like build verification test
Sanity test is to check application functioning acc to
requirement.
Vinodh Anandhan
Software Tester
Exceed Technologies (P) Ltd.,
Chennai - 87
vinodh.anandhan@exceedintl.com
Is This Answer Correct ? | 2 Yes | 1 No |
Answer / chaithanya abk
thats a very gud answer Mr.Rajendra Prasad Reddy .. A good
explanation indeed , appriciate ur effort ..
Is This Answer Correct ? | 1 Yes | 0 No |
Answer / rahul
I dont understand why rajendra is always not satified with
the answers of sujata....agreed that she doest gives to the
point answer ..but you should encourage her man
Is This Answer Correct ? | 1 Yes | 1 No |
Answer / vishal
Sanity Testing:
Sanity testing is initial level of testing efforts to
determine if a new version of build is performing well
enough and accepted it for further testing activity..
Smoke Testing:
Smoke testig is initial build acceptance test. Here we
atest the major functionalities of the build, if the some
test is passed then it will goes for further testing
activity...
Vishal
Quality Analyst
Is This Answer Correct ? | 1 Yes | 1 No |
Answer / aravind
santity testing: after release the build to testing department
what ever doing test engg is called sanity testing..
smoke testing: in fiew companies before going to release the
build to testing depa the develpoer checks where build is
correct or not is called smoke testing
make me if am wrong
Is This Answer Correct ? | 0 Yes | 0 No |
Answer / naveen.a
hii rajendra prssad reddy,
I think the aswer wat u have posted regarding smoke and
sanity testing is good.But if we go in depth,both the tests
are same.You will test the build(i mean for smoke testing)by
checking the functionalities only na...which is same as the
answer u gave for sanity testing.....
Is This Answer Correct ? | 0 Yes | 0 No |
Smoke Testing: As soon as we receive build, to check whether build is executable are not, where to check major functionalities are working are not in order to check wheather we go for further testing are not
Sanity testing: performing testing on major and minor functionalities of the application are working fine are not
Is This Answer Correct ? | 0 Yes | 0 No |
pls tell me who is in s/w testing field(either in company or as faculty) give the ans of my que. tel me why r u in testing ? reply me as soon as possible
Explain in detail whole test process activities.
why tracability matrix need in manual testing? how to create tracebility matrix for web application.. please can u send ur replies
What is your daily process? and roles and responsibility? please answer this question this is very imp question. I am putting 2+years of experience.
While Testing the Web application & Desktop Application What Difference did u find ? Tell me in details.
Who design the test case templates?
What is the actuall process of Smoke and Sanity Testing in companies
What is the difference between bug , error and defect ? Explain with example. 2... What is diff between test approach , test strategy, Test plan and test methodology documents? 3...How to test a website with manual testing? 4. What methodologies have you used to develop test cases?
13 Answers Infosys, SCI, Wipro,
What are the Testers Responsbile?
What is Software Testing? Objectives of Testing?
what is build and release?
how do i write perfect test case for functional testing