Answer / sofia

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.

Answer / samuel

Both have stated two different views so pls some on infrom
the correct answer

Answer / bhaskar

Build Aceptance testing or Build Verification testing or
Sanity testing:
It is a type of testing inwhich one will
conduct overall testing on the already released build
inorder to conform whether the build is proper or not for
conducting detailed testing.
Ususlly they check the following during this type of
testing

1. Whether the build can be properly installed in to the
environment or not
2. Whether one can naigate to all the parts of the
application or not
3. Whether all parts of the important features are
available or not
4. Whether the required connections are properly
established or not.

In some companies this is also called
as 'Smoke testing', but some compaies say that just before
releasing the build the developers will conduct overall
testing inorder to conform whether the build is proper or
not that is known as 'Smoke testing' and once the build is
released whether the test engineers are doing the build is
known as 'Build Acceptance testing or Build Verification
test or sanity testing'

Answer / vidhi

Smoke testing is to test the main function of every feature
of the built. Sanity testing is to test the every feature
of the built

Answer / santoshnathan

Sanity testing :This is a type of initial testing performing
on application and make sure that it has no blockages.
Blockages in the sense whether the all functionalities are
avialable or not in order to perform detailed testing on the
application.

Smoke Testing:This is also a type of initial testing
performing on application in order to test whether it is
stable or not.

But companies are following either one.

Answer / ramesh kr.

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).

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

Answer / prasad

Sanity: Initial Testing is conducted to ensure that every
link is working correctly or not, to proceed for testing.

Smoke: when the build is tested, the total is build is
tested again overall to ensure every thing is working
correct.

****Some companies say both are same*****

Answer / prathijna

Differences b/w Smoke Testing & Sanity Testing:

i) Testing the basic and critical features of an application before doing thorough or rigorous testing is known as smoke testing where as Sanity testing is a subset of acceptance testing and it is also subset of Regression testing.
ii) Smoke testing is shallow and wide testing where as in Sanity is Narrow and deep testing
iii)In smoke testing we do positive testing and write smoke test cases where as in Sanity testing we do both positive and negative testing and we don't write sanity test cases.
iv) In smoke testing we go for automation testing and where as in sanity testing we don't go for automation testing.

Answer / sunil reddy

smoke testing is conducted to ensure that application is
stable or not 4 further testing.

Sanity test is used to validate all major functionalities

Answer / kris

sanity testing is seeing if the application is fit enogh
for actual testing. eg: testing the weblink,browser etc.
smoke testing is testing the major functionalities in the
entire application. otherwords..,checking here and there
and get a feel of the whole system regarding the
functionality.

What are the non functional requirements?

5 Answers   CTS,

how can you define Priority and severity

13 Answers   HCL,

The project is going through the maintainance phase I logged a defect which is critical for resolving ,the developement team is in US when they got the reported bug they gave the xplanation that it is a six year old written code moreover we don't have proper followup documents to authenticate this one....in this senario wat will u do??

2 Answers  

what is the diffrence b/w Sanity testing and smoke testing

4 Answers   CIL,

What is Testpolicy document explain in detail? What is the use of this Document?

2 Answers  

what is meaning of manual testing,,?

5 Answers  

Can you explain decision tables?

0 Answers  

What is an end-to-end testing?

0 Answers  

Give me an example when black box testing will not able to detect a bug which white box will detect?

2 Answers   Nelito,

Explain Functionality Testing Techniques

2 Answers   Target,

Advantage and disadvantage of waterfall model,v model and iteration or incremental model?

2 Answers   Philips, TCS,

Which one is not tester responsibilities ? Option 1 Assure the process for contracting software is adequate Option 2 Review the adequacy of the contractors test plan Option 3 Perform acceptance testing on the software Option 4 Assure the ongoing operation and maintenance of the contracted software

1 Answers