what is the difference between sanity and smoke testing?
Answers were Sorted based on User's Feedback
Answer / varma
Smoke Testing:This is also Called Build verification
testing means we can test the major functionalities of the
application .if it is not working we reject the
build.i..e., the is is not in testable condition
Sanity testing:We can test each and every functionality is
working corrctly or not.(means we can test major and minor
(each and every)fuctionalities of the application)
Mail me if u r having any doubts
ysvrvarma@gmail.com
9949642465
| Is This Answer Correct ? | 5 Yes | 0 No |
Answer / keerti(aditi)
Sanity test:
It determines whether it is reasonable to continue testing.
A sanity test is usually unscripted.
A Sanity test is used to determine a small section of the
application is still working after a minor change.
smoke test:
Smoke test determines whether it is possible to continue
testing.If this fails its impossible to undergo or have
sanity testing.
A smoke test is scripted, either using a written set of
tests or an automated test.
A Smoke test is designed to touch every part of the
application in a cursory way. It’s shallow and wide.
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / akram khan
Sanity Testing:- it is like a specialized health checkup.
Smoke Testing:- it is like a General health checkup.
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / naina
Smoke testing means to check the testability of an application as soon as build is released for testing
And
Sanity testing include executing key end to end functional test cases.
They both are same considering their purpose.
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / princy
There is no difference in between sanity and smoke. Both
are same.Smoke testing checks if all the pages are properly
working. Sanity testing checks if all pages are displayed
properly and properly working,
| Is This Answer Correct ? | 1 Yes | 2 No |
Answer / ramumcato
Hi Varma, for these type of questins, we can give answer
with eample so that it can be easily understandable. can
you give a small example please.
Raam
| Is This Answer Correct ? | 0 Yes | 1 No |
Answer / anamika singh
smoke testing is also known Built verification test.smoke
testing is perform at the developer end to check the
stability of application ,whether the application work
without any hangout or not.
sanity testing is perform at testers end.It is done accross
a built.it focuses on few areas of mojor functionality
where changes has been done
| Is This Answer Correct ? | 0 Yes | 1 No |
Answer / sandeep15october
hey princy go throgh google and cnfrm it
| Is This Answer Correct ? | 0 Yes | 2 No |
Answer / sapna
sanity testing is also called build acceptance testing(BAT)
or build verification testing(BVT)
it is a testing where overall testing is performed on the
application whether it is possible for detailed testing or
not
this sanity testing is done by the testers when the build
is released(to accept or reject)
so, before releasing the build the same thing was done by
the developers to check whether it is working properly or
not.it is called smoke testing
| Is This Answer Correct ? | 1 Yes | 3 No |
Answer / dasari............
hi smoke is negative perception
sanitary is the positive perception
smoke test is done by devolopers
sanitary is done by test engineer
these both tests maximum same but slite different
this is my opinian
dasari.............
| Is This Answer Correct ? | 0 Yes | 3 No |
how can we do database testing. In database testing we verify the data integrity and data validation. how can we do testing of Index, triggers, views, ransactions,cursors etc
What are the review documents used for testing?
What is call-pair?
This question has been asked in my recent inerview with Adithya Birla Group.When to prepare System test plan after getting build or before getting build?
difference Between Quality assurance and Quality control
About Testing Methodology?
what is JOINTS & REGISTRY in SQL?
What's Click-stream measurement tests
What is the difference bt QA and QC
What is "pet model" of Bug reporting cycle
user A done some changes for a portion of test case doc. And user B also done some changes to same portion. If user-A checks in his file first then user-B. Then what is the state of that file?
Example of high severity and low priority bug