Quality Testing

Quality is delighting customers

Hi,

This is latest interview question, which i was faced: Why sanity testing is also called smoke testing?

Views: 2285

Reply to This

Replies to This Discussion

Sanity and smoke testing is the type of functionality testing which we generally do
Disparity between Smoke Testing and Sanity Testing

Smoke Testing

Is done to ensure high priority functionality of application works as required.
Is scripted - either using a written set of tests or an automated test
Is designed to touch every part of the application in a cursory way.
It is shallow and wide.

Sanity Testing
Is done to ensure system works as required.
Is unscripted.
Is used to determine a small section of the application is still working after a minor change.
It is narrow and deep.
Agree with you guys..there's a thin line diff in the two.

As in smoke - we test whether the basic functionality /feature of a program or an application works fine, despite of going into details of every feature when the build has just arrived.

while in case of other one we focus on all functionalites & features of an AUT.
Software development
In software development, the sanity test (a form of software testing which offers "quick, broad, and shallow testing") determines whether it is reasonable to proceed with further testing.

Software sanity tests are commonly conflated with smoke tests. A smoke test determines whether it is possible to continue testing, as opposed to whether it is reasonable. A software smoke test determines whether the program launches and whether its interfaces are accessible and responsive (for example, the responsiveness of a web page or an input button). If the smoke test fails, it is impossible to conduct a sanity test. In contrast, the ideal sanity test exercises the smallest subset of application functions needed to determine whether the application logic is generally functional and correct (for example, an interest rate calculation for a financial application). If the sanity test fails, it is not reasonable to attempt more rigorous testing. Both sanity tests and smoke tests are ways to avoid wasting time and effort by quickly determining whether an application is too flawed to merit any rigorous testing. Many companies run sanity tests and unit tests on an automated build as part of their development process.[3]

The Hello world program is often used as a sanity test for a development environment. If Hello World fails to compile or execute, the supporting environment likely has a configuration problem. If it works, the problem being diagnosed likely lies in the real application being diagnosed.

Another, possibly more common usage of 'sanity test' is to denote checks which are performed within program code, usually on arguments to functions or returns therefrom, to see if the answers can be assumed to be correct. The more complicated the routine, the more important that its response be checked. The trivial case is checking to see that a file opened, written to, or closed, did not fail on these activities – which is a sanity check often ignored by programmers. But more complex items can also be sanity-checked for various reasons.

Examples of this include bank account management systems which check that withdrawals are sane in not requesting more than the account contains, and that deposits or purchases are sane in fitting in with patterns established by historical data – large deposits may be more closely scrutinized for accuracy, large purchase transactions may be double-checked with a card holder for validity against fraud, ATM withdrawals in foreign locations never before visited by the card holder might be cleared up with him, etc.; these are "runtime" sanity checks, as opposed to the "development" sanity checks mentioned above.
I think , i m also confuse with that question so i m more website refer & 2 books are refer but one book in the exact meaning of sanity testing & smoke testing there is no difference between them expect the spelling,but i think they are different
&
i m also more time faced this question in the different companies interview, but in different way
what is the difference between in sanity testing & smoke testing?
can somebody explain me exact & simple difference between sanity & smoke testing ?
Well incase of sanity n smoke you will get 100 different responses from 100 people. Same here,

Smoke testing is applicable when tester get new build and he tests only basic positive scenarios before initiating to do application testing.

Sanity testing is applicable when tester gets new build and he testers major functionality before initiating to application testing
Hi,

Here is the main difference -

Smoke test - To ensure whether the build is fit for use. ( horizontal test)

Sanity test - After smoke test passes, ensuring that the main functionality is working as expected. (Vertical test)
Ex - Testing the main requirement such as calculating the discount part.
nice
because basic theme of testing or purpose is same in both....
As both are the same...In Some testing you have to make sure that all services are working so did not give any exceptions or any error and the same with Sanity Testing
So both are the same...
I small companies these terms were used interchanagebly and means the same.

But both are not same and in interviews you need to mention clear.Might be interview is trying to confuse you or he might not be aware of them exactly.

Smoke testing : Initial testing done by testers(Generally execute Pri1 sev1 test cases or we can say BVT cases to make sure whether the build to eligible for testing or not.)

If smoke tessting fails build will be rejected.

Sanity tetsing : Once smoke testing is completed and passed will do sanity testing - means throughly checking major functionalities (like executing some more important test cases) to know which functionalities are working.
Sanity and smoke are two different types of testing...

Smoke Testing: When the build is ready from DEV team, we use to test whether basic modules/tabs are existing or not to test application further.
Sanity testing: it is complete functional testing to test all requirements are working properly or not. We are validating data and test application in positive and negative test cases

RSS

TTWT Magazine


Advertisement

Advertisement

Advertisement

Advertisement

© 2022   Created by Quality Testing.   Powered by

Badges  |  Report an Issue  |  Terms of Service