Are monkey testing & gorilla testing same? If not, then
what is the difference between these two?
Answer Posted / lakshmanaraj bg
Monkey Testing and Gorilla testing are not same.
Monkey testing - an unflattering term used to describe inexperienced people "banging" on a terminal. Often used to describe testing by staff who have trouble finding their butt with both hands.
Gorilla testing - used to describe repetitive, boring manual testing that a tester has already done a hundred times and could do in their sleep. As in "a trained gorilla could execute these tests". Often a sign that testing needs to be automated.
In simple term it can be referred as following below,
Gorilla Testing - you have a real short window of time to test and X number of resources (typically experienced QA). You hit the app hard, with everyone focused on core functionality and critical paths a "typical" user would take through the app. Unfortunately, this is still all too common today.
Monkey Testing - mundane testing that you have to do when your company is too cheap to buy you an automation tool to do it for you. It's a huge waste of senior tester's time, but usually no other resources are available.
| Is This Answer Correct ? | 5 Yes | 2 No |
Post New Answer View All Answers
what is your daily activities?
Explain some techniques for developing software components with respect to testability.
Which was the most interesting bug you found.
Please let me know how to test labels in web application manually and how the testcases would be. Please provide me a sample testcase
What is bug priority?
When we use integration testing for any new system so why we required system testing.
What do you plan to become after say 2-5yrs (Ex: QA Manager, Why?)
Explain branch coverage and decision coverage.
can you show me the test cases on registration form
Hi Could someone please provide Siebel Testing Interview questions for 5 years exp.
tell me brief about your project? please help me how to explain the project what is the flow? my current project is ERP domain web based application. please help me
If you are handling a product testing and if there are around 100 test cases and in them few test cases are failed then at the end of the day how will you treat whether the product is pass/fail.? consider the failed test cases are in functional requirements.
can anyone help me in getting unix on manual testing i.e can u forward material & web sites to my mail id (suresh_57599@yahoo.com) to understand how the work flow working on manual testing on unix and the contents.plzzzzzzzz help me its urgent.
What is deferred status in defect life cycle?
What does you mean by positive and negative testing & what is the difference between them. Can anyone explain with an example?