No Monkey Testing and Gorilla Testing are not same.
Monkey Testing : Testing a system or an Application on the
fly, i.e just few tests here and there to ensure the system
or an application does not crash out
Gorilla Testing : Testing one particular module,
functionality heavily
vidhya ratnam is correct,actually as u said monkey or
gorilla testing comes under the catagory of Adhoc
testing,due to lack of time testers will test the main
functionalities of the application ,this is called monkey
or gorilla testing
this is satya,any doubts contact:9912418320
monkey testing means testing of an application, with no
test case document, and design .It is just to check what
could be the result ,if applicaton is used in improper way.
where as gorilla testing is the testing done on aplication,
to check if the user thinks to break the application, with
improper combination of keys,or pressing the key whose
option is not available in application.
so we can say in monkey testing ,no idea of
application to the user eg-1 year baby is playing with
keys,when application is running. Whereas gorilla testing,
although the user know the the application functionality,
but he wants to do more than that..
Monkey (light weight jumps easily) testing resembles the
behavior of a monkey on a tree....it jumps from one branch
to another with out any sequence/order....in the same way
monkey testing is the process of testing the functions of a
system with out any sequence or order... a tester will test
one function in module A and jump to another function in
another Module G and come back to another function in module C..
It is also called Random testing...it factories to test the
quality of group of items they will pick some items randomly
from a group of items and test the quality and analyze the
results.. this will be done by higher people in the
Test/Quality Center...
Gorilla (heavy weight can't move so easily) Testing on the
other hand is testing a function or module heavily....for
example testing a email functionality by click on "send
email" button...or creating an order by click on "check out"
button... continuously for more times...(with out stopping
after the first click..) in the first case it will send many
emails if it is delivering for each click event...same away
it may try to create multiple orders if it is processing
order for each click event...and some times may go in to
loop and application will hang after consuming more
resources...generally this will happen if there is a problem
in the hardware (key board)...if the key board is too old
some times the keys may struck suddenly leads to generation
of multiple events....
actually as u said monkey or
gorilla testing comes under the catagory of Adhoc
testing,due to lack of time testers will test the main
functionalities of the application ,this is called monkey
or gorilla testing
Monkey testing is testing like a monkey(that is lightly with
main functionality and without maintaining the
order/sequences).It is used to save time and to test basic
funtion is fine or not in a app.
But gorrila testing is used for heavily testing with a main
functionality and tested it heavily in the application.
It may possible that after monkey there some major defect
but after gorrila testing there should not be any major defect.
Let me know if you have any doubt.
such questions are waste, I pity on those interviewer who
asks such questions. Such questions have no significance.
Its sheer wasting time of interviewer and interviewee.
There are many other and interesting things to ask in the
interview. Fail to understand why such questions are given
importance.
Not a good practice
Sorry
It seems now that the difference between monkey testing and
gorilla testing is clear.
I want to clarify another conception: although both monkey
testing and gorilla testing comes from ad hoc testing, they
are different from ad hoc testing and also random testing.
The following definitions from ISTQB glossary give a good
description:
ad hoc testing(emphasizing testing process): Testing
carried out informally; no formal test preparation takes
place, no recognized test design technique is used, there
are no expectations for results and arbitrariness guides
the test execution activity.
random testing (emphasizing testing technique or test
design) : A black box test design technique where test
cases are selected, possibly using a pseudo-random
generation algorithm, to match an operational profile. This
technique can be used for testing non-functional attributes
such as reliability and performance.
monkey testing(emphasizing testing behaviour): Testing by
means of a random selection from a large range of inputs
and by randomly pushing buttons, ignorant on how the
product is being used.
There is a Create Card window. It contains Card Name,Lunch
discount & Dinner discount.
I have written test cases for above [+ve & -ve].Now there
is one Party discount is added to that window.
How should I maintain test case.Guide me properly.I want to
know that whether I have to write new test case bloking the
previous one.
Can you please tell me what and how to test in a web based
application manually? And i manually need to do usability
testing and functionality testing for the same (web based
application. So please tell me how and what to check the
functionality and usability of the web based application?
if bug is found & we will know the main Resion for that bug
Arrise
1 - Corrective & Prevention Action
2 - Risk ana
3 - Root Cause analysis
4 - Impact analysis