Answer / varshab

Smoke testing is basically perform to asure software is
stable enough to consider it for further testing.It is
shallow & wide as we navigate through all options of
application without going into much deep.In this we are
more concern about major functions without much bothering
about minor ones.e.g.It is more useful in configuration
(hardware) testing.

Sanity testing is cursory testing.When new build is
released from development team with minor changes, in this
case instead of performing through regression testing
sanity testing is more appropriate to ascertain indeed
rectifications are done.It is narrow & deep.It is subset of
regression testing.

Answer / sj

Take one example To test Word Doc::

In word doc we have different option available like File
Menu,Edit Menu,View Menu,Insert Menu,Tool Menu,Table Menu
etc.......
For Smoke Testing We check whether when we click in file
menu or in insert menu etc we get all options present in
that menu or not i.e Smoke Testing..


For Sanity testing After clicking on File menu we check its
sub menu whether or not they r working fine or not i.e
Sanity Testing ...........


with the help of example i think u understand the 2 Testing

Answer / deepa

Smoke Test:

When a build is received, a smoke test is run to ascertain
if the build is stable and it can be considered for further
testing.



Smoke testing can be done for testing the stability of any
interim build.



Smoke testing can be executed for platform qualification
tests.



Sanity testing:

Once a new build is obtained with minor revisions, instead
of doing a through regression, a sanity is performed so as
to ascertain the build has indeed rectified the issues and
no further issue has been introduced by the fixes. Its
generally a subset of regression testing and a group of
test cases are executed that are related with the changes
made to the app.



Generally, when multiple cycles of testing are executed,
sanity testing may be done during the later cycles after
through regression cycles.

Answer / akhil kumar

Hey guys are u going mad.First thing is that if u dont know
about the thing that please dont put your foot in that as
little knowledge is a very dangerous thing.This is very
simple thing which I m describing briefly:-

Sanity testing :- It is just to test the basic
functionalities of a software product and application.it is
done by testers.

smoke testing :-it is a form of regression testing.when a
application made some new changes to modules or added new
modules to a application then a smoke test is performed that
it is working fine or not.it can be done by both developers
and testers.

I hope this might have clear your doubts.

If anyone of has some queries regarding manual testing and
automation tools and quality assurance u can ask me freely.
my email id is akhil_25683@yahoo.co.in.

Thanks & Regards,
akhil

Answer / sridhar

Sanity Testing: sanity test is a very brief run-through of
the functionality of a computer program, system,
calculation, or other analysis, to assure that the system or
methodology works as expected

Smoke Testing: smoke testing is a preliminary to further
testing, i.e when the release is given to the test team -
need to do smoke testing for each and every link - in order
to verify that the next pages are displayed and the further
testing can be done.

Answer / rajkumar

Smoke Testing- Also called as Build Verification Testing.
This type of testing is done to check the stability of the
build that most of the crucial function are present and can
be accessed and to evaluate the build is ready for further
levels of testing. e.g. All menu options are present, all
forms can be navigated properly. This is a shallow and wide
approch

Sanity Testing- This is a cursory testing in which we will
check a functionality in detail rather than going for
overall build. Approach is narro & deep.

Answer / naveen

Smoke testing is a wider\broad approach in which we test the
stability of build. Whether build deployed to testing
environment functioning without any issues or not..Here the
main functionalities is tested(such as we are able to login
to the application without any issues)

Sanity testing is a narrow regression testing where we test
indepth functionalities are working as expected or
not(basically a touch test of all applications)

-Naveen

Answer / a.sameer

Smoke testing is done by developers before the build is
released to testers.

Sanity testing is done by testers to verify whether to
accept a build for further testing or not.

In both the same the way of technique used to test is the
same, both are for checking for minimal functionality of the
application only difference is done departments are different.

Answer / viji

smoke testing-Checking the functionality
Sanitary-opposite to smoke testing.checking in depth of
functionality of the process

Answer / silpa

sanity testing and smoke testing is same.
here we wil check the basic functionalities of our build.
we are using +ve data for sanity testing
but in smoke testing we are using -ve data .

system testing or sub system testing ? both are same or different ?

1 Answers   Amdocs,

what are the definitions of smoke , sanity and dry run testing ?

2 Answers  

what is difference between testing and development in your view?

4 Answers   Verizon,

how to connect your project in database?

0 Answers  

how will you define your bug status flow in softsmith qamonitor?

2 Answers  

What is IEEE 829 format

2 Answers  

What ishigh severity, low priority bug?

0 Answers  

For any web application, what are the possible login features that should be tested?

0 Answers  

what type of testing you are doing ?

3 Answers  

Hi everyone.This is one of my interview questions.Could you please send me the answer for this?My ID:spam4rekha@gmail.com Q : what is BVA and ECP ? Thank You rekha

4 Answers  

What is mean by Test Plan? What details will be mention in it?

3 Answers  

Hi harish n Satish...thanx for the response... Already told Functionality testing and user interface type testing to interviewer but he was expecting something else. And also explained test cases....Is it data driven testing for user id and password combinations? If i am not wrong....?

0 Answers   Cap Gemini,