Software Testing
What is Quality Assurance(QA)? Process, Methods, Examples
Before we learn Quality Assurance, let's understand- What is Quality? Quality is extremely hard to define,...
Monkey Testing is a software testing technique in which the tester enters any random inputs into the software application without predefined test cases and checks the behavior of the software application, whether it crashes or not. The purpose of Monkey testing is to find the bugs and errors in the software application using experimental techniques.
Gorilla Testing is a Software testing technique wherein a module of the program is repeatedly tested to ensure that it is working correctly and there is no bug in that module.
A module can be tested over a hundred times, and in the same manner. So, Gorilla Testing is also known as "Frustrating Testing".
One can consider that Monkey Testing, Gorilla Testing, and Ad-hoc Testing are same as there are some similar facts present in all of them but the real fact is that they are different from each other… how?
We will first see the difference between Monkey and Gorilla Testing. First be clear with it to avoid confusion.
Monkey Testing is performed randomly with no specifically predefined test cases | It is neither predefined nor random |
Monkey Testing is performed on entire system can have several test cases | Gorilla Testing is performed on specifically few selective modules with few test cases |
The objective of Monkey Testing is to check for system crash | Objective of Gorilla testing is to check whether the module is working properly or not |
Once get cleared with this difference have a look towards next;
Monkey Testing is performed randomly with no specifically predefined test cases | Ad-hoc testing is performed without planning and documentation(test cases and SRS) |
In Monkey Testing testers may not know what is the system is all about and its purpose | In Ad-hoc Testing tester must understand the system significantly before performing testing |
The objective of Monkey Testing is to check for system crash | Objective of Ad-hoc testing is to divide the system randomly into subparts and check their functionality |
Monkey Testing is further divided into several categories according to its way of implementation, See the following diagram for a quick idea of it;
Monkey Testing can also be performed for Android even. Monkey Testing may get efficient with the use of tools. Even it can be used to find more bugs like other testing types. If we use tool for Monkey Testing what could be the general process followed for it? Just have a quick look;
The process of Monkey Testing can be automated even with the use of tools but as it is some sort of new kind of testing introduced and not yet established on industry level these tools have less identity, unlike others. This situation may get changed with coming era of Testing Process then we will have look towards the upcoming impact of Monkey testing and its significant effect on industry standards. This is an introductory tutorial for Monkey Testing to cover basic idea about it.
Summary:
This article is contributed by Dhanshri Salvi
Before we learn Quality Assurance, let's understand- What is Quality? Quality is extremely hard to define,...
What is Path Testing? Path testing is a structural testing method that involves using the source code...
{loadposition top-ads-automation-testing-tools} There are tons of Software Development tools and...
Configuration Testing Configuration Testing is a software testing technique in which the software...
What is Regression Testing? REGRESSION TESTING is defined as a type of software testing to confirm...
What is Bugzilla? Bugzilla is an open-source issue/bug tracking system that allows developers to...