Monkey testing vs gorilla testing
In software engineering the software testers conduct monkey testing and gorilla testing at the final stages of the testing phase. These two are considered to be fault tolerance testing methodologies.It is normally the responsibility of the software testers to conduct these tests at the end of Software Development Life Cycle (SDLC).
Definitions[edit]
In testing terms monkey testing means that the tester acts like a monkey(not literally). Like a monkey knows nothing about the software likewise the tester gives random, unique and irrelevant inputs to the system to check its point of break.This type of technique is error based hit and trial technique to test the system's performance under different correct and wrong information.
Gorilla Testing is similar to monkey testing in sense that it also involves testing with wrong inputs but in this technique we give vast range of wrong and right inputs to test the system. The purpose of giving vast inputs is to check behavior of the system when extensively a module or functionality of the system is used.Each and every aspect of the module or functionality under test is tested in gorilla testing as the vast range of inputs hardly leave any thing behind.
Similarities[edit]
- Both of these tests are conducted in the final stages of testing phase.
- These tests are tailored in the end and don't have any special conducting methodologies.
- These tests are very uncommon.
- Both of these tests tend to find the breaking point of the system.
- Both of them are fault tolerance testing techniques.
Differences[edit]
Monkey testing doesn't require any special training or preparation. Any team member can conduct this test. The purpose is to crash the system and making sure it doesn't. For this purpose we can give different inputs and check the system's behavior.This testing only checks the output of the functionality.
Gorilla testing differs from monkey testing in preparation sense as for this testing the module or functionality under test has to be fully understood and all the team members are not capable for this testing so the person having full understanding of the module/functionality can conduct this test. This testing checks the behavior as well as the in depth elements of the modules.
Advantages[edit]
The data of monkey testing gives us the idea of how the system would perform under tangible wrong or right inputs; would it crash or give appropriate results?
The results of gorilla testing give the details of each and every aspect of the module/functionality under test. It makes sure that the system won't lag or be disturbed under exhaustive load if a functionality is performed repeatedly with wrong or right inputs.
References[edit]
This article "Monkey testing vs gorilla testing" is from Wikipedia. The list of its authors can be seen in its historical. Articles copied from Draft Namespace on Wikipedia could be seen on the Draft Namespace of Wikipedia and not main one.
