Defing Smoke testing, sanity testing, ad-hoc testing, monkey testing.

Can any one please define the tearms to me,
1) Smoke testing. 2) Sanity testing 3) Ad-hoc testing 4) Monkey testing.

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.

Hi,

Find below the definitions of the terms you have asked for:

<b>Smoke Testing:</b>
Smoke testing is done at the start of the application is deployed. Smoke test is the entry point for the entire test execution. When the application is passed under the smoke test then only further system testing or regression testing can be carried out.

In general smoke testing is done when the higher version of the build is deployed and is done at each and every time the build is deployed. In smoke testing the main functionalites are tested and the stability of the system is validated.

<b>Sanity Testing:</b>
Sanity testing is also similar to Smoke testing, but has some minor differences. Sanity testing is done when the application is deployed into testing for the very first time and in smoke testing only positive scenarios are validated but in sanity testing both the positive and negative scenarios are validated.

For example, if the new software is crashing systems every 5 minutes, 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.

<b>Ad-hoc testing</b>
Testing carried out using no recognised Test Case Design Technique which is a method used to determine Test Cases. Here the testing is done by the knolwedge of the tester in the application and he tests the system randomly with out any test cases or any specifications or requirements.

<b>Monkey testing</b>
Monkey test is a unit test that runs with no specific test in mind. The monkey in this case is the producer of any input. For example, a monkey test can enter random strings into text boxes to ensure handling of all possible user input or provide garbage files to check for loading routines that have blind faith in their data.

Regards,
Ganesan

Hi Bhushan,
Please check the following Definitions...

[B]Sanity testing[/B]:We will check the complete functionality of the application

[B]Smoke Testing:[/B] We will check the basic functionality of the application

[B]Adhoc/Monkey/Free Form Testing[/B]:

imagine something (TV) given to a monkey and watch how it uses and tests that....

Regards,
Krishna...

Hi All,

Ganeshan answers was excellent, even expalined with the examples..
but i am adding some more stuff to his coments...

Ganesh..
An adhoc testing is done by the person, who is having application knowledge with out following testing rules...

But in the case of monkey testing the person who is doing no need to have knowledge on the applicationa also...


Cheers,
Praveen

[B][I]Smoke Testing:[/I][/B]
It is basically a type of testing in which one can perform an initial non-detailed short-span conducted on the application in order to check if the desired windows / objects / features are basically available to carry on a detailed testing on them in other words it is an availability testing.

[B][I]Sanity Testing:[/I][/B]
It is a type of testing in which one can perform an initial non-detailed and short span testing on the application in order to check if the application is proper, proper mean proper availability of windows / object / features.

[B][I]*Note:[/I][/B] Smoke testing and sanity testing conceptually same but they differ from each other preciously as the smoke testing is associated with negative perception while sanity testing has positive perception.

[B][I]Adhoc Testing:[/I][/B]
It is a type of random and free style testing performed on the application without using the test case document, unlike formal testing in order to cover the functional areas which are not covered with test case coverage and to refine the test case document ultimately.

[B][I]*Note:[/I][/B] It is always advisable that adhoc testing is conducted by the same test engineer who has basically completed formal testing.
[B][I]
Monkey Testing:[/I][/B]
It is type of testing in which one can perform abnormal, beyond capacity, more volume of data related operations intentionally on the application to check if the application is stable despite the abnormal behavior.

The smoke testing is the first level of testing. In this we test only required fields of the application

In the sanity testing we test all the fields.

This so very informative

Hi Friend,

I am enlisting some differences between Smoke testing & Sanity Testing.

1.We do Smoke testing to confirm that recently deployed build is ready for further testing or not. This is a wider approach in which tester touches all areas of software without getting into deep.

1. We do Sanity testing to confirm that build with minor changes is working fine or not. For this tester need not to touch all areas of software but needs to be Focus on specific function or area under build where changes have done. For this tester needs to do Narrow Regression testing to find out impact of minor changes in build.

2. Smoke testing can be done by Manual or automated Test Scripts/Cases.

2. Sanity Testing is usually done without Test Scripts/Cases.

3. Smoke testing is done to ensure that most crucial function of application working fine but it does not bother about minor changes.

3. Sanity testing is done to ensure application is working in accordance to specification after minor changes are done in build. It is subset of regression testing.

Pls let me know if you are clear with difference.

Smoke testing -Testing Team Reject a bulid to development team with reson before start Testing.
<b>Sanity Testing:</b>
Sanity testing

It is Tester Acceptance Testing.Whether development build is stable for complete testing or not?

<b>Ad-hoc testing</b>

with out using any test cases or any specifications or requirements.

<b>Monkey testing</b>
Monkey test The coverage of main activities only in your application during testing is called as monkey testing