Interested to Buy Any Domain ? << Click Here >> for more details...
can any one tell whats the difference between smoke testing
and sanity testing
- 13 Answers
- 18432 Views
- CIC, HCL, I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / mayandi m
smoke testing will check all the functionalities in the
application,but not go deeply into it(otherwise we can say
BVT(Build verification test)
sanity testing wiil check major functionalities and deeply
go into that
both will prepare the application to be testable one
| Is This Answer Correct ? | 10 Yes | 0 No |
Answer / sm
Here are the differences you can see:
SMOKE TESTING:
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.
2)In software industry, smoke testing is a shallow and wide
approach whereby all areas of the application without
getting into too deep, is tested.
3)A smoke test is scripted, either using a written set of
tests or an automated test
4)A Smoke test is designed to touch every part of the
application in a cursory way. It’s shallow and wide.
5)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).
6)Smoke testing is normal health check up to a build of an
application before taking it to testing in depth.
SANITY TESTING:
1)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 sanity test is usually unscripted.
3)A Sanity test is used to determine a small section of the
application is still working after a minor change.
4)Sanity testing is a cursory testing, it is performed
whenever a cursory testing is sufficient to prove the
application is functioning according to specifications.
5)Sanity testing is a subset of regression testing.
6)Sanity testing is to verify whether requirements are met
or not, checking all features breadth-first.
Hope these points will help you to clearly understand the
Smoke and sanity tests and will help to remove any
confusion.
| Is This Answer Correct ? | 4 Yes | 0 No |
Answer / lucky
Smoke Testing is to vefity the applications basic
functionality after a new build is installed.(2 to 3 hr
testing after the new build installed).
Sanity testing is to verify the applications major
functionality is woroking fine after a new build is
installed and give a confidence to test team to go ahead
for further testing or reject the build.(1 or 2 days
testing after the new build installed)
| Is This Answer Correct ? | 4 Yes | 0 No |
Answer / sateesh.m
as of my knowledge, just before relasing the build the
developers will check whether the build is proper forhter
detailed testing or not . that is known as smoke testing
and once the build is relaised the test engineers will
check whether the build knos as sanitary testing
| Is This Answer Correct ? | 3 Yes | 2 No |
Answer / softwaretester4u
Ashok Kumar Gurram,hi this is not eorrect answer as i
experience .sanity and smoke differece is there or not .i
don't know but smoke testing is checking all the major
functonalies are not checking before relaesd to the testing
team at inc or system testing level
| Is This Answer Correct ? | 2 Yes | 2 No |
Answer / sailaja
The answer which I am giving is purely on my analysis by
understanding the concept.
Sanity testing is the one which we are going to perform on
each build before going for rigorous testing with a set of
preliminary test cases. Based on the execution of these
testcase we can decide whether to go with through testing
or suspend the testing for fixing before further
execution. Since we are deciding the reasonableness it may
be considered in two aspects. One is for further/rigorous
testing. And some of the practioners says we peform this
type of testing before we ship the build to customer.
In summary it is going to considered for two reasons. 1.
for rigorous testing and another one is before ship the
application.
Where as Smoke Test was introduced by Microsoft when they
were developing the NT 4 in which everyday they were
releasing the new build with new component(code segment) or
modifying the existing one. Smoke test was performed by
Microsoft to ensure that no smoke comes out with these
changes. Till then Smoke test was performed by many people
in the Hardware environment.
Please correct me if my understanding is not correct
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / salman
hi......
Smoke Testing is performed to that the critical
functionalities of the program is working fine Sanity
Testing is done to check the new functionality / bugs have
been fixed
The objective of this testing is to verify the "stability"
of the system in order to proceed with more rigorous
testing The objective of the testing is to verify the
"rationality" of the system in order to proceed with more
rigorous testing
This testing is performed by the developers or testers
Sanity testing is usually performed by testers
Smoke testing is usually documented or scripted Sanity
testing is usually not documented and is unscripted
Smoke testing is a subset of Regression testing Sanity
testing is a subset of Acceptance testing
Smoke testing exercises the entire system from end to end
Sanity testing exercises only the particular component of
the entire system
Smoke testing is like General Health Check Up Sanity
Testing is like specialized health check up
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / bitragunta
SMOKE TESTING:to check the basic functionality of an application ir check the stabulity of the build,
SANITY TESTING:to check the major functionality of an application such a functionality part,ie buttons,text box,amoe fields
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / ashok kumar gurram
Smoke Testing: In this testing we will check whether all
componenets are present or not. Where as in Sanity we will
check all components are working properly or not.
| Is This Answer Correct ? | 3 Yes | 4 No |
Answer / uttam007
BOTH THE ABOVE ANSWER ARE RIGHT TO CERTAIN EXTEND.LET ME RE-
PHASE IT, SMOKE TEST WE PERFORM AFTER EACH AND EVERY
BUILD,VERSION CHANGE ETC. THIS TEST WE TRY TO FIND WHETHER
ALL THE CONDITIONS IS MET AS WE DERIVED.
NOW SANITY TEST IS THE ONE WHEN WE DO THE INITIAL TESTING
OF ANY SOFTWARE WHETHER SOFTWARE IS ACCEPTABLE FOR
TESTING.GENERALLY ITS THE FIRST TEST, WHEN A QA IS CALLED
FOR AFTER THE APPLICATION IS DEVELOPPED.
| Is This Answer Correct ? | 2 Yes | 3 No |
9. Are there materials you would like to see added to the Web site? Which ones?
Write TestCases for mobile
what type of testing you do for web based applications than client-sever application ...pls expaline
How do you satisfied ur client, P.M and T.L? (In P.M)
Which document you will get with new Build during testing?
Who is responsible for doing "Cause-Effect GraphCause Effect Graph". If tester is responsible then how we to do it? Urgent
I would like to know about the steps to follow for testing a .NET web application. Please provide detailed steps with more general scenarios.
what is the difference between client server & web based applications?
Tell me some Adhoc testing scenarios of ebay (online auction product)?
What is a bug triage?
Scenario A year ago we developed a standards compliant website for a client. Their site is very popular resulting in the client wanting to be able to track how it is being used by their users. The first part of this project is to create a Login function so that users can be identified on the website. The data supplied by users would have to be handled securely. You have been allocated this project to work on. You will be responsible for the task from start to finish and will be expected to give feedback to your manager. User expectations  The client wants their users to be able to login using a page that fits in with the website design.  Tom wants to access the website but doesn’t want his login information to be available to anyone else.  Paul doesn’t want to login to the website because he’s not a frequent user. Task Please provide some feedback on how you would do the following:-  Being the only Test Engineer on this task, what would your approach be for this requirement?  Identify the key areas for testing this page.  What tools if any, would you use to perform the testing, bearing in mind that the testing will be done without using an ‘automated test tool’.  Provide a sample test case that could be used for testing this page, for example as a word or Excel document.
what is testing?
5 Answers Naukri.com, RealTech, TCS, Value Labs,
Automation Testing 
