Difference between sanity and smoke test

Hi all,
:p i am dibya mishra,new to this forum.
can anyone please provide the answer of the above question ,<b>"Difference between sanity and smoke test" </b>with respect to phase of SDLC where this kind of test is performed.

Regards,
Dibya Mishra

Hi,
This is also called as sanity testing. This is mainly used to identify environmental related problems and is performed mostly by test manager. For any application it is always necessary to have the environment first checked for smooth running of the application. So in this testing process the application is run in the environment technically called as dry run and checked to find that the application could run without any problem or abend in between.

Regards,
Janelyn

This type of testing is also called sanity testing. This testing is done in order to ensure whether the application or system developed is ready for further major testing. This is done so that the system or application can function properly at least to the minimum expected level.

Diffrent Companys use diffrent kinds. It depends on them. But Actually
Sanity and Smoke are same they are used for testing the navigating steps of application in a sequence form. But some people use Sanity First i,e when the tester gets the Build(EXE). And Does the Smoke testing a day before the release of the Project,Prductor program....
ok

In simple words, i feel the following about Sanity and Smoke Testing.

Sanity Testing: Brief test of major functional elements of a piece of software to determine if its basically operational.
Sanity Tests are useful both for initial environment validation and future interactive increments.It gives a measure of confidence that the system works as expected prior to a more exhaustive round of testing.

Smoke Testing: A quick-and-dirty test that the major functions of a piece of software work.Smoke tests are designed to confirm that changes in the code do function as expected and do not cause failure of the rest of an entire build.a smoke test generally consists of a collection of tests that can be applied to a newly created or repaired computer program. Sometimes the test is performed by the automated system that builds the final software.

The Web Standards Project online Acid test is to test the compliance of the web browser with software technology standards.Any browser could match its software code against the test and get instant results online whether it passed or not.

The test is really an effort to draw a line in the sand between compliance with open industry standards and exclusionary web sites based on closed proprietary formats.
Apple Computer's Safari was the first to pass the test last year.

Is the Santity Testing & Smoke Testing are same? If it is not, Give difference between Santity Testing & Smoke Testing.

Hi,
I have an doubt on diff between sanity testing and smoke testing ?

How could you say new build failure after done the sanity tesing?

when we get failure in the build during sanity testing then we report the problems to devlopment team(its depends on company)
After completion of their modifications, they release build to testing team.
again starts sanity testing untill the build is stable.

Smoke Testing:It is first testing to be performed on the intial build before tester takes it for further testing.
It is done on build level .
It is also used to check basic functionality of the build.

Sanity Testing:It is done on module level and It is used to check main functionality of the build.
one more point is to check the bugs which are found during smoke testing whether they are resolved or not?

Hi All, dont confuse with Smoke and Sanity, its very simple.

Smoke Testing is not intend to test any functionality of the application. Its a just ensuring successfull deployment of build, configuration of Email server, DB connectivity, resource bundle deployment and more like PDF generation(depends on application and requirement).

Sanity Testing is testing the major functionality ensuring build is stable for further testing efforts(for system testing).

Is it Clear now??

The sanity testing is to see how sane the application is for further testing where as smoke testing is see whether new features or functionality added are working good with exiting one and there is no problem.


With regards,
Brijesh Jain.

Before geving build to the testing team in the development site people conducting smoke testing for completeness & correctness.
After receiving bild from develop ment site and for tester acceptance test(before the testers going to comlete execution of applcation) the testing team conndecting a test for completeness & correcness of an application build is called sanity test.
That's all:)

Hiiiiiiii................
..............Lots of wishes to all of you from Heart
On Happy New Year 2007..................

Sanity Testing :
Is can say the testing tht covers all those test cases or steps tht r necessary to pass to start the next level of testing.(Main concern is u can go forward(Next level) only when you get passesd all the necessary steps(Test Cases) at that level of testing.)

Smoke Testing:
Some how can say that it's over look testing whr intention is not going to deep But testing the main functionalities of the system thoroughly.(Finally can say testing the system thoroughly & it need to have experience of that level tht u can verify the system on smoke testing, u know wht the things r must to chk ,which parts r mostly hav to b tested, like all that.)

Friends plz correct me If i m wrong I wil b thank ful to u.
Thnx & regards
rajeev sharma
9818004180

What is the difference between shakedown testing and sanity testing??

Hi What is the difference between Sanity,Smoke testing.
What is Gamma testing

smoke testing: most cost effective method for identifying and detectind defects in software! They are designed to confirm that changes in the code function as expected!

Sanity testing : it is to test basic required functionality of the basic system!

Gamma Testing: at customer site! Refers to the process of improving and evolving products after the initial release!

hope iam clear !:D

Hello vmshenoy,
Congratulations for being member of the month.
Can u explain smoke testing in a bit detail. Because somebody in this forum itself had said that smoke testing is not intended to test any functionality of the application.its just ensuring of successful deployment of build and all its attachments...
I am a bit confused...

shakedown testing is a synonym for sanity testing and shakeup testing is a synonym for smoke testing

Hi

I think simply we say as
sanity testing means whether the build is ready for further testing or not
smoke testing means wheter the build is ready fr release or not

i think this is also right

if any mistake plz tell me
ok
Thanks

Sanity testing is testing the new version is working better than the previous version.
Smoke testing is just running the application to know the flow & functionality of the application

Sanity Testing is a narrow type of regression testing...ie, testing a particular module of an application in deeper...

smoke Testing is a wide range of testing..ie,testing an application without getting in to deeper...

i guess i'm ri8!!! if any issues plz lemme know...

With regards
Suganj

who do the Sanity testing and smoke testing. Tester or Developer.

It can be done by either Testers or the Developers.:)

It depends from company to company and their decision.

But, generally Testers do it.:eek:

Sanity Testing is performed whenever cursory testing is sufficient to provide the application is functioning according to specifications. Thes level of testing is a subset of Regression Testing.

Smoke Testing is a relatively simple check to see whether the product "smokes" when it runs. Smoke Testing is also known as AD-HOC TESTING, e.i. Testing without a formal Test Plan.

Smoke Test a phrase used to describe a subset of tests typically limited in number that can be run against each software build to determine whether the software has regressed in form or function since a previous build.

“Smoke Testing might be a characterized as a rolling integration strategy”. Smoke testing is an integration testing approach that is commonly used when “shrink-wrapped” software products are being developed. It is designed as a pacing mechanism for time-critical projects, allowing the software team to assess its project on a frequent basis.

The Smoke Test should exercise the entire system from end to end.
Smoke Testing provides benefits such as:

1) integration risk is minimized.
2) the quality of the end-product is improved.
3) error diagnosis and correction are simplified.
4) progress is easier to asses.

Sanity Testing - typically an initial testing effort to determine if a new software version is performing well enough to accept it for a major testing effort.
For example, if the new software is often crashing systems, bogging down systems to a crawl, or destroying databases, the software may not be in a 'sane' enough condition to warrant further testing in its current state.

After so much discussion , I am still not able to comprehend the difference between these two types of testing.
Anyone please answer in points.
a) Is sanity and smoke testing same? say yes or no
b) If no then what is the basic difference ?

[QUOTE=ruchikak;12879]After so much discussion , I am still not able to comprehend the difference between these two types of testing.
Anyone please answer in points.
a) Is sanity and smoke testing same? say yes or no
b) If no then what is the basic difference ?[/QUOTE]

[b]sanity and smoke testing are not same.[/b]

Difference can be better understand with this example.

If you purchase a new mobile and you use it with care for few days, this is sanity testing.You will see, ya, all functions are well working.Now after few days it's on to you how badly you use/test it.

Now you have added memory card in your mobile, or have purchased handfree for your mobile which was not there.Now you will see whether memory card or handfree kit is working with your cell or not?this is smoke testing.

I hope now it should be clear to you and there should be no confusion.

Thanks Brijesh.
On the basis of ur example can u please define these two types of testing . That will help.

[QUOTE=ruchikak;12919]Thanks Brijesh.
On the basis of ur example can u please define these two types of testing . That will help.[/QUOTE]

Sanity testing is initial testing to verify that the build is working and exhaustive testing can be performed.

Smoke testing is required when any new feature or function is added in the existing working build to verify that the build is still working with new feature added.

Thanks
Congrats for being member of month .

ok let u explain exact explanation abt sanitary and smoke

Smoke test and Sanity test almost shares the same definition, but still has some minor differences.

Both Smoke and sanity test are called as Build verification test, and done at the beginning once when the build or application is deployed, and checks whether all the main functionalities are working fine.

The difference is in the smoke test we will be validating the main functionalities only with the positive scenarios, but in the sanity test the main functionalities are validated with both the negative and positive scenarios.

Smoke tests are often scripted where the machine determines whether the outcome was as expected, whereas sanity test are often a gut-check of whether the results "appear" to be reasonable.

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.

Smoke testing:

is it possible to test the application/software further,this type of testing is done with minimum requirements and decision whether further testing is possible or not is taking immediately...

Sanity testing:

is it resonable to test the application/software, once smoke testing is done sanity testing is performed ,and decision of whether testing the application/software is resonably is taken immediately.

Both type of testing is done with minimum requirements~~`

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.


thanks & regards
trainee_tester

Hi Dibya,

A smoke test determines whether it is possible to continue testing and
sanity test determines whether it is reasonable to proceed with further testing.

A software smoke test determines whether the program launches and the interfaces are accessible and responsible.
Sanity test exercises the smallest subset of application functions needed to determine whether the application logic functional and correct.

If the smoke test fails, it is impossible to conduct a sanity test.
If the sanity test fails, it is not reasonable to attempt more rigorous testing.

Hope this make it a lot clearer.
Feel free to get back incase of doubts.

Regards,
Tina.

Smoke Testing for every Build and Sanity for every Release