Interested to Buy Any Domain ? << Click Here >> for more details...
what is the difference between smoke, sanity and dry run
testing?
- 7 Answers
- 25927 Views
- Infosys, I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / madhavi
Smoke testing mean testing the basic function to check the
product is stable or not.
Sanity testing mean testing few modules deeply to check it
is bug free or not
Dry run testing mean testing the entire product deeply i.e,
checking all modules in depth to check whether it is bug
free or not.
| Is This Answer Correct ? | 33 Yes | 12 No |
Answer / kishore
smoke testing and sanity testing are one and the same. if
the quick test is conducted in test environment before
functional testing is called smoke testing. if the quick
test is conducted in client environment before User
Acceptance Testing (UAT) is called sanity testing.
| Is This Answer Correct ? | 11 Yes | 3 No |
Answer / sreenath
It is a type of testing in which one will perform overall testing to perform the detail testing.,
In some companies both are same,.
In some companies the developer will do testing before release the build called smoke test,.AFTER BULID RELEASE the test eng will perform testing called sanity testing,.
| Is This Answer Correct ? | 5 Yes | 2 No |
Answer / madz
SMOKE: testing critical feature (if the application starts sucesfully), before going for thorough testing.Scripted
To make sure the application is stable for the further rigorous testing.
SANITY: testing the impacted areas for the bugs, after new functionality is added.Non Scripted
| Is This Answer Correct ? | 1 Yes | 0 No |
Answer / saravanaragupathy
SMOKE TESTING:
* 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 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.
* Smoke testing is conducted to ensure whether the most
crucial functions of a program are working, but not
bothering with finer details. (Such as build verification).
* Smoke testing is normal health check up to a build of an
application before taking it to testing in depth.
SANITY TESTING:
* 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.
* 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.
* 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.
* Sanity testing is to verify whether requirements are met
or not, checking all features breadth-first.
Sources :
http://www.softwaretestinghelp.com/smoke-testing-and-sanity-testing-difference/
| Is This Answer Correct ? | 3 Yes | 3 No |
Answer / sandeep
smoke testing is testing the basic feature before actual
testing begins,scripted one.
sanity testing is the a specific feature in detail
| Is This Answer Correct ? | 4 Yes | 5 No |
Answer / geetanjali
smoke testing is the first level of testing on newly
released build to check main functionality
sanity testing is the next level of some testing, to test
mandatory and optional functionalities
| Is This Answer Correct ? | 1 Yes | 3 No |
what can be the reason for client not accepting the release?
Q) A hotel telephone sys can perform 3 functions . Call another hotel room by entering a room number(201 to 500) . Call an external line by entering a 9, followed by the number. . call various hotel services 0=operator, 7=room service 8=reception. Write sets of test cases to adequately test this telephone system
wht r 6 sigma standards
Wht is the Difference between Test Harness and Test Driver Anybody can explain it..Thanks in advance...
What is a defect?
Can v prepare Test cases only from BRS from Tester point of view?
what are the contents of a test plan?
What is your testing approach/plan if requirements are frequently changing?
How to test the Fire walls?
Why we give test deliverable to client ? or what is the purpose & necessary for giving test deliverable to client ?
What is quality center? What are the modules of quality center?
Can u please explain the regression testing criteria? we are having 1000 testcases, outof 1000 TC'S 800 defects we find,whose priority and seviority is high . in this situation how we can done the regression testing?
Automation Testing 
