What is the diff. between Sanity , smoke and ad-hoc testing?
- 8 Answers
- 31054 Views
- I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / sravan kumar.p
Smoke testing: checks whether the application is ready for further major testing and working without dealing with the finer(more) details.
Sanity testing: done prior to release as final inspection and after applying minor patches.
Ad-hoc testing: It is a testing technique done by end users .
without any defined process,proper planning,no specified rules required. Least formal method of testing
| Is This Answer Correct ? | 10 Yes | 3 No |
Answer / subhasmita gouda
Smoke Testing: It is done by both developers or testers. It Verifies the critical functionalities of the system. It is a subset of acceptance testing. It is documented or scripted.
Sanity Testing: It is done by testers. It verifies the new functionality like bug fixes. It is a subset of Regression Testing. It is not documented or scripted.
Adhoc Testing: It is done without Test cases & Test planning. It is done when there is less time or there is lac of documentation avilable.
| Is This Answer Correct ? | 4 Yes | 0 No |
Answer / b.v.s.sekhar
Sanity Testing:It is first level of black box testing.In
this level Testers are checking the build whether it is
working with out run time errors or not and any
functionality missing or not.Sanity testing is also known as
smoke testing.
Ad-hoc testing:Due to lack of time, testing is conducting
on important aspects of software is called ad-hoc testing.
| Is This Answer Correct ? | 8 Yes | 10 No |
Answer / baskar
Sanity Testing:Is the initial level of testing,done to find
the basic functionality of the system is working fine and
well enough to allow for doing the testing of remaining all
the functionality of the system
Smoke Testing:It focus on testing the major functionality
of the system we say it as build verification testing.done
to find major functionality of the is working fine and
allow the build to move to testing phase for doing testing
of remaning all the functionality of the system.
| Is This Answer Correct ? | 2 Yes | 4 No |
Answer / syed zabiur rahman
In smoke testing the whole functionality gets tested but
not deeply.Sanity testing is also the same like the smoke
test the main difference is in smoke test only negative
functionality has tested and in sanity testing only
positive functionality has tested.
Adhoc testing is performed for an emergency purpose only
that is having less time. the whole functionality is tested
here.
| Is This Answer Correct ? | 6 Yes | 9 No |
Answer / thaiva
Sanity testing is User acceptance testing
To determine whether the build can be testableor not.
Smoke testing is Build verification testing
To check whther the system works fine after the build is
released without any hanging.
Adhoc testing is random level of testing without using any
test case document.
| Is This Answer Correct ? | 3 Yes | 7 No |
Answer / girish.s
Smoke testing :-Testing the basic features of the build, as soon as it enters to the receiver.., receiver may be Customer or Test engineer to make sure tat the software can undergo nxt posssible testing types.
sanity testing:-Actually speaking thr is no differences between smoke and sanity testing.
it varies by project to project tat's all.
Adhoc Testing:-Testing the application using Creative scenarios which is not referred in the CRS.
Smoke testing:-Entering oly positive data .
Adhoc Testing:-trying with oly negative data.
| Is This Answer Correct ? | 0 Yes | 4 No |
Answer / suman v
Forum4:
________________________________________
Smoke Sanity
1 Smoke testing originated in the hardware testing practice
of turning on a new piece of hardware for the first time and
considering it a success if it does not catch fire and
smoke. In software industry smoke testing is a shallow and
wide approach whereby all areas of the application without
getting into too deep is tested. A sanity test is a narrow
regression test that focuses on one or a few areas of
functionality. Sanity testing is usually narrow and deep.
2 A smoke test is scripted--either using a written set of
tests or an automated test A sanity test is usually unscripted.
3 A Smoke test is designed to touch every part of the
application in a cursory way. It's is shallow and wide. A
Sanity test is used to determine a small section of the
application is still working after a minor change.
4 Smoke testing will be conducted to ensure whether the most
crucial functions of a program work but not bothering with
finer details. (Such as build verification). Sanity testing
is a cursory testing; it is performed whenever a cursory
testing is sufficient to prove the application is
functioning according to specifications. This level of
testing is a subset of regression testing.
5 Smoke testing is normal health check up to a build of an
application before taking it to testing in depth. sanity
testing is to verify whether requirements are met or not
checking all features breadth-first.
Adhoc testing - testing done on main functionalities due to
lack of time. An adhoc testing is done by the person, who is
having application knowledge with out following testing rules...
| Is This Answer Correct ? | 0 Yes | 5 No |
how many meeting in realtime environment? what are they?plz explain?
What are noise variables?
i have an android phone i want to share a photo to my friends phone via Bluetooth.can you tell me possible test cases for this?
What is meant by SIT?
what is data stratification
What kind of techniques used while writing test cases?
What is bug severity?
What is the differnt between Test condition and TesT Scenario
wat is test management ?what are the components available in test management?
Write the possible positive and negative testcases for telephone.
i have two questions ,1)wat is sixsigmatesting 2)wat is stand alone project.plz anybody give the answer
What is split testing?
Automation Testing 
